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
Your team maintains a Rails application for agricultural planning. A business stakeholder needs a new feature that pulls current and forecast weather data from an external weather service API. The API authenticates via OAuth (client credentials flow) and returns JSON payloads describing weather readings for geographic regions. It supports pagination and occasionally has transient network failures.
The engineering team has no existing pattern for integrating with external services, but needs something maintainable and testable as more third-party APIs will follow in the coming months. The feature must fetch temperature, humidity, wind_speed, region_id, and recorded_at fields for a given region. A search capability is needed to look up readings by region ID.
Implement a complete Ruby module for the weather service integration under app/services/weather_service/. Include all necessary Ruby source files for the integration. Also produce a README.md inside the module directory documenting how to use the integration and how errors surface.
Expected output files:
app/services/weather_service/auth.rbapp/services/weather_service/client.rbapp/services/weather_service/fetcher.rbapp/services/weather_service/builder.rbapp/services/weather_service/reading.rb (domain entity)app/services/weather_service/README.mdspec/services/weather_service/ — spec files for at least Auth, Client, and the domain entitydocs
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