Back to Details

ddd-strategic-design

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

DDD Strategic Design

DDD战略设计

Use this skill when

适用场景

  • Defining core, supporting, and generic subdomains.
  • Splitting a monolith or service landscape by domain boundaries.
  • Aligning teams and ownership with bounded contexts.
  • Building a shared ubiquitous language with domain experts.
  • 定义核心子域、支撑子域和通用子域。
  • 按领域边界拆分单体应用或服务架构。
  • 使团队及职责与限界上下文对齐。
  • 与领域专家共建共享通用语言。

Do not use this skill when

不适用场景

  • The domain model is stable and already well bounded.
  • You need tactical code patterns only.
  • The task is purely infrastructure or UI oriented.
  • 领域模型稳定且已完成良好的边界划分。
  • 仅需要战术代码模式。
  • 任务纯面向基础设施或UI。

Instructions

操作步骤

  1. Extract domain capabilities and classify subdomains.
  2. Define bounded contexts around consistency and ownership.
  3. Establish a ubiquitous language glossary and anti-terms.
  4. Capture context boundaries in ADRs before implementation.
If detailed templates are needed, open 
references/strategic-design-template.md
.
  1. 提取领域能力并对子域进行分类。
  2. 围绕一致性和职责定义限界上下文。
  3. 建立通用语言词汇表及禁用术语。
  4. 在实施前将上下文边界记录到ADR中。
如需详细模板，请打开
references/strategic-design-template.md
。

Required artifacts

所需工件

  • Subdomain classification table
  • Bounded context catalog
  • Glossary with canonical terms
  • Boundary decisions with rationale
  • 子域分类表
  • 限界上下文目录
  • 包含标准术语的词汇表
  • 带决策依据的边界决策文档

Examples

示例

text
Use @ddd-strategic-design to map our commerce domain into bounded contexts,
classify subdomains, and propose team ownership.
text
使用@ddd-strategic-design将我们的电商领域映射为限界上下文，对子域进行分类，并提出团队职责划分方案。

Limitations

局限性

  • This skill does not produce executable code.
  • It cannot infer business truth without stakeholder input.
  • It should be followed by tactical design before implementation.
  • 该技能不生成可执行代码。
  • 若无利益相关者输入，无法推断业务事实。
  • 实施前需后续进行战术设计。