unimanage-backend

To build a .NET backend API using CQRS and MediatR, this Skill generates the necessary Controllers, Commands, Queries, Validators, and Handlers, enforcing strict separation of concerns and Clean Architecture. It standardizes RESTful API URL patterns, HTTP methods, and response structures.

The best way to structure .NET API endpoints with Clean Architecture is using a utility-first approach with predefined helpers for validation, response formatting, and database operations. This Skill enforces those standards, reducing boilerplate code and ensuring architectural consistency across RESTful endpoints.

To implement Dapper data access with SQL Server in a CQRS pattern, this Skill provides predefined database utilities for querying and handling transactions. It leverages Dapper within the MediatR handler pipeline to cleanly separate read queries from write commands.

Yes, this approach generates boilerplate code for RESTful API response formatting by enforcing a utility-first approach with predefined helpers. It automatically handles standardized response structures for both single resources and paginated lists, ensuring consistent API outputs.

Yes, you can use this Skill to generate validation logic for ASP.NET Core endpoints. When creating an endpoint, it produces the necessary Validator components alongside the Command and Handler, ensuring all incoming requests are validated according to the predefined backend standards.

You should use CQRS with MediatR instead of a standard CRUD controller in .NET when you need clear separation of concerns for complex read and write operations. This approach reduces boilerplate, enforces standardized response formatting, and maintains strict Clean Architecture boundaries via utility-first helpers.