What problem does it solve? Adding a new backend feature to an ASP.NET Boilerplate modular monolith requires touching many layers — domain entities, DTOs, application services, DbContext registration, and migrations — and it is easy to break layer boundaries or naming conventions. This Skill enforces the SafeGuard architecture rules so every new feature lands in the correct project with the correct patterns. ## Core Features & Use Cases - Layered Feature Scaffolding: Generates entities in the Core domain layer, DTOs with AutoMap, app service interfaces and implementations using AsyncCrudAppService, and DbContext registrations. - Architecture Guardrails: Enforces dependency direction (Web.Host → Web.Core → Application → Core), ABP authorization attributes, and repository-based data access instead of direct DbContext usage. - Migration Guidance: Produces the correct dotnet ef migrations command while requiring the user to run it manually. - Use Case: Ask to add a LeaveType CRUD module, and receive a ready-to-paste entity, DTO, ILeaveTypeAppService interface, LeaveTypeAppService implementation, DbContext update, and migration command that all follow the project conventions. ## Quick Start Ask the assistant to scaffold a new backend feature such as "Add a JobGrade entity with CRUD following the SafeGuard backend architecture" and review the generated layer-by-layer code.
