rails-dev
Opinionated Rails conventions: rich models, concerns, CRUD-everything, state-as-records, minimal dependencies, Minitest with fixtures. Load this skill BEFORE any code-level thinking, not only before editing a file. It is required the moment a task touches Rails code in ANY way: designing or even just discussing a data model, schema, migration, entity, association, field, validation, class, or method name; writing, planning, reviewing, analyzing, testing, debugging, or refactoring; or proposing any model, table, column, route, or code snippet inline in chat. If you are about to name a model or
npx skills add tech-leads-club/agent-skills --skill rails-dev --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rails Conventions ## Core Philosophy - **Rich models** - Business logic lives in models, not service objects - **Everything is CRUD** - New resource over new action (`resource :closure` not `post :close`) - **State as records** - `Closure` model instead of `closed: boolean` - **Concerns for composition** - `Closeable`, `Watchable`, `Commentable` - **Explicit over clever** - Inline until repetition is real; an abstraction earns its place, it isn't built on speculation - **Small interfaces** - No public method without a caller - **Let it crash** - Bang methods (`create!`), handle failures at the boundary, not by pre-guarding (`references/error-handling.md`) - **Invariants in the schema** - Hard rules (presence, uniqueness, ranges) are NOT NULL / unique / check constraints; validations are for user-facing messages, not the source of truth. References stay soft: no foreign keys, integrity at the model layer - **Minimal dependencies** - Build it yourself before reaching for gems. No Devise, Pundit, RSpec, FactoryBot, ViewComponent, service/form objects, or decorators - **Database-backed** - Solid Queue/Cache/Cable, no Redis - **Test coverage** - Maintain roughly 1:1 test ratio (1 line
- Core Philosophy
- Reference Selection
- Coding style
- Conditionals
- Method order
- Visibility
- Bang methods
- Method naming
- Comments
- Errors
- Sources
What does the rails-dev skill do?
Opinionated Rails conventions: rich models, concerns, CRUD-everything, state-as-records, minimal dependencies, Minitest with fixtures. Load this skill BEFORE any code-level thinking, not only before editing a file. It is required the moment a task touches Rails code in ANY way: designing or even just discussing a data model, schema, migration, entity, association, field, validation, class, or method name; writing, planning, reviewing, analyzing, testing, debugging, or refactoring; or proposing any model, table, column, route, or code snippet inline in chat. If you are about to name a model or
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill rails-dev --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.