Curated library of 39 AI agent skills for Ruby on Rails development. Organized by category: planning, testing, code-quality, ddd, engines, infrastructure, api, patterns, context, orchestration, and workflows. Includes 5 callable workflow skills (rails-tdd-loop, rails-review-flow, rails-setup-flow, rails-quality-flow, rails-engines-flow) for complete development cycles. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and TDD automation.
95
98%
Does it follow best practices?
Impact
95%
1.20xAverage score across 35 eval scenarios
Passed
No known issues
A network of animal shelters shares animals between locations. When a transfer is approved, the system must: (1) decrement the animal count at the source shelter, (2) increment the count at the target shelter, and (3) record a transfer log entry — all as a single atomic operation. If any step fails, the others should be rolled back. Additionally, the team needs to look up recent transfers for a given animal by tag number, and that query must be safe against injection since tag numbers are user-supplied strings from an external partner API.
Your task is to write a Ruby service for processing an animal transfer between two shelters. The service should accept source shelter ID, target shelter ID, and the animal's tag number. It should perform the multi-step update atomically, and also expose a method for querying transfer history by tag number using a raw SQL approach for performance reasons.
Produce the following files:
app/services/<module>/<service>.rb — the transfer servicespec/services/<mirrored_path>_spec.rb — specs covering: successful transfer, source shelter not found, database failure mid-transfer (transaction rollback scenario)Use stub comments where real ActiveRecord calls would occur (e.g. # TODO: Shelter.find_by!(id: ...)) so the service structure is clear without a running database.
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
mcp_server
skills
api
api-rest-collection
rails-graphql-best-practices
code-quality
rails-architecture-review
rails-code-conventions
rails-code-review
rails-review-response
rails-security-review
rails-stack-conventions
assets
snippets
refactor-safely
context
rails-context-engineering
rails-project-onboarding
ddd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
engines
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
infrastructure
rails-api-versioning
rails-background-jobs
rails-database-seeding
rails-frontend-hotwire
rails-migration-safety
rails-performance-optimization
orchestration
rails-skills-orchestrator
patterns
ruby-service-objects
strategy-factory-null-calculator
yard-documentation
planning
create-prd
generate-tasks
ticket-planning
testing
rails-bug-triage
rails-tdd-slices
rspec-best-practices
rspec-service-testing