Domain Modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Domain Modeling
Actively build and sharpen the project's domain model as you design.
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.
Sharpen fuzzy language
When the user uses vague or overloaded terms, propose a precise canonical term.
Discuss concrete scenarios
When domain relationships are being discussed, stress-test them with specific scenarios.
Cross-reference with code
When the user states how something works, check whether the code agrees.
Update CONTEXT.md inline
When a term is resolved, update CONTEXT.md right there. Don't batch these up — capture them as they happen.
CONTEXT.md should be totally devoid of implementation details. It is a glossary and nothing else.
Offer ADRs sparingly
Only offer to create an ADR when all three are true:
- Hard to reverse — the cost of changing your mind later is meaningful
- Surprising without context — a future reader will wonder "why did they do it this way?"
- 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.