ddd-skill

Formalize domain boundaries into bounded contexts, aggregates, and event schemas.

Updated Mar 2, 2026

Search Tags:#architecture #ddd #domain-driven-design #bounded-context #aggregates #domain-events #context-map

Ready to run

npx skills add https://github.com/dacy/architect-skill --skill ddd-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ddd-skill
Source: https://github.com/dacy/architect-skill/tree/main/.claude/skills/ddd-skill
Command: npx skills add https://github.com/dacy/architect-skill --skill ddd-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain-driven design helps teams align solution architecture with business intent by modeling boundaries, languages, and events to drive service decomposition, APIs, and event contracts.

Core Features & Use Cases

Identify and define core domains, subdomains, and bounded contexts.
Define aggregates, entities, and value objects within each context.
Document ubiquitous language and map context relationships to guide architecture decisions.

Quick Start

Provide a business requirement and let the skill produce a domain design and context map for solution boundaries.

Frequently Asked Questions about ddd-skill

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

FAQPage Schema

How do I identify bounded contexts and domain events for microservice architecture?▼

You define bounded contexts by submitting business requirements to produce a domain design that maps subdomains, aggregates, entities, and domain events into cohesive service boundaries and API contracts.

What is the best way to drive service decomposition using domain-driven design?▼

Domain-driven design drives service decomposition by modeling core domains and ubiquitous language to formalize bounded context relationships, producing a cohesive context map and API implementation plan.

How do I model aggregates and entities within a bounded context?▼

Model aggregates and entities within a bounded context by applying domain-modeling requirements that identify core domain contexts, aggregates, and domain events to produce a context map for architecture decisions.

When do I need a context map for API contracts and event schemas?▼

A context map is needed for API contracts and event schemas when aligning solution architecture with business intent across multiple subdomains and bounded contexts to drive microservice decomposition.

Can I use domain-driven design to formalize microservice boundaries from business requirements?▼

Domain-driven design formalizes microservice boundaries by taking a business requirement to produce a domain design specifying core domains, bounded contexts, aggregates, and domain events for implementation planning.