dhh-rails-style

Enforce DHH's Rails coding conventions by applying rules for REST purity, fat models, thin controllers, Current attributes, and Hotwire patterns to your Ruby code generation and refactoring processes.

Best practices for Rails model and controller design favor fat models and thin controllers, prioritizing state management via records and a clarity over cleverness philosophy to maximize maintainability.

Review Rails code against 37signals style guidelines by identifying deviations from DHH's review patterns, checking for RESTful routing, and suggesting improvements aligned with preferred gem choices.

This Rails style guide directly applies to Hotwire patterns and Current attributes, enforcing specific conventions drawn from 37signals' production codebases to ensure clarity and efficiency.

Use fat models and thin controllers in Rails when following DHH's convention enforcement, which moves business logic and state management into model records to maintain controller clarity.

The philosophy behind DHH's Rails coding style is clarity over cleverness, promoting maintainable code through REST purity, specific gem choices, and established patterns from 37signals' production codebases.