Clean Architecture

Use this skill only for projects that intentionally follow Clean Architecture. Keep policy inward and mechanisms outward.

Layer Rule

• Domain: entities, value objects, aggregates, domain services, domain events, and invariants.

• Use cases: application-specific orchestration, transaction boundaries, ports, authorization decisions that are application policy, and repository interface usage.

• Interface adapters: controllers, presenters, gateways, repository implementations, RPC adapters, DTO mapping, and persistence mapping.

• Infrastructure: cross-cutting mechanisms such as logging, configuration, metrics, DI wiring, clocks, IDs, and concrete driver setup.

Workflow

1. Confirm the project actually uses Clean Architecture.

2. Map the touched code to the four layers.