rails-patterns

Topics in the source

• Rails Patterns
• When to Activate
• Core Concepts
• The directory contract
• Skinny controllers
• Service objects
• Form objects
• Query objects

Framework patterns for modern Ruby on Rails applications (Rails 7.1+ and 8.x). Rails is opinionated by design; these are the patterns the community has converged on for apps that stay maintainable past the 50-model mark. This skill is the "how." For the "what" and "when" (the decisions about which pattern to reach for), see the Ruby patterns rules — rules/ruby/patterns.md in this repository, installed as rules/ecc/ruby/patterns.md. Building a Rails application (full-stack, API-only, or hybrid) Reviewing a PR that touches app/ or config/ Generating models, controllers, services, or jobs A controller action grows past 10 lines A model file grows past 200 lines ActiveRecord queries start appearing in controllers or views Rails apps follow a predictable structure. Add directories deliberately, not casually. Avoid app/lib/, app/utils/, app/managers/. If something does not fit the directories above, the design usually needs rethinking, not a new directory. Truly generic code goes in lib/. Controllers receive a request, delegate to the right object, and render a response. Business logic lives elsewhere. (Per the Ruby patterns rules, extract to a service object when the controller starts c

This is an excerpt. Refer to the complete source and its current requirements.