domain-modeling

Topics in the source

• Domain Modeling
• File structure
• During the session
• Challenge against the glossary
• Sharpen fuzzy language
• Discuss concrete scenarios
• Cross-reference with code
• Update GLOSSARY.md inline

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.) Most repos have a single context: If a GLOSSARY-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 GLOSSARY.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed. 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?" 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." When domain relationships are being discussed, stress-test them with specific scenarios. Inven

This is an excerpt. Refer to the complete source and its current requirements.