Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By palkan
Analyze Rails codebases for layered architecture violations like god objects, bad callbacks, and misplaced logic; review PRs and git changes with prioritized reports; generate phased refactoring roadmaps, extraction recommendations, and annotated test skeletons to enforce patterns.
npx claudepluginhub palkan/skills --plugin layered-railsDeep 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.
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.
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Design and review Rails applications using Vanilla Rails philosophy from 37signals/Basecamp. Emphasizes thin controllers, rich domain models, and avoiding unnecessary service layers.
Rails conventions for consistent architecture + implementation in real codebases
Complete Rails development workflow with TDD, security reviews, and Linear integration
Advanced Ruby on Rails skills for MVC patterns, Active Record, and Hotwire
Ruby on Rails development toolkit with skills for Rails, Ruby, RSpec, RuboCop, SimpleCov, Brakeman, and code review with Sandi Metz principles
Agent that simplifies and refines Ruby on Rails code following 37signals patterns and the One Person Framework philosophy
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Share bugs, ideas, or general feedback.
A collection of Claude Code skills by Vladimir Dementyev.
Design and review Rails applications using layered architecture principles from the Layered Design for Ruby on Rails Applications book.
Install:
/plugin marketplace add palkan/skills
/plugin install layered-rails@palkan-skills
Commands:
| Command | Purpose |
|---|---|
/layers:analyze | Full codebase architecture analysis |
/layers:analyze:callbacks | Score model callbacks, find extraction candidates |
/layers:analyze:gods | Find god objects via churn x complexity |
/layers:review | Review code changes for layer violations |
/layers:spec-test | Run specification test on specific files |
/layers:gradual [goal] | Plan incremental adoption of layered patterns |
We recommend asking Claude itself to update the instructions for Compound Engineering to include Layered Design features according to your needs. Below you can find some examples.
If you use the compound-engineering plugin, add explicit instructions to include layered-rails planning and reviewing agents.
In your compound-engineering.local.md file:
---
review_agents:
- layered-rails
- rails-reviewer
- security-sentinel
# - ...
---
# ...
# also worth adding something like:
We are **gradually adopting layered design principles** from "Layered Design for Ruby on Rails Applications" — clean abstraction boundaries, explicit layers, and specification tests...
Similarly, for planning features, add to your CLAUDE.md (or AGENTS.md, or whatever) smth like:
# ...
### For planning agents
When planning new features or architectural changes, use the `layered-rails` skill for analysis:
- `/layers:gradual` — plan incremental adoption of layered patterns
- `/layers:analyze` — full codebase architecture analysis
- `/layers:review` — review code from a layered architecture perspective
- `/layers:spec-test` — apply the specification test to evaluate layer placement
Alternatively, you can try to add shorter instructions to CLAUDE.md:
Extend the list of **review agents** with the `layered-rails:layered-rails-reviewer` agent to check for architecture layer violations. Must be applicable to such commands from the compound-engineering plugin as `/workflow:review`, `/plan_review`, and similar.
Extend the list of **planning agents** with the `layered-rails:layered-rails-gradual` agent to plan refactoring according to the layered design principles. Must be applicable to such commands from the compound-engineering plugin as `/workflow:plan`, `/deepen_plan`, and similar.
MIT