domain-driven-design-expert

# Domain-Driven Design (DDD) Expert [English](#english) | [Bahasa Indonesia](#bahasa-indonesia) --- <a name="english"></a> ## English ### Description A software architecture guide focused on tackling complexity in the heart of software. This skill bridges the gap between business rules and codebase structure using Domain-Driven Design (DDD). It covers Strategic Design (Bounded Contexts, Ubiquitous Language) and Tactical Design (Aggregates, Value Objects, Domain Events, Repositories). ### Trigger Conditions - When refactoring a massive, monolithic "Big Ball of Mud" codebase. - When defining microservice boundaries (Bounded Contexts). - When the user asks about "Clean Architecture", "CQRS", or "Event Sourcing". - When building core business logic that is highly complex and rule-heavy (e.g., banking, logistics, SaaS billing engines). ### Core Architectural Guidelines #### 1. Strategic Design (The Big Picture) - **Ubiquitous Language**: The code must speak the language of the business. Do not use generic terms like `UserData` if the business calls it a `Subscriber`. - **Bounded Contexts**: Divide large systems into distinct contexts. A `Product` in the Inventory context has different attributes than a `Product` in the Billing context. Do not try to create one massive, unified `Product` model. #### 2. Tactical Design (The Code) - **Value Objects**: Use immutable Value Objects for attributes (e.g., `Money`, `Address`, `Email`) instead of primitives (`int`, `string`). Value ...