What problem does it solve? Writing business logic in traditional application services often leads to layer-boundary violations, infrastructure leakage, in-memory aggregation, and inconsistent patterns. This Skill guides the implementation of service operations so they stay aligned with the modeled domain, existing repository abstractions, and established solution conventions. ## Core Features & Use Cases - Layer-safe service implementation: Enforces Domain/Application-only dependencies, banning Entity Framework, Dapper, DbContexts, and other infrastructure types from the service layer. - Pattern-consistent workflows: Searches the codebase for similar services, mapping conventions, error/result patterns, and unit-of-work conventions before writing code. - Strict data-access rules: Prohibits in-memory aggregation, EF Include/ThenInclude in the Application layer, unnecessary repository Update calls, and SaveChangesAsync unless DB-generated values are required. - AutoMapper enforcement: Requires AutoMapper for DTO projections with a mandatory verification gate that locates or creates Profile mappings. - Use Case: When asked to implement a GetOrderSummary operation on an existing OrderService, the Skill inspects nearby services, extends the repository abstraction for the aggregation, maps via AutoMapper, and produces code matching the solution's conventions. ## Quick Start Implement the CancelOrder operation in the existing OrderService following the application service implementation guidelines.
