Writing Ruby on Rails code can follow a clear and proven style. That style comes from DHH at 37signals. It focuses on simplicity and correctness. The best code is the code you do not write. The second best is code that is obviously correct.
This approach uses REST purity and fat models with thin controllers. It avoids unnecessary gems and fancy tools. Instead it relies on plain Rails features like concerns, database constraints, and Hotwire. You build solutions before reaching for extra libraries.
The style embraces clarity over cleverness. It favors write-time operations over read-time computations. It also uses database-backed everything instead of Redis or Sidekiq. The result is code that is easy to understand and maintain.
Global
mkdir -p ~/.claude/skills/ce-dhh-rails-styleProject
mkdir -p .claude/skills/ce-dhh-rails-styleSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues