Engineering
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.
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.
Actively build and sharpen the project's domain model as you design.
When the user uses a term that conflicts with the existing language in CONTEXT.md, call it out immediately.
When the user uses vague or overloaded terms, propose a precise canonical term.
When domain relationships are being discussed, stress-test them with specific scenarios.
When the user states how something works, check whether the code agrees.
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.
Only offer to create an ADR when all three are true:
If any of the three is missing, skip the ADR.