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
# Good: narrow and tested
spec.add_dependency "rails", ">= 7.0", "< 8.0"
spec.required_ruby_version = ">= 3.0"
# Bad: claims support without CI evidence
# spec.add_dependency "rails", ">= 5.2" # untested on 5.2/6.x# File: lib/my_engine/widget_policy.rb
# ✅ Good: constant matches path
module MyEngine
class WidgetPolicy
end
end
# ❌ Bad: will break with Zeitwerk
# class WidgetPolicy # expected in widget_policy.rb at root — wrong namespaceRun bundle exec rake zeitwerk:check to detect mismatches before shipping.
# In engine.rb
initializer "my_engine.setup" do
config.to_prepare do
MyEngine::Decorator.apply # runs on each reload in development
end
endHooks registered outside config.to_prepare run only once at boot and will not pick up reloaded code.
# .github/workflows/ci.yml
strategy:
matrix:
ruby: ["3.1", "3.2", "3.3"]
rails: ["7.0", "7.1", "7.2"]
steps:
- name: Set Rails version
run: bundle config set --local gemfile gemfiles/rails_${{ matrix.rails }}.gemfile
- run: bundle exec rake zeitwerk:check
- run: bundle exec rspecEach claimed version in add_dependency must have a matching row in the matrix.
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