Software Development

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 sketch a column you are already in scope, even in an exploratory back-and-forth where no file is written yet. Do not let a \"we're just discussing\" framing defer it. Do NOT use for non-Rails backends, NestJS, or general architecture (use nestjs-modular-monolith or coding-guidelines).

Publisher / source

tech-leads-club/agent-skills (found on GitHub top repositories)

Upstream record

tech-leads-club/agent-skills

Version

Version 1

Published

2026-11-04

Publication review

Approved for publication · recorded passed scan 2026-11-04

Content fingerprint

edb41dc63a474c156ce2f3e9a40bcbbd053b9c0b0fb2a583402f8af4e370dda7