What problem does it solve? When working on ABP/ASP.NET Boilerplate solutions, it is easy to introduce incorrect project references—such as injecting DbContext into application services or letting the domain layer depend on application logic—which breaks the layered architecture and makes the codebase hard to maintain. ## Core Features & Use Cases - Layer Dependency Validation: Defines which ABP projects (Domain.Shared, Domain, Application.Contracts, Application, EntityFrameworkCore, HttpApi, Host) may reference each other and flags violations. - Repository Pattern Enforcement: Ensures data access goes through repository interfaces defined in Domain with implementations in EntityFrameworkCore or MongoDB projects, never direct DbContext usage. - Multi-Application Guidance: Covers vertical separation rules for solutions with multiple application layers (e.g., Admin and Public APIs) that share a common domain. - Use Case: When adding a new feature or reviewing a pull request, use this Skill to verify that new entities, DTOs, repository interfaces, and controllers are placed in the correct project and that no cross-layer violations were introduced. ## Quick Start Review my ABP solution structure and check whether the new project references I added follow the correct layer dependency rules.
