Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ciembor/clean-architecture
Apply Robert C. Martin-inspired architecture rules when separating business policy from frameworks, databases, UI, or infrastructure details.
Passed 22 of 23 test cases with the skill, and 19 of 23 without it.
3 fixed19 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
An application contains a monolithic `SystemManager` class that performs user registration, inventory updates, order processing, and email dispatching. Recommend how to refactor this architecture into maintainable application boundaries.
| Checked | Without skill | With skill |
|---|---|---|
| Each business operation is split into an independent single-purpose use case class | Missed | Passed |
| Use cases orchestrate interactions between entities and outer-layer gateways | Passed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a task involves architectural boundaries, dependency direction, use cases, entities, interface adapters, framework isolation, or technology churn.
Before making design or code decisions, read and apply clean-architecture.mini.md. Use clean-architecture.md only as a deeper reference when the mini rules are not enough for the current architectural tradeoff.
test cases passed, vs 19 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.