What problem does it solve? Teams adopting Clean Architecture often misplace components, such as putting repository implementations in the infrastructure layer or leaking external dependencies into the domain layer. This Skill provides design guidance and review checkpoints based on a strict four-layer structure (Domain, Use Case, Interface Adapters, Infrastructure) to keep dependencies pointing inward. ## Core Features & Use Cases - Layer Responsibility Guidance: Defines exactly what belongs in each of the four layers, including the rule that persistence and RPC implementations live in the Interface Adapters layer, not Infrastructure. - Review Checkpoints: Supplies concrete checks such as detecting external dependencies in the domain layer, verifying repository implementation placement, and preventing infrastructure layer bloat. - Detailed Reference: Includes a per-layer breakdown of responsibilities with a dependency inversion example in TypeScript. - Use Case: When reviewing a pull request in a Clean Architecture project, ask the AI to verify that a new repository implementation is placed in the Interface Adapters layer and that the domain layer contains no database or HTTP client code. ## Quick Start Review this codebase according to Clean Architecture and check whether the repository implementations and layer dependencies are placed correctly.
