domain-modeling

主动构建与精炼项目领域模型并记录术语与决策

主动梳理和打磨项目的 domain model，把术语、边界条件和设计决策写进词汇表或 ADR，确保团队用同一套 ubiquitous language。在要确定名词含义、记录架构决定或为其他技能提供领域上下文时使用。特点是会质疑模糊定义、补充边缘场景并随时更新文档，避免大家对同一概念有不同理解。

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

## File structure

Most repos have a single context:

```
/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/
```

If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts.