A Claude Code plugin owning DDD practice skills. It holds the stewardship disciplines of domain-driven design, independent of any one planning or workshop workflow.
| Skill | What it does |
|---|---|
/domain-driven-design:curate-language |
Actively maintains the consuming project's ubiquitous-language glossary: resolves ambiguous or overloaded terms, records canonical language and rejected synonyms, and routes entries to already-known bounded contexts. It never discovers boundaries itself. |
Deferred: context-mapping and aggregate-design join this plugin when those
practices materialize as skills.
Bounded-context discovery is out of scope here. Workshop-driven discovery lives in
the standalone event-storming plugin, which curate-language soft-routes to when
boundaries are missing.
- Reads your conventions, assumes none. Glossary filename, location, shape, and context map come from the consuming project; where none exist, creation is lazy and discovery-first. It never prescribes a universal filename.
- No
userConfig, no persistent state, no network.
/plugin marketplace add melodic-software/claude-code-plugins
/plugin install domain-driven-design@melodic-softwareThe planning plugin invokes /domain-driven-design:curate-language when it is installed, and
records resolved terms in its own artifacts when it is not. Install this plugin alongside
planning to get glossary stewardship inside the planning workflow.
MIT (SPDX-License-Identifier: MIT).