What problem does it solve? Cross-layer refactors in a .NET Clean Architecture codebase often introduce upward dependencies, misplaced validation, or layer leakage that silently violate the repository contract. This Skill blocks those violations by loading the dependency rules, layer responsibilities, and fix patterns before any architectural change is made. ## Core Features & Use Cases - Dependency Direction Enforcement: Verifies Domain has no external references, Application references Domain only, and Persistence/Infrastructure never leak into inner layers. - Layer Placement Guidance: Decides whether code belongs in Domain, Application, Persistence, Infrastructure, API, or Blazor using decision guides and violation examples. - Record/Class Migration Rules: Governs record class, sealed record, and readonly record struct selection during value-object migrations. - Use Case: When adding a new MediatR handler that needs database access, the Skill ensures the handler depends on a repository interface in Application rather than injecting DbContext directly. ## Quick Start Ask the assistant to review whether a new service or repository belongs in Domain, Application, Persistence, or API before writing the code.
