Clean Architecture helps you build software that is easy to change and test. It focuses on separating core business rules from outside concerns like databases and user interfaces. Robert C. Martin's principles guide you to keep your inner layers pure and your dependencies pointing inward.
This skill provides 42 rules organized by priority. You can use it when designing new systems or cleaning up old code. The rules cover dependency direction, entity design, use case isolation, and more.
By following these best practices, your code becomes more maintainable and less risky to update. It helps developers work together without stepping on each other's changes.
Global
mkdir -p ~/.claude/skills/clean-architectureProject
mkdir -p .claude/skills/clean-architectureSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective