Model C++ domain concepts and distinguish entities from value objects.
npx skills add https://github.com/13eholder/Modern-Cpp-Skills --skill m09-domain-13eholder
Please help me install this Agent Skill. Skill: m09-domain Source: https://github.com/13eholder/Modern-Cpp-Skills/tree/main/m09-domain Command: npx skills add https://github.com/13eholder/Modern-Cpp-Skills --skill m09-domain-13eholder
This Skill helps avoid common domain-design mistakes in C++ such as confusing identity with value, accidentally enabling object slicing, exposing implementation details in headers, and allowing invalid object states through public fields.
Design a User type by making the ID a strong type, treating Name and Address as value objects, deleting the User copy constructor while allowing move, encapsulating invariants in private members exposed through methods, and owning child entities with unique_ptr.
High-intent search queries and answers about installing and using this skill.
In C++ domain models, entities should have deleted copy constructors and be identified by strong typed IDs, while value objects are copyable types representing concepts like Name or Address without identity.
Use the Pimpl idiom in C++ headers to reduce compile-time coupling and hide implementation details when designing business-facing domain models where encapsulating private invariants behind public methods is required.
Define aggregate roots in C++ by owning child entities with unique_ptr or vectors, establishing clear ownership boundaries that prevent invalid object states and accidental object slicing.
Prevent object slicing and invalid states in C++ domain design by deleting copy operations on entities, keeping data members private, and exposing invariants only through public method interfaces.
Avoid raw integers for entity IDs in C++ domain-driven design; instead, use strong typed IDs to prevent identity errors and distinguish entities from value objects at compile time.
Design a repository interface for a C++ aggregate by defining a User type with a strong UserId, treating Name and Address as value objects, and exposing persistence interfaces for the aggregate root.
jorgeochipinti97Model business domains with DDD patterns to define entities, value objects, aggregates, and domain events.
AGIBuildImplement Domain-Driven Design tactical patterns in C# for domain models.
Ronin15Diagnose SDL3 HammerEngine dependency health with circular dependency and layer violation reports.
ArogyaReddyTeach DOTS-based ECS patterns for data-oriented Unity game development.
