clean-code-architecture
Clean Code and Software Architecture Design
Apply clean-code and software-architecture principles to Java Spring Boot backend API microservices, async microservices, and adapter libraries. Use this skill for design review, refactoring, and architecture guidance across the codebase produced by generate-api-code, generate-async-code, and generate-adapter-lib-code. This skill does not change public API contracts, event contracts, or existing layering conventions — it improves the quality of code within those boundaries.
Important: This skill does NOT introduce a new architecture, framework, or package layout. It enforces clean structure, naming, and dependency direction within the repository's existing layered shape (
Controller/Listener -> Service interface -> ServiceImpl -> adapter/shared-lib client).
No Human-in-the-Loop: This skill runs as an autonomous step in an agentic workflow. It never pauses for user confirmation, style preference, or approval of a finding. Scope resolution, severity classification, and fix-vs-report decisions are driven by the deterministic rules in this document and by standard industry static-analysis thresholds. There is no pass/fail gate — the skill works through the checklist below and applies fixes directly.
Code-Context Check (Perform Before Any Tool Calls)
This skill runs unattended inside an agentic workflow. There is no human in the loop to answer clarifying questions, so scope must be resolved autonomously from available signals, never by pausing for user input.