What problem does it solve? Writing MediatR command handlers often leads to layer violations, infrastructure leakage, and inconsistent patterns across a codebase. This Skill guides the implementation of Handle methods so business logic stays in the right layer, follows existing domain patterns, and respects strict rules around repositories, Unit of Work, and AutoMapper. ## Core Features & Use Cases - Guided Handle Method Implementation: Fills in or corrects the Handle method of existing *CommandHandler.cs files while preserving method signatures and IntentManaged attributes. - Layer Boundary Enforcement: Prevents direct dependencies on Entity Framework, Dapper, DbContexts, or other infrastructure types inside handlers, directing data access through Domain/Application repository abstractions. - Strict Data Access Rules: Enforces no in-memory aggregation, no unnecessary SaveChangesAsync calls, no redundant repository Update calls with EF tracking, and mandatory AutoMapper usage for DTO projections. - Use Case: When adding a new command like CreateOrderCommandHandler, the Skill inspects existing handlers, repositories, and domain entities, then implements the Handle method using established patterns such as loading aggregates, invoking domain behavior, and returning the standard result type. ## Quick Start Implement the Handle method in my CreateCustomerCommandHandler.cs following the existing repository and domain patterns in this solution.
