ddd-contexts

Design Bounded Contexts and Ubiquitous Language glossaries from subdomain classifications.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill ddd-contexts-100thieves-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-contexts
Source: https://github.com/100Thieves-team/plady-expert-skills/tree/main/.claude/skills/ddd-contexts
Command: npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill ddd-contexts-100thieves-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams practicing Domain-Driven Design struggle to translate classified subdomains into clear Bounded Context boundaries, leading to terminology conflicts, ambiguous data ownership, and inconsistent models across teams. ## Core Features & Use Cases - Context Boundary Design: Cluster capabilities into Bounded Context candidates using consistency and language boundaries, with explicit responsibilities and non-responsibilities. - Ubiquitous Language Glossary: Produce term definitions with business examples, synonyms, anti-terms, and conflict-resolution strategies per context. - Boundary ADRs: Record ownership, decision rationale, trade-offs, risks, and alternatives for every context boundary decision. - Use Case: After classifying subdomains (e.g., Core: Booking & Conflict Management), feed the classification table and event flows into this Skill to receive a context directory, glossary, anti-term list, and boundary ADRs. ## Quick Start Ask the AI to design Bounded Contexts and a Ubiquitous Language glossary from your subdomain classification table and event flow list.

Frequently Asked Questions about ddd-contexts

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

FAQPage Schema
How do I design Bounded Contexts in Domain-Driven Design?

Cluster capabilities using consistency boundaries and language boundaries as criteria, then define each context's responsibilities, core concepts, events, and data ownership. This Skill guides that process and outputs a context directory plus boundary ADRs.

What is a Ubiquitous Language glossary and how do I create one?

A Ubiquitous Language glossary defines each core domain term with a business example, owning context, synonyms, and anti-terms. Create one by defining terms per context and resolving same-name-different-meaning conflicts through translation or renaming.

What inputs does the ddd-contexts skill require?

It requires a subdomain classification table with a core domain declaration and event flows with hotspot annotations. Optional inputs include organizational information like team boundaries and terminology seeds.

When should I redesign Bounded Context boundaries?

Redesign boundaries when invariants span multiple contexts, when terminology conflict rates exceed 20 percent, or when aggregate boundaries contradict context boundaries. These are explicit backtrack triggers in the Skill.

How do I handle terminology conflicts across Bounded Contexts?

Resolve conflicts by providing translation strategies between contexts or renaming terms, and record each resolution in the glossary. Maintain an anti-term list covering generic technical words like Manager or Handler and ambiguous business terms.