Claude Cursor Skill

domain-modeling

Build and sharpen a project's domain model. Use when discussing codebase terminology, resolving a vague or overloaded word, stress-testing how domain concepts relate, writing or editing a GLOSSARY.md, or recording or editing an ADR.

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download svyatov-supermatt-skills_domain-modeling-6b893bc.zip · 4 KB

Install

skills CLI npx skills add https://github.com/svyatov/supermatt/tree/main/skills/domain-modeling
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install svyatov-supermatt@llmmart
Git git clone https://github.com/svyatov/supermatt.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole svyatov/supermatt collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Domain Modeling

Actively build and sharpen the project's domain model as you design. This is the active discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely reading GLOSSARY.md for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

File structure

Read docs/agents/domain.md first if it exists. Its configured glossary, map, and ADR paths take precedence, including older names such as CONTEXT.md and CONTEXT-MAP.md; read the configured map for per-context paths. Use the defaults below only where no path is configured. Throughout this skill and its format references, GLOSSARY.md, GLOSSARY-MAP.md, and docs/adr/ mean those resolved paths. Preserve existing names; do not rename or migrate files.

Most repos have a single context:

/
├── GLOSSARY.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If the resolved glossary map exists, the repo has multiple contexts. The map points to where each one lives:

/
├── GLOSSARY-MAP.md
├── docs/
│   └── adr/                          ← system-wide decisions
├── src/
│   ├── ordering/
│   │   ├── GLOSSARY.md
│   │   └── docs/adr/                 ← context-specific decisions
│   └── billing/
│       ├── GLOSSARY.md
│       └── docs/adr/

Create files at the resolved paths lazily: the glossary only when the first term is resolved, and an ADR directory only when the first ADR is needed.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in GLOSSARY.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?"

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things."

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?"

Update GLOSSARY.md inline

When a term is resolved, update GLOSSARY.md right there. Don't batch these up: capture them as they happen. Use the format in GLOSSARY-FORMAT.md.

GLOSSARY.md should be totally devoid of implementation details. Do not treat GLOSSARY.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

  1. Hard to reverse: the cost of changing your mind later is meaningful
  2. Surprising without context: a future reader will wonder "why did they do it this way?"
  3. The result of a real trade-off: there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.

Files (supermatt)
  • agents
    • openai.yaml 112 B
      Loading…
  • ADR-FORMAT.md 2.9 KB
    Loading…
  • GLOSSARY-FORMAT.md 2.8 KB
    Loading…
  • SKILL.md 3.8 KB
    ---
    name: domain-modeling
    description: Build and sharpen a project's domain model. Use when discussing codebase terminology, resolving a vague or overloaded word, stress-testing how domain concepts relate, writing or editing a GLOSSARY.md, or recording or editing an ADR.
    license: MIT
    ---
    
    # Domain Modeling
    
    Actively build and sharpen the project's domain model as you design. This is the *active* discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `GLOSSARY.md` for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)
    
    ## File structure
    
    Read `docs/agents/domain.md` first if it exists. Its configured glossary, map, and ADR paths take precedence, including older names such as `CONTEXT.md` and `CONTEXT-MAP.md`; read the configured map for per-context paths. Use the defaults below only where no path is configured. Throughout this skill and its format references, `GLOSSARY.md`, `GLOSSARY-MAP.md`, and `docs/adr/` mean those resolved paths. Preserve existing names; do not rename or migrate files.
    
    Most repos have a single context:
    
    ```
    /
    ├── GLOSSARY.md
    ├── docs/
    │   └── adr/
    │       ├── 0001-event-sourced-orders.md
    │       └── 0002-postgres-for-write-model.md
    └── src/
    ```
    
    If the resolved glossary map exists, the repo has multiple contexts. The map points to where each one lives:
    
    ```
    /
    ├── GLOSSARY-MAP.md
    ├── docs/
    │   └── adr/                          ← system-wide decisions
    ├── src/
    │   ├── ordering/
    │   │   ├── GLOSSARY.md
    │   │   └── docs/adr/                 ← context-specific decisions
    │   └── billing/
    │       ├── GLOSSARY.md
    │       └── docs/adr/
    ```
    
    Create files at the resolved paths lazily: the glossary only when the first term is resolved, and an ADR directory only when the first ADR is needed.
    
    ## During the session
    
    ### Challenge against the glossary
    
    When the user uses a term that conflicts with the existing language in `GLOSSARY.md`, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?"
    
    ### Sharpen fuzzy language
    
    When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things."
    
    ### Discuss concrete scenarios
    
    When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
    
    ### Cross-reference with code
    
    When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?"
    
    ### Update GLOSSARY.md inline
    
    When a term is resolved, update `GLOSSARY.md` right there. Don't batch these up: capture them as they happen. Use the format in [GLOSSARY-FORMAT.md](./GLOSSARY-FORMAT.md).
    
    `GLOSSARY.md` should be totally devoid of implementation details. Do not treat `GLOSSARY.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
    
    ### Offer ADRs sparingly
    
    Only offer to create an ADR when all three are true:
    
    1. **Hard to reverse**: the cost of changing your mind later is meaningful
    2. **Surprising without context**: a future reader will wonder "why did they do it this way?"
    3. **The result of a real trade-off**: there were genuine alternatives and you picked one for specific reasons
    
    If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.