igmarin/rails-agent-skills
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
BOUNDARY_GUIDE.mdskills/testing/rails-bug-triage/
Bug Triage Boundary Guide
Maps common bug shapes to the highest-value first failing spec.
| Bug shape | Likely first spec | Path |
|---|---|---|
| Wrong status code, params handling, JSON payload | Request spec | spec/requests/ |
| Invalid state transition, validation, calculation | Model or service spec | spec/models/ or spec/services/ |
| Async side effect missing or duplicated | Job spec | spec/jobs/ |
| Engine routing/install/generator regression | Engine spec | Dummy app path |
| Third-party mapping/parsing issue | Integration or client-layer spec | spec/services/module_name/ |
Diagnosing the Right Layer
- HTTP symptoms (wrong status, wrong JSON shape, redirect loops): start at request level
- Data symptoms (wrong value saved, wrong validation message): start at model or service
- Timing symptoms (missing email, job not enqueued): start at job or service spec
- Engine symptoms (routes not found, generator broke): use dummy app request spec
When the Boundary Is Unclear
- Write the spec at the highest visible symptom boundary first.
- Run it — if it fails for the wrong reason (e.g., factory error), move down a layer.
- The correct boundary is where the failure message directly names the missing behavior.
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