Agent skill · sammcj
domain-model
Actively build and sharpen a project's domain model - challenge terms against the glossary, stress-test boundaries with scenarios, cross-reference against the code, and record the glossary (CONTEXT.md) and decisions (ADRs) the moment they crystallise. Use when you are changing the domain model itself, pinning down a ubiquitous language, or recording an architectural decision.
What it needs
About 2k tokens when loaded.
What this skill does
Domain modelling 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 CONTEXT.md for vocabulary is not this skill; that is a one-line habit any skill can do. This skill is for when you are changing the model, not just consuming it. File structure Most repos have a single context: If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives: Create files lazily - only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it 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 CONTEXT.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 CONTEXT.md inline When a term is resolved, update CONTEXT.md right there. Don't batch these up - capture them as they happen. Use the format in CONTEXT-FORMAT.md. CONTEXT.md should be totally devoid of implementation details. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sammcj/domain-model--ea0cd6