Where should business logic that spans multiple models go?

According to the Layered Rails pattern, multi-model orchestration belongs in the Application layer, typically implemented as a Service Object or an Interaction.

When should I use Layered Rails instead of standard Rails MVC?

Use it when your models or controllers exceed 500 lines, when you have complex business operations involving multiple models, or when the domain logic becomes difficult to test in isolation.

Can I use this skill alongside the dhh-coder skill?

Yes, it is designed to complement dhh-coder. You should default to DHH-style simplicity for standard CRUD and only reach for layered patterns when the specific domain complexity demands more structure.

How does the Callback Scoring system work?

It rates model callbacks from 1 to 5. Internal data transformers score high (4-5) and stay in the model, while external side-effects like sending emails score low (1-2) and should be extracted to services.

What is the Four-Layer Architecture in Rails?

It divides the application into Presentation (UI/HTTP), Application (Orchestration), Domain (Business Logic), and Infrastructure (Persistence/APIs) layers to prevent tight coupling and ensure data flows in one direction.

Layered Rails Architecture | Claude Code Skill

Layered Rails provides a comprehensive framework for organizing complex Rails codebases by separating concerns into Presentation, Application, Domain, and Infrastructure layers. It helps developers move logic out of 'fat' models and controllers into specialized patterns like Service Objects, Form Objects, and Query Objects. By enforcing strict dependency rules and providing a clear decision tree for code placement, this skill ensures applications remain maintainable, testable, and scalable as they grow in complexity while complementing simpler patterns when appropriate.

Características Principales

01Provides a 'Callback Scoring' system to identify and extract side-effects from ActiveRecord models

02Identifies 'extraction signals' to proactively refactor high-churn or overly complex code sections

03Establishes clear dependency rules to ensure lower layers never depend on higher-level context

04Implements a strict four-layer architecture: Presentation, Application, Domain, and Infrastructure

05Offers a detailed decision tree for selecting patterns like Service Objects, ViewComponents, and Policy Objects

0629 GitHub stars

Casos de Uso

01Refactoring 'fat' ActiveRecord models or bloated controllers into maintainable, specialized abstractions

02Architecting complex business logic that involves multiple models and multi-step external API integrations

03Performing architectural audits on existing Rails codebases to identify and fix layer violations

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add majesticlabs-dev/majestic-marketplace layered-rails

For use in Claude.ai and ChatGPT

Download Skill