ddd-architect

Name: ddd-architect
Availability: InStock
Author: Olivier

Map subdomains, bounded contexts, and integration patterns for DDD projects.

Updated Aug 23, 2026

Search Tags:#ddd #bounded-context #hexagonal-architecture #architecture-design #context-map #subdomain

Ready to run

npx skills add https://github.com/tojoolivier/claude-config --skill ddd-architect-tojoolivier

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides systematic guidance to translate domain terminology into a coherent strategic architecture, producing subdomain classifications, bounded contexts, and context maps that align with Hexagonal Architecture.

Core Features & Use Cases

Subdomain classification into Core, Supporting, and Generic
Define bounded contexts with owned glossary terms and inside/outside boundaries
Draw Context Maps with integration patterns and rationales
Hexagonal Architecture layer map showing driving, application, domain, and driven sides
Use case: when starting a new domain, generate a complete strategic design to guide implementation and integration

Quick Start

Generate a Phase 2 Context Map and bounded contexts from the PM glossary and domain hints.

Frequently Asked Questions about ddd-architect

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

FAQPage Schema

How do I map subdomains and bounded contexts for DDD architecture?▼

To design strategic DDD architecture, you classify subdomains into Core, Supporting, and Generic, then define bounded contexts with owned glossary terms and boundaries. It produces a context map specifying integration patterns aligned with Hexagonal Architecture.

What is a context map in domain-driven design and when do I need one?▼

A context map in domain-driven design is a strategic diagram that defines bounded context interactions and integration patterns. You need one when starting a new complex domain to guide implementation and align driving, application, domain, and driven Hexagonal layers.

How do I classify subdomains into core, supporting, and generic categories?▼

You classify subdomains into core, supporting, and generic categories by analyzing domain terminology and business value to determine strategic differentiation. This classification defines bounded context boundaries and guides the mapping of Hexagonal Architecture layers.

Does DDD architecture work with Hexagonal Architecture layer mapping?▼

Yes, DDD architecture works with Hexagonal Architecture by mapping bounded contexts to driving, application, domain, and driven sides. This integration defines clear boundaries and specifies how owned glossary terms interact across system layers.

What are the limitations of strategic DDD for complex domain design?▼

The limitation of strategic DDD for complex domain design is that it focuses solely on high-level subdomain classification, context mapping, and integration patterns. It does not handle tactical implementation details like entity design or aggregate implementation.