Building clean software means keeping parts separate. This skill shows you how to organize Java code using Clean Architecture and Domain-Driven Design. You will learn to put business logic in the center and keep it free from frameworks like Spring. This makes the code easier to test and change later.
Anyone working with Spring Boot applications can benefit. The patterns help you split code into layers like domain, application, and infrastructure. You also get guidance on using ports and adapters to swap out databases or APIs without breaking the core logic.
Whether you start a new project or fix an old one, these rules keep your codebase clean and focused. The result is a system that is more maintainable and simpler to understand for your whole team.
Global
mkdir -p ~/.claude/skills/clean-architectureProject
mkdir -p .claude/skills/clean-architectureSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues