Verified:GitHub

domain-driven-design

Assesses the viability of Domain-Driven Design for complex business domains.

2|Updated Mar 15, 2025

Search Tags:#domain modeling #ddd #strategic design #bounded context #ubiquitous language #event-driven architecture #tactical patterns

Ready to run

npx skills add https://github.com/dandudzi/dotfiles --skill domain-driven-design-dandudzi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-driven-design
Source: https://github.com/dandudzi/dotfiles/tree/main/dot_claude/skills/domain-driven-design
Command: npx skills add https://github.com/dandudzi/dotfiles --skill domain-driven-design-dandudzi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps determine if Domain-Driven Design (DDD) is suitable for a complex business domain and guides the application of its principles, ensuring better alignment between software and business needs.

Core Features & Use Cases

DDD Viability Assessment: Evaluates domain complexity, team size, ownership, and change frequency to recommend DDD adoption.
Strategic Design Guidance: Routes to sub-skills for defining subdomains, bounded contexts, and ubiquitous languages.
Tactical Pattern Implementation: Guides the creation of aggregates, value objects, and domain events.
Event-Driven Architecture Integration: Facilitates integration with event sourcing and CQRS patterns.
Use Case: When starting a new large-scale project with complex business rules, use this skill to decide if DDD is appropriate and to initiate the strategic design phase.

Quick Start

Use the domain-driven-design skill to assess if DDD is viable for a new insurance underwriting system.

Frequently Asked Questions about domain-driven-design

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

FAQPage Schema

How do I know if domain-driven design is viable for my complex business domain?▼

Domain-driven design viability is assessed by evaluating domain complexity, team size, ownership, and change frequency. This analysis determines whether DDD adoption will effectively align your software architecture with complex business needs before committing to strategic design.

What is the best way to define bounded contexts and ubiquitous languages for a new system?▼

Defining bounded contexts and ubiquitous languages requires strategic design guidance that routes to specialized sub-skills. This approach establishes clear subdomain boundaries and shared terminology to align software models with business domains effectively.

How do I implement tactical patterns like aggregates and value objects in DDD?▼

Implementing tactical patterns like aggregates and value objects requires structured guidance for domain model creation. This Skill routes to tactical design sub-skills that support defining these patterns alongside domain events to enforce business rules.

Can I integrate event sourcing and CQRS patterns with event-driven architecture in DDD?▼

Integrating event sourcing and CQRS patterns with event-driven architecture is fully supported within DDD. The Skill facilitates routing to specialized sub-skills that connect tactical domain events with these architectural patterns for scalable system design.

Do I need domain-driven design for a large-scale project with complex business rules?▼

Domain-driven design is recommended for large-scale projects with complex business rules to ensure alignment between software and business needs. Use viability assessment to confirm DDD suitability and initiate the strategic design phase for such projects.

When should I not use domain-driven design for software architecture?▼

Domain-driven design should not be used when domain complexity, team size, or change frequency are insufficient to justify its overhead. The viability assessment evaluates these factors to prevent unnecessary DDD adoption in simpler business domains.