dhh-rails-style

DHH Rails style enforces REST-first patterns, fat models with thin controllers, and Current attributes for authorization. Apply it during code generation or refactoring by mapping controller actions to resources, organizing logic into concerns, and keeping authorization simple on the User model.

REST-first means designing controllers around resources and HTTP verbs rather than custom actions. Each resource maps to standard actions (index, show, create, update, destroy), simplifying routing, reducing controller complexity, and aligning with Rails conventions.

Yes. DHH Rails style includes guidance for Turbo and Stimulus integration within REST-first patterns. These tools enhance view interactivity without breaking REST principles or requiring fat controllers.

Place business logic in models (fat models), keep controllers lean by delegating to models, use concerns for shared behavior across models, and implement authorization through Current attributes and User model logic rather than scattered authorization checks.

DHH style prioritizes simplicity and convention over configuration, favoring fat models, thin controllers, database-backed design, and modular concerns. It contrasts with service-object-heavy or microservice approaches by keeping Rails apps monolithic and straightforward.

Yes. The skill codifies DHH Rails conventions to guide code reviews, ensuring consistent patterns across controllers, models, concerns, and authorization workflows. Use it as a reference for maintaining style conformance across your team.