Layered Rails Skills

Design and review Rails applications using layered architecture principles from the Layered Design for Ruby on Rails Applications book.

The bundled plugins and slash commands target Claude Code, while the core skill content (SKILL.md + workflows + references + examples) is also usable from other environments such as Codex.

Install (recommended — full plugin with commands and sub-agents):

/plugin marketplace add palkan/layered-rails-skills
/plugin install layered-rails@layered-rails-skills

Commands:

Install via skills.sh (skill content only — no slash-command bindings):

npx skills add palkan/layered-rails-skills --skill layered-rails

skills.sh delivers the skills/layered-rails/ tree — SKILL.md, workflows/, references/, and examples/. The /layered-rails:* slash commands and the layered-rails-planner / layered-rails-reviewer sub-agent registrations are not part of the skill spec and won't be copied, but every workflow they wrap is in workflows/ and can be invoked by name in plain language ("run the layered-rails review workflow on this diff"). Use this path when you want the same skill in Codex, the Claude API, or any other agent that supports skills.sh; use /plugin install when you want the slash commands.

Install via rails-hyperdrive (Rails apps — bundle-aware, commands and sub-agents included):

group :development do
  gem "rails-hyperdrive", ">= 0.8"
  gem "layered-rails-skills"
end

bin/rails hyperdrive:init

Installs the same skill tree into .claude/skills/layered-rails/, tailored to the app's bundle: the architecture core installs into any Rails app, while each per-gem reference manual under references/gems/ (Action Policy, ViewComponent, Alba, …) installs only when its gem is in the app's Gemfile.lock (the archspec manual is the exception — it installs unconditionally, since its job is to introduce that gem) — gating declared in hyperdrive.yml at the repo root — and SKILL.md's Gem References table lists only what was installed. bin/rails hyperdrive:sync picks up updates on gem upgrades.

The commands and sub-agents come along too, into .claude/commands/ and .claude/agents/. Since that directory has no plugin namespace, the commands install prefixed — /layered-rails-analyze rather than /layered-rails:analyze — and the two sub-agents keep their names.

Integration with compound-engineering

We recommend asking Claude itself to update the instructions for Compound Engineering to include Layered Design features according to your needs. Below you can find some examples.

If you use the compound-engineering plugin, add explicit instructions to include layered-rails planning and reviewing agents.

In your compound-engineering.local.md file:

---
review_agents:
  - layered-rails:layered-rails-reviewer
  - rails-reviewer
  - security-sentinel
  # - ...
---

# ...

# also worth adding something like:

We are **gradually adopting layered design principles** from "Layered Design for Ruby on Rails Applications" — clean abstraction boundaries, explicit layers, and specification tests...

Similarly, for planning features, add to your CLAUDE.md (or AGENTS.md, or whatever) smth like:

# ...

## For planning agents

When planning new features or architectural changes, use the `layered-rails` skill for analysis:
- `/layered-rails:plan` — plan incremental adoption of layered patterns
- `/layered-rails:analyze` — full codebase architecture analysis
- `/layered-rails:review` — review code from a layered architecture perspective
- `/layered-rails:spec-test` — apply the specification test to evaluate layer placement

Alternatively, you can try to add shorter instructions to CLAUDE.md:

Extend the list of **review agents** with the `layered-rails:layered-rails-reviewer` agent to check for architecture layer violations. Must be applicable to such commands from the compound-engineering plugin as `/workflow:review`, `/plan_review`, and similar.

Extend the list of **planning agents** with the `layered-rails:layered-rails-planner` agent to plan refactoring according to the layered design principles. Must be applicable to such commands from the compound-engineering plugin as `/workflow:plan`, `/deepen_plan`, and similar.

License

MIT

{
  "name": "layered-rails-skills",
  "owner": {
    "name": "Vladimir Dementyev",
    "url": "https://github.com/palkan"
  },
  "metadata": {
    "description": "A collection of Claude Code skills by Vladimir Dementyev",
    "version": "3.1.0"
  },
  "plugins": [
    {
      "name": "layered-rails",
      "description": "Design and review Rails applications using layered architecture principles from 'Layered Design for Ruby on Rails Applications'",
      "version": "3.1.0",
      "author": {
        "name": "Vladimir Dementyev",
        "url": "https://github.com/palkan"
      },
      "homepage": "https://github.com/palkan/layered-rails-skills",
      "tags": [
        "rails",
        "ruby",
        "architecture",
        "layered-design",
        "code-review"
      ],
      "source": "./layered-rails"
    }
  ]
}