dotnet-ddd

Builds the Application and API layers for a .NET DDD aggregate — DTOs, Result-returning application services, controllers, and DI wiring. Use after the domain is modeled, to expose a use-case over HTTP.

Plans .NET DDD/Clean-Architecture features across layers and enforces the dependency rule. Use when adding a new aggregate/use-case, deciding which layer code belongs in, or reviewing whether a change respects layer boundaries.

Writes the Domain layer for a .NET DDD API — entities deriving from BaseEntity, domain-service contracts, and invariant/validation logic. Use when modeling a new aggregate's core or adding business rules.

Writes the Infrastructure layer for a .NET DDD API — EF Core repositories, entity configurations, DbContext registration, UnitOfWork, JWT, and EF migrations. Use for persistence wiring and data-access concerns.

Writes xUnit unit tests for a .NET DDD API, one test project per layer mirroring tests/unit-tests. Use to cover domain rules, application services, repositories, controllers, and mappings.

Create and apply an EF Core migration for a .NET DDD API, targeting the Infrastructure project with the API as startup. Use when the model changed and the database schema needs to follow.

Review a diff or set of files in a .NET DDD API for layer-boundary and dependency-rule violations, Result/validation misuse, and convention drift. Use for "review this for DDD/architecture issues".

Add a new endpoint/action to an existing aggregate's controller and application service in a .NET DDD API, without scaffolding a whole new aggregate. Use for "add a GET/POST/search/... to the X API".

Scaffold a new aggregate/feature end-to-end across all DDD layers (Domain, Application, Infrastructure, Transversal, API) plus xUnit tests, mirroring the Product reference. Use when the user wants to add a new entity/use-case to a .NET DDD Web API.

1 hook across 1 event