Guide Domain-Driven Design tactical patterns with TypeScript code examples.
npx skills add https://github.com/0r0loo/my-claude-code-toolkit --skill ddd-0r0loo
Please help me install this Agent Skill. Skill: ddd Source: https://github.com/0r0loo/my-claude-code-toolkit/tree/main/.claude/skills/DDD Command: npx skills add https://github.com/0r0loo/my-claude-code-toolkit --skill ddd-0r0loo
This Skill provides a comprehensive guide to Domain-Driven Design's tactical patterns, helping developers build robust, maintainable, and domain-centric software by clarifying complex modeling concepts.
Order aggregate is correctly modeled, its invariants are protected, and interactions with Customer and Product are managed via ID references.Consult the DDD skill for guidance on modeling a Product entity with Value Objects for Price and Dimensions.
High-intent search queries and answers about installing and using this skill.
Implement Domain-Driven Design tactical patterns in TypeScript by following detailed best practices and code examples for Aggregates, Entities, Value Objects, and Repositories. The guide ensures robust object modeling and state management within a layered architecture.
Modeling an Aggregate requires defining clear rules to protect its invariants and manage state. Best practices dictate referencing other aggregates like Customer or Product by ID, ensuring boundaries are respected and inter-aggregate communication is handled via Domain Events.
Use a Value Object for domain concepts without identity, like Price or Dimensions, and an Entity for objects with distinct lifecycles. The guide clarifies these Domain-Driven Design modeling concepts with TypeScript code snippets illustrating good and bad practices.
Inter-aggregate communication uses Domain Events for asynchronous notifications and Domain Services for stateless business logic. This approach maintains clear boundaries and decouples aggregates, ensuring maintainable, domain-centric software design.
A DDD layered architecture enforces dependency rules flowing from Presentation and Infrastructure towards the Application and Domain layers. This structure isolates domain logic, keeping the core business model maintainable and independent from infrastructure concerns.
spallempatiScaffold a .NET solution with Clean Architecture layers and dependency injection.
ResgridOrganize .NET applications into four-layer Clean Architecture projects.
Muath2000Audit database schemas, Drizzle ORM models, and persistence patterns.
89jobrienDesign Go applications with clean or hexagonal architecture and Domain-Driven Design.