Download for MacApple silicon, macOS 14+
Skill

abp-app-nolayers

@abpframework Updated 2026-11-01

ABP Single-Layer (No-Layers / nolayers) application template - single project structure, feature-based file organization, no separate Domain/Application.Contracts projects. Use when working with the single-layer web application template or when the project has no layered separation.

abpangulararchitectureaspnetaspnet-coreaspnetcoreblazorc-sharp

Install

With your agent

Install OMGSkills skill "abpframework/abp:.claude/skills/abp-app-nolayers" 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-app-nolayers ~/.claude/skills/abp-app-nolayers

From README

ABP Single-Layer Application Template Docs: https://abp.io/docs/latest/solution-templates/single-layer-web-application Solution Structure Single project containing everything: Key Differences from Layered | Layered Template | Single-Layer Template | |------------------|----------------------| | DTOs in Application.Contracts | DTOs in Services folder (same project) | | Repository interfaces in Domain | Use generic IRepository directly | | Separate Domain.Shared for constants | Constants in same project | | Multiple module classes | Single module class | File Organization Group related files by feature: Simplified Entity (Still keep invariants) Single-layer templates are structurally simpler, but you may still have real business invariants. For trivial CRUD entities, public setters can be acceptable. For non-trivial business rules, still prefer encapsulation (private setters + methods) to prevent invalid states.