Domain Driven 디자인
원문: domain-driven-design
Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.
무엇을 하나요
Domain Driven Design Use this skill when You need to model a complex business domain with explicit boundaries. You want to decide whether full DDD is worth the added complexity. You need to connect strategic design decisions to implementation patterns. You are planning CQRS, event sourcing, sagas, or projections from domain needs. Do not use this skill when The problem is simple CRUD with low business complexity. You only need localized bug fixes. There is no access to domain knowledge and no proxy product expert. Instructions 1. Run a viability check before committing to full DDD. 2. Produce strategic artifacts first: subdomains, bounded contexts, language glossary. 3. Route to specialized …
실행 시 본인 API 키(BYOK)로 동작하며, 모델 비용은 사용자 계정에서 직접 결제됩니다.