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

This skill owns domain vocabulary and durable decision records. shape-design owns feature behavior and requirements. An ADR records why a hard-to-reverse decision was made; it is not a specification or implementation plan.

This skill is the acting half of the vocabulary and decisions parts of the planning-contract capture checkpoint (Contract version: 1): shaping calls it when resolved terms or qualifying decisions need capture. Load that contract for classification, scoped authority, and handoff rules; if it is not installed, stop and request installing planning-contract rather than proceeding on inherited or invented rules.

File structure

Most repos have a single context: