Files
antigravity-skills-reference/skills/ddd-strategic-design/SKILL.md
sck_0 aa71e76eb9 chore: release 6.5.0 - Community & Experience
- Add date_added to all 950+ skills for complete tracking
- Update version to 6.5.0 in package.json and README
- Regenerate all indexes and catalog
- Sync all generated files

Features from merged PR #150:
- Stars/Upvotes system for community-driven discovery
- Auto-update mechanism via START_APP.bat
- Interactive Prompt Builder
- Date tracking badges
- Smart auto-categorization

All skills validated and indexed.

Made-with: Cursor
2026-02-27 09:19:41 +01:00

1.5 KiB

name, description, risk, source, tags, date_added
name description risk source tags date_added
ddd-strategic-design Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains. safe self [ddd, strategic-design, bounded-context, ubiquitous-language] 2026-02-27

DDD Strategic Design

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.

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.

Required artifacts

  • Subdomain classification table
  • Bounded context catalog
  • Glossary with canonical terms
  • Boundary decisions with rationale

Examples

Use @ddd-strategic-design to map our commerce domain into bounded contexts,
classify subdomains, and propose team ownership.

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.