ddd-strategic-design

Defines bounded contexts, subdomains, and ubiquitous language for domain-driven design.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill ddd-strategic-design-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/ddd-strategic-design
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill ddd-strategic-design-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams splitting monoliths or designing new systems often draw service boundaries along technical layers, producing distributed monoliths, shared databases, and conflicting terminology. This Skill guides the strategic side of Domain-Driven Design so boundaries align with business capabilities and team ownership. ## Core Features & Use Cases - Subdomain Classification: Categorizes capabilities as Core, Supporting, or Generic to drive build-vs-buy decisions. - Bounded Context & Context Mapping: Defines context boundaries by consistency scope, team ownership, and language, then maps relationships (Shared Kernel, Customer-Supplier, Anti-Corruption Layer, Open Host Service). - Ubiquitous Language Glossary: Produces a term glossary with banned synonyms enforced across code, database columns, and API fields. - Use Case: When decomposing a monolith into services, use this Skill to extract domain capabilities, classify subdomains, define bounded contexts, and record each boundary decision as an ADR before writing any code. ## Quick Start Ask the agent to apply DDD strategic design to define bounded contexts and a ubiquitous language glossary for your domain, for example an e-commerce order and logistics system.

Frequently Asked Questions about ddd-strategic-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define bounded contexts in domain-driven design?▼

Define bounded contexts by grouping concepts that share transactional consistency, team ownership, and meaning. Split where the same term carries different meanings, and align each context with a team that can deploy and operate it independently.

What is the difference between core, supporting, and generic subdomains?▼

Core subdomains differentiate the business and must be built in-house. Supporting subdomains are necessary but not differentiating, suiting internal or custom solutions. Generic subdomains are common problems best solved with off-the-shelf products or SaaS.

When should I use event sourcing with DDD?▼

Use event sourcing when you need a complete audit log, time-travel state reconstruction, or event-based integration. Apply it only to Core subdomains, since it adds schema versioning complexity and typically requires CQRS for queries.

What context mapping patterns exist between bounded contexts?▼

Common patterns include Shared Kernel, Customer-Supplier, Conformist, Anti-Corruption Layer, Open Host Service, and Published Language. Choose based on team relationships and how much coupling between models you can tolerate.

When should I not use DDD strategic design?▼

Skip it when the domain model is stable with clear boundaries, when only tactical code patterns are needed, or for pure infrastructure and UI work. It also cannot infer business truth without stakeholder input.