If you're building line-of-business apps in C# and want to move beyond anemic CRUD models, this covers the tactical DDD patterns that actually matter: aggregate roots that enforce invariants, value objects using records, domain events, and repository contracts. The aggregate design rules table is worth the price of admission alone (reference other aggregates by ID only, one aggregate per transaction). It stays focused on the pure domain layer and explicitly punts on EF Core mapping, validation, and messaging infrastructure. The Money and Order examples show how to use private setters, factory methods, and collection encapsulation to keep business rules inside the model rather than scattered across services. Good fit if you're tired of services that are just database update scripts with extra steps.
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-domain-modeling