ddd-strategic-design

Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language.

150|51|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/AratKruglik/claude-laravel --skill ddd-strategic-design-aratkruglik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-strategic-design
Source: https://github.com/AratKruglik/claude-laravel/tree/main/.claude/skills/ddd-strategic-design
Command: npx skills add https://github.com/AratKruglik/claude-laravel --skill ddd-strategic-design-aratkruglik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of designing large-scale software systems by providing a structured approach to defining domain boundaries, ensuring better modularity, team alignment, and maintainability.

Core Features & Use Cases

  • Subdomain Classification: Identifies and categorizes business capabilities into core, supporting, and generic subdomains.
  • Bounded Context Definition: Establishes clear boundaries for different parts of the business domain, aligning with team ownership.
  • Ubiquitous Language: Facilitates the creation of a shared vocabulary between technical teams and domain experts.
  • Use Case: When starting a new large project or refactoring a monolith, use this skill to define the strategic DDD artifacts, ensuring a solid foundation for development.

Quick Start

Use the ddd-strategic-design skill to map our e-commerce platform into bounded contexts and define the ubiquitous language for the checkout process.

Frequently Asked Questions about ddd-strategic-design

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

FAQPage Schema
What is strategic design in Domain-Driven Design and when do I need it?

Strategic design in Domain-Driven Design is defining subdomains, bounded contexts, and ubiquitous language to solve complex business domain modeling. You need it when starting large projects or refactoring monoliths to ensure modularity, team alignment, and maintainability.

How do I decompose a monolith using bounded contexts?

To decompose a monolith using bounded contexts, map business capabilities to clear domain boundaries aligning with team ownership. This process identifies core, supporting, and generic subdomains to establish a structured modular foundation for development.

How do I create a ubiquitous language for my domain experts and technical teams?

Creating a ubiquitous language requires clearly articulating business capabilities and their relationships. This establishes a shared vocabulary between technical teams and domain experts, directly mapping business domains to bounded contexts.

What is the best way to classify subdomains in software architecture?

The best way to classify subdomains in software architecture is categorizing business capabilities into core, supporting, and generic subdomains. This strategic design approach ensures better alignment of teams with domain boundaries.

Do I need clear business capability articulation to define domain boundaries?

Yes, you need clear articulation of business capabilities and their relationships to define domain boundaries. Without this prerequisite, establishing accurate bounded contexts and mapping domain boundaries for team alignment is not possible.