layered-rails

Deep analysis of Active Record callbacks in the codebase.

Identify and analyze god objects in the codebase using churn × complexity metrics.

Comprehensive layered architecture analysis of a Rails codebase or specific directory.

Plan gradual adoption of layered architecture patterns.

Standalone code review from layered architecture perspective.

Run the specification test on files to evaluate layer responsibility alignment.

Use this agent when planning incremental adoption of layered architecture for Rails codebases. Creates phased roadmaps for introducing patterns like authorization (policies), callback extraction, god object decomposition, or ViewComponent adoption. Analyzes current state, finds existing patterns to build upon, and produces specific before/after code examples with 'stop here if' guidance.

Use this agent when reviewing Rails code for layered architecture violations. Checks for: Current.user in models, notifications/mailers in domain layer, request objects in services, business logic in controllers, anemic models, low-scoring callbacks (operations that should be extracted), code-slicing concerns, and god objects. Provides specific fixes with code examples.

Design and review Rails applications using layered architecture principles from "Layered Design for Ruby on Rails Applications". Use when analyzing Rails codebases, reviewing PRs for architecture violations, planning feature implementations, or implementing patterns like authorization, view components, or AI integration. Triggers on "layered design", "architecture layers", "abstraction", "specification test", "layer violation", "extract service", "fat controller", "god object".