add-command

To scaffold a CQRS command, provide the command name and target domain to generate the command record, handler, validator, and POST endpoint skeleton following project conventions. It wires DI registration and OpenAPI metadata across domain, application, and API layers.

The best way to generate a new CQRS command across microservices is using a scaffolding tool that creates type-safe command and response shapes while aligning file structure and naming with existing project conventions. It ensures consistent handler and endpoint creation.

Yes, scaffolding a CQRS command includes generating a validator and setting up DI wiring. The generated skeleton ensures the command record, handler, and endpoint are properly registered for dependency injection alongside OpenAPI-compatible endpoint metadata.

Yes, you can use command scaffolding for POST endpoints with OpenAPI metadata. The scaffolding process generates endpoints that are OpenAPI-compatible, ensuring the API layer exposes the new command with proper documentation and type-safe response shapes.

You need to scaffold a new command handler in a CQRS architecture when adding a new write operation that requires domain, application, and API layer coverage. It automates creating the handler, validator, and endpoint skeletons to maintain project conventions.

A CQRS command scaffold needs a validator and type-safe response shapes to ensure input integrity and predictable API contracts. Generating these components together guarantees the command handler adheres to project conventions and OpenAPI metadata requirements.