From rails-agent-skills
Triages and decomposes complex Ruby on Rails requests into ordered sub-tasks, delegates to specialized skills for testing, code review, engines, DDD, and patterns. Enforces TDD discipline across code-producing work.
npx claudepluginhub igmarin/rails-agent-skills --plugin rails-agent-skillsThis skill uses the workspace's default tool permissions.
Triages and decomposes any Ruby on Rails request into ordered sub-tasks, then delegates to the correct specialized skill. Enforces the Tests Gate Implementation mandate across all code-producing work.
Orchestrates Rails TDD cycle: generates failing RSpec spec first, implements minimal code to pass, refactors, adds YARD docs, runs linters, and creates self-reviewed PR. For red-green-refactor feature development.
Maps Rails tasks to domain skills (models, controllers, views, hotwire, testing) integrated with Superpowers workflows. Checks Superpowers dependency and enforces foundation usage first.
Writes idiomatic Ruby code using metaprogramming, Rails patterns, performance optimization. Specializes in gem development, RSpec/Minitest testing, and RuboCop.
Share bugs, ideas, or general feedback.
Triages and decomposes any Ruby on Rails request into ordered sub-tasks, then delegates to the correct specialized skill. Enforces the Tests Gate Implementation mandate across all code-producing work.
When a task arrives, identify the matching skill from the tables below and name it explicitly as the next skill to use before responding further. Generated artifacts (YARD docs, Postman collections, READMEs) must be in English unless the user explicitly requests another language.
Invocation example:
User: "I want to add a payment feature but I'm not sure where to start."
Claude: "This is a feature request with unclear scope. I'll start by loading the codebase context, then create a PRD.\n\nNext skill: skills/context/rails-context-engineering"
Non-negotiable: no implementation code until a test exists, runs, and fails for the right reason (feature missing, not config/syntax).
| Skill | Use when... |
|---|---|
| rails-context-engineering | Before any code/spec/PRD in an existing Rails codebase — load schema, routes, nearest patterns, surface ambiguity |
| rspec-best-practices | Writing, reviewing, or cleaning up RSpec tests; TDD discipline for all implementation |
| rails-tdd-slices | Choosing the best first failing spec for a Rails change |
| rails-bug-triage | Turning a bug report into a reproduction spec and fix plan |
| rails-code-review | Reviewing Rails PRs, controllers, models, migrations, or queries — the subject is a specific file or changeset |
| rails-architecture-review | Reviewing structure, boundaries, fat models/controllers — the question is about design or system shape, not a specific PR |
| rails-stack-conventions | Writing Rails code for PostgreSQL + Hotwire + Tailwind stack |
| refactor-safely | Restructuring code while preserving behavior |
| create-prd | Planning a feature or writing requirements |
| generate-tasks | Breaking a PRD into implementation tasks |
When multiple skills could apply: TDD → Planning → Domain discovery → Process (refactor-safely) → Domain implementation (rails-*, ruby-*). Use rails-tdd-slices when the first failing spec is not obvious.
Key disambiguation signals:
rails-architecture-review vs rails-code-review: use architecture-review when the question is about system shape, service boundaries, or design patterns; use code-review when the subject is a concrete PR, file, or changeset.rails-tdd-slices vs rspec-best-practices: use tdd-slices when the challenge is which test to write first; use rspec-best-practices when the challenge is how to write or improve a test.rails-context-engineering before any other code-producing skill in an unfamiliar or existing codebase.Fallback for ambiguous requests: If no clear skill match, default to rails-context-engineering to load codebase context, then re-evaluate based on findings.
User: "There's a bug where orders placed at midnight sometimes get the wrong price."
Match: Concrete bug report with a reproduction path. See "Bug fix" workflow below.
Next skill: skills/testing/rails-bug-triage
User: "Help me improve this Rails app."
Match: Vague request, no clear skill. Use fallback: load context first.
Next skill: skills/context/rails-context-engineering
User: "I have a PR that adds a new controller, changes the Order model, adds a migration, and introduces a service object."
Match: Multi-concern changeset. Load context, then decompose into appropriate review skills.
Next skill: skills/context/rails-context-engineering
For additional routing examples (DDD-first features, GraphQL APIs, engines, edge cases), see assets/examples.md.
Sub-skills are invoked by stating their name as the next skill to apply, e.g. "Next skill: skills/workflows/rails-tdd-loop", before proceeding with that skill's instructions.
TDD Feature Loop (primary daily workflow) — use skills/workflows/rails-tdd-loop:
skills/context/rails-context-engineering → [CHECK: context loaded] → skills/workflows/rails-tdd-loop → PR
Feature (standard): skills/context/rails-context-engineering → [CHECK: context loaded] → skills/planning/create-prd → [CHECK: PRD approved] → skills/planning/generate-tasks → [CHECK: tasks complete] → skills/workflows/rails-tdd-loop
Bug fix: skills/testing/rails-bug-triage → [GATE: reproduction spec fails] → skills/workflows/rails-tdd-loop → fix → verify passes
For additional workflows (DDD-first, code review, engines, refactoring, GraphQL), see assets/workflows.md.