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.)

Shared artifacts and invocation modes

Read the project artifact contract before selecting files. In read-only work, resolve and consume context without edits. In design or implementation work, persist settled vocabulary, relationships, and qualifying decisions in the configured artifacts. References below to GLOSSARY.md mean the selected vocabulary artifact; preserve an existing legacy name rather than creating a duplicate.

File structure

Most repos have a single context: