Planning skill that interrogates your use case before any code is written, then recommends the right Twilio Conversations stack — ConversationRelay, Memory, Intelligence, Orchestrator, TaskRouter — and the implementation skills to follow.
Domain Modeling Skill
Matt Pocock's skill for actively building a project's domain model while you design: it challenges terms against GLOSSARY.md, sharpens vague language, stress-tests concepts with scenarios, checks claims against the code and records ADRs sparingly.
Install
Other ways to install
About
- Challenges terms that conflict with the project's GLOSSARY.md
- Proposes precise canonical terms for vague or overloaded language
- Stress-tests domain relationships with invented edge-case scenarios
- Cross-checks the user's statements against the code
- Updates the glossary inline, with support for multi-context GLOSSARY-MAP.md repos
- Offers ADRs only for hard-to-reverse, surprising, real trade-off decisions
Domain Modeling is an engineering skill from Matt Pocock's mattpocock/skills collection. It is the active half of keeping a shared vocabulary for a codebase: not just reading the glossary, but changing the model as the design conversation happens. It loads when you discuss codebase terminology, write or edit a GLOSSARY.md, or record or edit an architecture decision record (ADR). It is also what the collection's grill-with-docs skill combines with grilling to produce docs during a design interview.
The skill describes where things live: a single GLOSSARY.md and docs/adr/ at the root for most repositories, or a GLOSSARY-MAP.md that points to per-context glossaries and ADR folders in a repo with several bounded contexts. Files are created lazily, only when there is something to write.
During a session the agent calls out a term that conflicts with the glossary, proposes one precise word for a vague or overloaded one (is an "account" a Customer or a User?), invents edge-case scenarios to force clear boundaries between concepts, and checks what the user says against the code, surfacing contradictions. Resolved terms go into the glossary straight away, in the bundled format, and the glossary stays free of implementation details. ADRs are offered only when a decision is hard to reverse, surprising without context and the result of a real trade-off; if any of the three is missing, there is no ADR. It needs no tools beyond file editing. MIT licensed.
SKILL.md
The instructions your agent loads, as published by Matt Pocock.
Related Skills
See all Domain Modeling alternativesSkill: Archify Architecture Diagrams
by tt-a1i
Turns plain-language requirements or pasted Mermaid into validated architecture, workflow, sequence, data-flow and lifecycle diagrams as self-contained interactive HTML.
Skill: SeeCode
by Aryan Utkarsh
Turn a short JSON spec into animated, explorable diagrams in 45 types, exported as HTML, SVG, PNG, GIF or MP4.
Skill: Diagram Design
by Cathryn Lavery
Agent skill that draws 40+ editorial diagram types as self-contained HTML and SVG, matched to your brand, with no Mermaid look.