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
{
"context": "Tests whether the agent selects the appropriate spec type for each layer of behavior: request spec for the HTTP endpoint (not controller spec), and model spec for the domain validation rule. Also verifies the agent places specs at the correct paths and covers the right behavioral boundaries.",
"type": "weighted_checklist",
"checklist": [
{
"name": "type: :request used",
"description": "The endpoint spec uses `type: :request` in the RSpec.describe declaration",
"max_score": 15
},
{
"name": "type: :controller NOT used",
"description": "No spec file uses `type: :controller` — controller spec style is absent",
"max_score": 15
},
{
"name": "Model spec file exists",
"description": "A spec file for the Booking model is present at spec/models/booking_spec.rb",
"max_score": 8
},
{
"name": "type: :model used",
"description": "The model spec uses `type: :model` in the RSpec.describe declaration",
"max_score": 8
},
{
"name": "No system or feature spec",
"description": "No spec file uses `type: :system` or `type: :feature` for these behaviors",
"max_score": 10
},
{
"name": "Request spec in spec/requests/",
"description": "The endpoint spec file is placed under spec/requests/ (not spec/controllers/)",
"max_score": 10
},
{
"name": "Endpoint URL in describe",
"description": "The request spec's RSpec.describe block references the HTTP method and endpoint path (e.g. 'POST /bookings')",
"max_score": 8
},
{
"name": "Endpoint success case covered",
"description": "The request spec contains at least one example asserting a 2xx HTTP status for a successful booking",
"max_score": 8
},
{
"name": "Endpoint failure case covered",
"description": "The request spec contains at least one example asserting a non-2xx status for a failed booking (full class or duplicate)",
"max_score": 8
},
{
"name": "Model uniqueness validation tested",
"description": "The model spec contains an example that verifies a duplicate booking is invalid",
"max_score": 10
}
]
}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