Architecture Clean Architecture

Overview

Use this skill to structure systems so business rules remain stable while infrastructure and frameworks evolve.

Scope Boundaries

• Framework and infrastructure details are leaking into domain logic.
• Dependency direction is inconsistent and change cost is rising.
• Teams need explicit boundaries between use cases, adapters, and delivery layers.

Core Judgments

• Domain boundary: what business rules must stay framework-independent.
• Use-case orchestration: what belongs in application services versus domain entities.
• Dependency inversion points: where interfaces must isolate infra concerns.
• Transaction and consistency scope: where atomicity belongs in the stack.