abp-dependency-rules
ABP project layer dependency rules - which projects can reference which, domain/application/infrastructure separation, cross-layer violations to avoid. Use when reviewing project structure, adding new project references, or checking if a dependency direction is correct.
Install
With your agent
Install OMGSkills skill "abpframework/abp:.claude/skills/abp-dependency-rules" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/abpframework/abp /tmp/abp && ln -s /tmp/abp/.claude/skills/abp-dependency-rules ~/.claude/skills/abp-dependency-rulesFrom README
ABP Dependency Rules Core Principles (All Templates) These principles apply regardless of solution structure: Domain logic never depends on infrastructure (no DbContext in domain/application) Use abstractions (interfaces) for dependencies Higher layers depend on lower layers, never the reverse Data access through repositories, not direct DbContext Layered Template Structure Note: This section applies to layered templates (app, module). Single-layer and microservice templates have different structures.
More from this repo
abp-angular
ABP Angular UI patterns - generate-proxy, ListService, PermissionGuard, abpLocalization pipe, ConfirmationService,...
abp-app-nolayers
ABP Single-Layer (No-Layers / nolayers) application template - single project structure, feature-based file...
abp-application-layer
ABP Application Services, DTOs, CRUD service, object mapping (Mapperly/AutoMapper), validation, error handling.