Curated library of AI agent skills for Ruby on Rails development. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and workflow automation.
98
99%
Does it follow best practices?
Impact
98%
1.38xAverage score across 26 eval scenarios
Passed
No known issues
{
"context": "Tests whether the agent follows a test-first development workflow: writing the spec before the implementation, documenting the expected failure before any service code is written, and explicitly planning the implementation scope before coding it.",
"type": "weighted_checklist",
"checklist": [
{
"name": "process_log.md exists",
"description": "A process_log.md file is present in the workspace",
"max_score": 5
},
{
"name": "Spec content before implementation",
"description": "In process_log.md, the section describing or quoting spec/test content appears earlier in the document than the section describing or quoting implementation code",
"max_score": 20
},
{
"name": "Expected failure documented",
"description": "process_log.md includes a description of what the test would produce (fail, error, or expected failure output) before implementation code was written — not just 'test passes'",
"max_score": 15
},
{
"name": "Test design phase present",
"description": "process_log.md contains a distinct phase or section focused on test design — describing the boundary being tested, edge cases, or what the spec is intended to verify",
"max_score": 12
},
{
"name": "Implementation plan before code",
"description": "process_log.md contains an explicit step where the scope of the implementation is planned (which class/methods will be created) before source code is written",
"max_score": 12
},
{
"name": "No implementation code before spec phase",
"description": "process_log.md does NOT show Ruby service implementation code in a section that precedes any spec/test content — implementation code only appears after test content",
"max_score": 12
},
{
"name": "At least three distinct phases",
"description": "process_log.md contains at least three clearly labelled or structurally distinct phases of development work",
"max_score": 8
},
{
"name": "Spec file exists",
"description": "spec/services/memberships/upgrade_service_spec.rb is present",
"max_score": 5
},
{
"name": "Implementation file exists",
"description": "app/services/memberships/upgrade_service.rb is present",
"max_score": 5
},
{
"name": "Spec uses describe/context structure",
"description": "The spec file uses RSpec.describe for the class and at least one context block for a scenario variation",
"max_score": 6
}
]
}api-rest-collection
create-prd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
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
generate-tasks
mcp_server
rails-architecture-review
rails-background-jobs
rails-bug-triage
rails-code-conventions
rails-code-review
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
rails-graphql-best-practices
rails-migration-safety
rails-review-response
rails-security-review
rails-skills-orchestrator
rails-stack-conventions
rails-tdd-slices
refactor-safely
rspec-best-practices
rspec-service-testing
ruby-service-objects
strategy-factory-null-calculator
ticket-planning
yard-documentation