rails-conventions

Rails conventions provide a canonical file structure map for Rails 7+ apps, covering app/, config/, and lib/ directories. They establish clear naming patterns, RESTful routing, and architectural guidelines like fat models and skinny controllers to ensure maintainable and predictable code organization.

To apply the fat model skinny controller pattern, keep your Rails controllers lean by delegating business logic and data validation to the models. This architectural convention improves maintainability by ensuring controllers primarily handle request routing and responses.

Setting up RESTful routing in Rails 7 involves mapping HTTP verbs to controller actions conventionally, ensuring predictable resource endpoints. This standard approach aligns with the Rails Way, guiding scalable application organization and easier collaboration during onboarding and refactoring.

Use Rails concerns during refactoring to extract shared logic across multiple models or controllers, adhering to architectural guidelines. This convention prevents code duplication and maintains the fat model, skinny controller balance by grouping related functionalities into modular, reusable modules.

These Rails conventions apply to both new applications and legacy refactoring efforts. The guidelines cover standard file structure, naming, and RESTful routing for Rails 7+ projects, ensuring scalable code organization during onboarding, active development, and code reviews.