command-generator

To generate CQRS command scaffolding, request the AI to create a command record, FluentValidation validator, and IRequestHandler handler for a specific feature. This produces sealed record types, validation classes, and handler implementations using IUnitOfWork and Result within your Application/Features folder.

The best way to structure MediatR command handlers and validators is using a per-feature folder layout. Place the sealed record command, FluentValidation validator, and IRequestHandler implementation together under Application/Features/[Aggregate] to maintain uniform, testable code across create, update, and delete operations.

Yes, this CQRS scaffolding works specifically with FluentValidation and MediatR. It generates FluentValidation validators with standard rules including child rules for collections, and produces IRequestHandler implementations that integrate MediatR's request handling pipeline for your .NET applications.

Yes, you can use IUnitOfWork and Result patterns in your command handlers. The generated IRequestHandler implementations specifically use IUnitOfWork for persistence and return Result or Result<T> objects, ensuring standardized transaction handling and consistent error reporting across your CQRS features.

To create a CreateOrderCommand with validation in .NET, ask the AI to generate the command under Application/Features/Orders. It produces a sealed record command type, a FluentValidation validator with common rules, and an IRequestHandler that persists data via IUnitOfWork and returns Result.

CQRS command scaffolding is the automated generation of command records, validators, and handlers for create, update, and delete operations. You need it when building .NET applications with MediatR and FluentValidation to eliminate repetitive manual coding and ensure consistent, production-ready architectural patterns.