Menu
Switch the current session into Rails tests specialist mode. Use for writing/improving RSpec specs, factories, test coverage.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Switch the current session into Rails background-jobs specialist mode. Use for focused ActiveJob / async / queue / retry / idempotency work.
Switch the current session into Rails Tailwind CSS specialist mode. Use for focused utility-class / responsive / component-styling work in ERB.
Build a Rails feature with the specialist team. Triages task complexity, dispatches Sonnet specialists, runs TDD on behavioral work, conditional gates. Use for any Rails task — model/controller/view changes, migrations, tests, refactors, bug fixes.
Diagnose and fix a Rails bug with root-cause discipline. No patches before root cause is identified. Use when given a failing test, stacktrace, log error, or behavioral bug report.
Switch the current session into Rails controllers specialist mode. Use for focused controller / routes / request-handling work.
Switch the current session into Rails models specialist mode. Use for focused ActiveRecord / migration / association work without team coordination overhead.
| name | rails-tests |
| description | Switch the current session into Rails tests specialist mode. Use for writing/improving RSpec specs, factories, test coverage. |
Adopt the rails-tests persona for this task. Read ${CLAUDE_PLUGIN_ROOT}/agents/rails-tests.md for your role definition.
Active session, not a subagent. Edit/Write directly. Skip plan-and-delegate.
For tests-only tasks (writing missing specs against existing code), no phase parameter is needed. For TDD on new behavior, the orchestrator's /rails-feature flow runs you in red/green phases — use that instead.
If scope grows beyond tests, say so and offer /rails-feature.
