Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill library distills the Rails conventions used at 37signals—from Campfire, Fizzy, and DHH’s own reviews—into a set of agent-ready skills. It covers architecture, naming, security, Hotwire, migrations, jobs, testing, and webhooks, giving Rails developers a default baseline for writing and reviewing code the way 37signals does. Tech leads can use it to standardize team practices without writing internal docs from scratch.
WHO IT'S FOR
Rails Developers at 37signals-scale
adopt 37signals coding conventions and architecture patterns
Coding Assistant / LLM Prompt Engineers
calibrate AI agents for 37signals Rails code
Tech Leads / Engineering Directors
establish and enforce Rails conventions across teams
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
In the same terminal working directory, replace the author-provided `your-app` placeholder with the path to the target application, while keeping the destination suffix `.claude/skills/`.
A Ruby or Rails repository with a current git diff
Use the dhh skill to review the current git diff. Lead with the most important issue, cite file and line locations, provide concrete replacement code where possible, and finish with either “Ship it” or a prioritized list of fixes. Do not modify files.
Relevant database adapter and approximate table size, if known
Use the rails-migrations skill to review the migration at [MIGRATION_PATH]. Identify lock, reversibility, constraint, and backfill risks, then propose the smallest deploy-safe sequence. Treat [MIGRATION_PATH] as a placeholder for the actual migration file. Do not modify files.
CODE_OR_TEST_PATH: path to the Rails code or tests to review
A short description of the expected behavior
Use the rails-testing skill to review [CODE_OR_TEST_PATH] and recommend a small set of high-value Minitest tests using fixtures. Prioritize observable behavior, domain invariants, request-cycle coverage, and relevant authorization failures without duplicating assertions across layers. Treat [CODE_OR_TEST_PATH] as a placeholder for the file or directory to inspect. Do not modify files.