domain-modeling

Installation
SKILL.md

Contract

  • Input: problem or task defined by the skill body.
  • Output: Markdown artifact or structured result with completion criteria met.
  • Side effects: none (design/review/documentation only unless explicitly stated).
  • Dependencies: none (self-contained unless linked to other skills).
  • Stop condition: all process steps completed; artifact saved; criteria checked.
  • Risk: low.
  • Boundary: produces reasoning or documentation artifacts; does not modify external systems unless explicitly instructed.

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

Contract

Installs
2
First Seen
Sep 7, 2026
domain-modeling — quantumquirkxyz/skills-quirk