ddd-strategic-design

Map business domains and define bounded contexts with DDD strategic patterns.

2|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/dandudzi/dotfiles --skill ddd-strategic-design-dandudzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/dandudzi/dotfiles/tree/main/dot_claude/skills/ddd-strategic-design
Command: npx skills add https://github.com/dandudzi/dotfiles --skill ddd-strategic-design-dandudzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps in clearly defining and organizing complex business domains by applying Domain-Driven Design (DDD) strategic patterns, leading to better software architecture and communication.

Core Features & Use Cases

  • Subdomain Classification: Categorize business areas into Core, Supporting, or Generic domains to guide investment and design intensity.
  • Bounded Context Definition: Identify and delineate explicit boundaries for domain models, ensuring consistency and manageable scope.
  • Ubiquitous Language: Establish a shared vocabulary between technical and business stakeholders for precise communication.
  • Context Mapping: Define relationships and integration patterns between different bounded contexts.
  • Use Case: When starting a new project or refactoring an existing system, use this Skill to map out the business landscape, identify key domains, and define how different parts of the system will interact.

Quick Start

Use the ddd-strategic-design skill to help classify the 'order management' 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 define bounded contexts for a complex business domain?

Bounded contexts delineate explicit boundaries for domain models to ensure consistency and manageable scope. You define them by classifying subdomains as core, supporting, or generic, which guides investment and aligns software architecture with business strategy.

What is the best way to establish a ubiquitous language between technical and business stakeholders?

A ubiquitous language establishes a shared vocabulary between technical and business stakeholders for precise communication. It is defined by applying Domain-Driven Design strategic patterns to map business domains and align software models with business strategy.

How do I classify subdomains as core, supporting, or generic during strategic design?

Subdomain classification categorizes business areas into core, supporting, or generic domains to guide investment and design intensity. This strategic design step ensures you focus architectural resources on the areas providing the most competitive business value.

How does context mapping work for integrating bounded contexts?

Context mapping defines relationships and integration patterns between different bounded contexts, such as Anti-Corruption Layers or shared kernels. It establishes how distinct domain models interact, ensuring system integration aligns with the overall domain-driven design.

When do I need strategic domain-driven design patterns for software architecture?

You need strategic domain-driven design patterns when starting a new project or refactoring an existing system to map the business landscape. It helps identify key domains, define bounded contexts, and align software architecture with business strategy.