skills.rest
iCesofT
iCesofTCOMMUNITY
Explore all skills by this author →
Website𝕏@fjahijadoGitHub

ddd-strategic-design

Identify core subdomains and bounded contexts to create a ubiquitous language glossary.

1|1|Updated Apr 16, 2026
Search Tags:#ddd#domain-driven-design#bounded-context#ubiquitous-language#subdomains
One-click install
npx skills add https://github.com/iCesofT/awesome-ai --skill ddd-strategic-design-icesoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/iCesofT/awesome-ai/tree/main/agents/skills/ddd-strategic-design
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill ddd-strategic-design-icesoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Aligns business domain complexity with software architecture by defining strategic subdomains, bounded contexts, and ubiquitous language.

Core Features & Use Cases

  • Define core, supporting, and generic subdomains for complex domains.
  • Map bounded contexts to ownership and data boundaries.
  • Create a ubiquitous-language glossary to unify stakeholder concepts.
  • Produce ADR-ready context boundaries for implementation planning.

Quick Start

Identify core subdomains, define bounded contexts, and draft a ubiquitous language glossary for the domain.

Frequently Asked Questions about ddd-strategic-design

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

FAQPage Schema
How do I identify bounded contexts for a complex business domain?▼

To identify bounded contexts for a complex business domain, you isolate core, supporting, and generic subdomains to define ownership and data boundaries. This produces a structured bounded-context catalog with rationale for implementation planning.

What is ubiquitous language in domain-driven design and when do I need it?▼

Ubiquitous language in domain-driven design is a shared glossary unifying stakeholder concepts across teams. You need it when aligning complex business domain terminology with software architecture to prevent translation errors between technical and domain experts.

How do I create a subdomain catalog for domain-driven design?▼

Creating a subdomain catalog for domain-driven design involves categorizing business capabilities into core, supporting, and generic subdomains. This classification defines strategic priorities, producing a structured catalog that informs bounded context mapping.

Does strategic domain-driven design work for team alignment and ADR planning?▼

Strategic domain-driven design works for team alignment and ADR planning by mapping bounded contexts to ownership boundaries. It produces ADR-ready context boundaries with rationale, ensuring structured implementation planning across complex domains.

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

Core subdomains carry the primary competitive differentiator, while supporting subdomains provide necessary but non-differentiating capabilities. Generic subdomains offer universally available functionality. Categorizing these clarifies strategic domain priorities.

Related Skills

Explore More Software Engineering Skills→
RamonsDkaRamonsDka
1

domain-identification-grouping

Identify business domains and group code components into domain-based groupings.

Community
Advanced
DhumitechDhumitech

ddd-strategic-design

Classify domain capabilities and subdomains into bounded contexts with ADR rationales.

Community
Intermediate
radkomihradkomih

ddd-refactor

Analyze codebases to identify DDD anti-patterns and generate a phased refactoring plan.

Community
Advanced
tyevanstyevans
14

storm-prep

Analyze codebases to discover domain events and output structured YAML.

Community
Advanced