30-SECOND BRIEF
What it does—and when it fits
Domain Modeling turns a codebase's ubiquitous language into an actively maintained engineering artifact. It records canonical terms in CONTEXT.md, uses CONTEXT-MAP.md for multiple bounded contexts, checks statements against code and scenarios, surfaces contradictions, and reserves ADRs for surprising, costly-to-reverse decisions with real tradeoffs.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/domain-modeling/~/.claude/skills/domain-modeling/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add mattpocock/skills --skill domain-modeling --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Define canonical language
Create a concise glossary that code, tests, and discussion can share.
Map bounded contexts
Separate terms and relationships when one repository contains multiple domain models.
Resolve contradictions
Compare prose, code, and concrete scenarios before declaring a domain rule.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to mattpocock/skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It documents language and decisions; it does not replace implementation design or domain-expert validation.
- Premature glossaries or ADRs can freeze vocabulary before the team understands the domain.
BEST FIT
Who it is for
Teams clarifying complex business domains
Maintainers reducing terminology drift
BEFORE YOU USE IT
Risks to review before use
Institutionalizing the wrong model
A confidently written canonical term can steer code and communication in the wrong direction. Ground entries in code and scenarios, record contradictions, and revise the glossary as understanding changes.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at mattpocock/skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.