Apply Domain-Driven Design to structure .NET domain models with aggregates and value objects.
npx skills add https://github.com/shahdanish/vibepos --skill ddd-shahdanish
Please help me install this Agent Skill. Skill: ddd Source: https://github.com/shahdanish/vibepos/tree/main/skills/ddd Command: npx skills add https://github.com/shahdanish/vibepos --skill ddd-shahdanish
Domain-Driven Design helps you model complex business rules clearly so invariants stay consistent and side effects remain decoupled as your .NET system grows.
Load the skill when designing aggregates and value objects for a DDD + Clean Architecture .NET codebase, then implement a small aggregate root with validated value objects and domain events to capture meaningful state changes.
High-intent search queries and answers about installing and using this skill.
To enforce aggregate consistency boundaries in Domain-Driven Design, structure your .NET domain models so aggregate roots serve as the only entry point, validating invariants strictly inside the aggregate within a single transactional unit.
Mapping strongly-typed IDs using EF Core in Clean Architecture requires translating strongly-typed structs through EF Core conversions, preventing identifier mixing across entities while maintaining persistence decisions within bounded contexts.
Domain events decouple side effects in a .NET aggregate root by allowing you to raise events in the domain model and handle integration or side effects externally, avoiding pollution of core business logic.
You need value objects in Domain-Driven Design to replace primitive obsession with immutable records like Money, EmailAddress, and OrderNumber, ensuring correct equality and validation within your .NET domain models.
Yes, you should persist aggregates via one repository per aggregate root in Clean Architecture. This Domain-Driven Design approach maintains consistency boundaries and prevents cross-aggregate invariants from becoming fragile.
iceflowerApply Domain-Driven Design patterns to model aggregates and bounded contexts.
duranserkanStandardize domain modeling with DRN.Domain patterns and EF Core configurations.
Maj3D10Implement Domain-Driven Design tactical patterns for .NET applications.
codewithmukeshEnforce aggregate boundaries and domain rules in .NET C# domain models.
