Layered Rails
- 410 repo stars
- Updated May 20, 2026
- palkan/skills
layered-rails is a Claude skill that applies layered architecture principles from Layered Design for Ruby on Rails Applications so developers can structure and review Rails code with correct abstractions.
About
layered-rails is a Claude skill based on Layered Design for Ruby on Rails Applications that helps developers write, refactor, and review Rails code across presentation, application, domain, and infrastructure layers. Reach for it when implementing or reviewing models, controllers, services, jobs, policies, or view components and you need guardrails against layer violations, callback misuse, or god objects. It bundles workflows for architecture audits, specification tests, callback scoring, and gradual layerification plans.
- Four-layer model: presentation, application, domain, infrastructure with unidirectional flow
- Workflows: analyze, review, spec-test, service audit, callback scoring, god-object analysis
- Pattern catalog covers service, query, form, policy, presenter, and value objects
- Specification test extracts responsibilities that exceed a layer's primary concern
- Plugin install adds slash commands like /layered-rails:review and /layered-rails:plan
Layered Rails by the numbers
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/palkan/skills --skill layered-railsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 410 |
|---|---|
| Last updated | May 20, 2026 |
| Repository | palkan/skills ↗ |
How should this Rails code be organized across layers, and where do service objects, policies, and domain logic actually belong?
Designs and reviews Rails apps using layered architecture—presentation, application, domain, infrastructure—with spec tests, pattern catalogs, and refactor workflows.
Who is it for?
Rails developers refactoring or reviewing medium-to-large codebases who want systematic layer enforcement, pattern selection, and specification-test guidance.
Skip if: Non-Rails projects or greenfield apps with no interest in layered architecture discipline or incremental layerification.
When should I use this skill?
Writing or refactoring Rails models, controllers, services, or jobs; reviewing PRs for layer violations; or running specification tests on a file or directory.
What you get
Layer-correct refactor recommendations, violation reports, callback scores, god-object decomposition plans, and pattern-specific implementation guidance aligned to the four-layer model.
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
What are the four architecture layers?
Presentation (controllers, views, mailers), application (services, forms), domain (models, value objects), and infrastructure (Active Record, external APIs).
What is the specification test?
List each responsibility in a file, compare it to the layer's primary concern, and extract anything that belongs in a lower layer.
When should I extract a service object?
Use services to orchestrate domain operations as a waiting room—avoid letting app/services become a permanent bag of unrelated objects.