Model .NET business rules with aggregates, value objects, and domain events.
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill ddd-trossitec
Please help me install this Agent Skill. Skill: ddd Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/ddd Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill ddd-trossitec
DDD helps you model complex business rules by organizing your code around clear consistency boundaries instead of letting CRUD-style data structures erode invariants and maintainability.
Use this when implementing DDD tactical patterns in .NET—especially around aggregates, domain events, value objects, and repository persistence—and when your architecture advisor recommends DDD with Clean Architecture.
Load this skill while implementing your next aggregate-based feature and ask your AI to design the aggregate root, value objects, domain events, and repository persistence approach for your bounded context.
High-intent search queries and answers about installing and using this skill.
To model aggregates in .NET, use aggregate roots as the sole entry point and validate invariants inside the aggregate to enforce consistency boundaries within a single transaction. This prevents CRUD-style data structures from eroding your business rules and maintainability.
The best way to prevent primitive obsession and ID mix-ups in domain modeling is by using value objects represented as immutable records alongside strongly-typed IDs, ensuring type-safe identifiers and validated data structures across your bounded context.
You should dispatch domain events during EF Core persistence to decouple cross-aggregate side effects from core logic. This ensures external code interacts through the aggregate root while keeping cross-aggregate consistency eventual rather than immediate.
Common DDD anti-patterns to avoid include oversized aggregates, misusing domain events for intra-aggregate logic, assigning identity to value objects, and creating anemic aggregates that lack behavior. These erode consistency boundaries and domain model effectiveness.
Yes, you can use this DDD tactical guidance for Clean Architecture feature development in .NET. It specifically applies to implementing bounded contexts, defining aggregate root behavior, persisting aggregates, and coordinating side effects when your architecture advisor recommends DDD.
AlteriomConvert PRDs into DDD models with bounded contexts, aggregates, and domain events.
shahdanishApply Domain-Driven Design to structure .NET domain models with aggregates and value objects.
mitkoxImplement CQRS patterns in .NET applications using MediatR.
cameronraysmithExplain event sourcing patterns including event replay, state reconstruction, and CQRS.
