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 SaaS platform allows users to cancel their subscriptions from their account settings. The current cancellation logic is sprawled across a controller action: it updates the subscription record, schedules a grace-period email, and records a cancellation audit entry — all inline in the controller. The team has decided to extract this into a proper service layer so the logic can be tested in isolation and reused from an admin dashboard and an API endpoint.
Your job is to write a Ruby service that handles subscription cancellation for a given user. The service receives a user ID and a cancellation reason, looks up the active subscription, marks it as cancelled, and returns a structured result indicating whether the operation succeeded. If the user has no active subscription, or if the record cannot be saved, the service must return an appropriate failure result — it should never raise an exception back to its caller.
Produce the following files:
app/services/<choose_appropriate_module>/<choose_appropriate_name>.rb — the service implementationspec/services/<mirrored_path>_spec.rb — RSpec spec covering the success path, the "no active subscription" path, and a save-failure pathThe spec file should follow standard RSpec conventions (describe, context, let, .call).
Do not create a Rails app scaffold — just write the two Ruby files with realistic content. Use # TODO: integrate with actual ActiveRecord models comments where you would normally call ActiveRecord, so the structure is clear without requiring a running Rails app.
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