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 structures the spec file following RSpec conventions: describe for class/method, context for scenarios, spec path mirroring source path, prefer let over let!, and no 'and' in example descriptions. Also verifies frozen_string_literal pragma and subject definition.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Spec file at mirrored path",
"description": "The spec file is placed at spec/services/notifications/user_notifier_spec.rb — mirroring the source path app/services/notifications/user_notifier.rb",
"max_score": 15
},
{
"name": "RSpec.describe uses module::class",
"description": "The top-level RSpec.describe references the full constant Notifications::UserNotifier (or described_class equivalent)",
"max_score": 10
},
{
"name": "describe for method",
"description": "A describe block is used for the '.call' class method (e.g. describe '.call')",
"max_score": 10
},
{
"name": "context for scenario variations",
"description": "At least two context blocks are used to describe scenario variations — phrased with 'when' or 'with' (e.g. 'when event_type is invalid')",
"max_score": 12
},
{
"name": "let used for test data",
"description": "Test data (user_id, event_type, params) is set up using let blocks, not bare instance variables or local variables in before hooks",
"max_score": 10
},
{
"name": "No let! for non-setup data",
"description": "let! is NOT used for data that does not need to exist unconditionally — only plain let is used for parameters and simple values",
"max_score": 10
},
{
"name": "No 'and' in example descriptions",
"description": "No it block description contains ' and ' — each example tests exactly one behavior",
"max_score": 12
},
{
"name": "Frozen string literal",
"description": "The spec file begins with # frozen_string_literal: true",
"max_score": 8
},
{
"name": "Subject defined",
"description": "A subject or named subject is defined for the main service call (e.g. subject(:result) { described_class.call(...) })",
"max_score": 8
},
{
"name": "let_it_be NOT used",
"description": "let_it_be is NOT used anywhere in the spec file (test-prof is not in this project)",
"max_score": 5
}
]
}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