A skill that applies Robert C. Martin's Clean Architecture to real work — planning a new system/feature, or reviewing an existing one for structural health. Covers SOLID at the module level, component cohesion & coupling (REP/CCP/CRP, ADP/SDP/SAP), the Dependency Rule, and the Humble Object pattern, with guidance on scaling the rigor to the size of the project instead of forcing full layering onto everything.
It triggers automatically whenever you're designing, structuring, architecting, building, or refactoring something — not just when you say "clean architecture" out loud.
/plugin marketplace add msg-01/clean-architecture-skill
/plugin install clean-architecture@clean-architecture-tools
Then reload:
/reload-plugins
Planning a new system or feature — walks through identifying actors, mapping use cases per actor, deciding what actually needs a boundary vs. what can wait (partial boundaries), inverting dependencies so business logic never depends on a detail, and wrapping unavoidable IO/DOM/framework calls in a Humble Object.
Reviewing something that exists — checks for dependency-direction violations, actor entanglement (an SRP violation hiding as "this function does one thing"), details leaking upward into business logic, coupling health once there's more than one file/module (cycles, stability direction, rigid "stable" cores), boundary hygiene, and untestable glue mixed into logic that should be pure.
Findings are written up the way a careful technical reviewer would: verdict first, categorized honestly (real violation vs. stylistic preference vs. acceptable shortcut for the project's actual size), with the concrete fix shown, not just described.
.claude-plugin/
plugin.json # plugin manifest
marketplace.json # marketplace catalog (this repo is its own marketplace)
skills/
clean-architecture/
SKILL.md
references/
solid-principles.md
component-cohesion-coupling.md
dependency-rule-and-layers.md
boundaries-and-humble-object.md
case-study-and-implementation.md
SKILL.md is the cheat sheet and workflow; the references/ files hold the full depth on each principle and are only pulled in when a specific topic needs it.
Based on Robert C. Martin, Clean Architecture: A Craftsman's Guide to Software Structure and Design (Prentice Hall, 2017).
MIT — see LICENSE.