Rails Skills Orchestrator

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"

CROSS-CUTTING MANDATE: Tests Gate Implementation

Non-negotiable: no implementation code until a test exists, runs, and fails for the right reason (feature missing, not config/syntax).

Core Skills (Most Common)

Skill Priority

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.

Routing Examples

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.

Typical Workflows

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.

Assets

• assets/examples.md — 20+ routing examples covering ambiguous requests, multi-concern PRs, DDD-first features, engines, and edge cases
• assets/workflows.md — Extended workflow definitions for DDD-first, code review, engines, refactoring, and GraphQL
• docs/reference/skill-catalog.md — Complete skill catalog with trigger words, descriptions, and stage-based navigation