What problem does it solve? Writing MediatR query handlers that respect layered architecture is error-prone: developers often leak infrastructure concerns (EF Core, Dapper, DbContexts) into the Application layer, compute aggregations in memory, or misuse Unit of Work and AutoMapper. This Skill guides the implementation of the Handle method so handlers stay aligned with domain models and existing query patterns. ## Core Features & Use Cases - Layer-boundary enforcement: Ensures handlers only depend on Domain or Application abstractions and never reference infrastructure packages like Entity Framework or Dapper. - Query pattern guidance: Applies existing repository, projection, pagination, filtering, and mapping conventions found in the codebase before inventing new approaches. - Strict data-access rules: Enforces AutoMapper for DTO projections, forbids in-memory aggregation, and controls SaveChangesAsync and repository Update usage. - Use Case: When adding a new GetCustomerOrdersQueryHandler.cs, use this Skill to implement the Handle method using the existing repository abstraction, AutoMapper projection, and cancellation-token-aware async calls. ## Quick Start Implement the Handle method in my OrdersQueryHandler.cs following the mediatr-query-handler skill rules and existing repository patterns.
