domain-driven-design
SolidDDD tactical patterns for complex business modeling including entities, value objects, aggregates, domain services, repositories, specifications, and bounded contexts. Python dataclass implementations with TypeScript alternatives. Use when building rich domain models, enforcing invariants, or separating domain logic from infrastructure.
Install
Quality Score: 86/100
Skill Content
Details
- Author
- yonatangross
- Repository
- yonatangross/orchestkit
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
design_data_model
Use this skill when designing domain models, entities, value objects, aggregates, or the conceptual structure of the business domain — separate from database schema or ORM concerns. Triggers on: "how should I model this domain?", "what entities do I need?", "design the domain model for X", "should this be an entity or value object?", "what are the aggregates?", "how should these concepts relate?", "DDD domain modeling", "model this business concept in code". Also use when translating requirements into objects and relationships before writing any code.
principle-ddd
Domain-Driven Design (DDD) — bounded contexts, aggregates, entities, value objects, ubiquitous language, domain events, context map, anti-corruption layer, and repository pattern. Auto-load when modeling a complex domain, splitting services, deciding service boundaries, microservice splits, designing aggregates, or aligning code with business language.
ddd
Domain-Driven Design patterns for .NET — aggregates, value objects, strongly-typed IDs, domain events, repositories, and layer rules.