AGENT SKILL

domain-modeling

Build and sharpen domain terms and relationships, or write/edit the domain glossary in CONTEXT.md. Reading existing vocabulary alone does not require this skill.

License 许可
MIT
所属仓库
BetoFrega/skills
最近更新
2026-11-14
Stars
★ 0
Forks
0

01 前言 Front Matter

name
domain-modeling
description
Build and sharpen domain terms and relationships, or write/edit the domain glossary in CONTEXT.md. Reading existing vocabulary alone does not require this skill.

02 资源文件 4

03 SKILL.md 正文

Domain Modeling

Challenge terminology and relationships; capture resolved glossary terms and architectural choices as they crystallize.

File structure

Resolve domain configuration, including external files. Honor configured glossary, context map, and ADR destinations. Defaults: root CONTEXT.md and docs/adr/ for one context; root CONTEXT-MAP.md identifies multiple contexts, their glossaries, and context-specific ADR locations, with docs/adr/ for system-wide choices. Create a glossary at its first resolved term and an ADR directory at its first record.

During the session

Challenge against the glossary

Surface conflicting use immediately: the glossary says X while the discussion means Y. Resolve the distinction openly before changing terminology.

Sharpen fuzzy language

Propose precise canonical terms for vague or overloaded words.

Discuss concrete scenarios

Stress-test relationships and concept boundaries with specific edge-case scenarios. Explain how proposed terms and relationships change responsibilities, rules, and behavior. For consequential domain/product choices, compare viable alternatives through recommend and obtain the user's decision before adopting them; prior approval remains valid within scope. Edit the glossary only for meaning that is already settled.

Cross-reference with code

Check behavioral claims against code and raise contradictions for resolution. Code shows what was implemented, which may differ from approved intent.

Update CONTEXT.md inline

Capture each resolved term immediately using CONTEXT-FORMAT.md; do not batch it. Keep CONTEXT.md exclusively a glossary, without implementation details, specs, scratch notes, or implementation decisions. Report local glossary/map changes through document delivery.

Record architectural decisions

Use write-adr for admission, authoring, format, and updates.

Product behavior and policy

Read affected canonical contracts through consolidate. For approved rule, permission, state, or exception changes, use its decision and catalogue routes within session documentation authority. Keep definitions in the glossary and link behavior to its product authority.

04 同仓库更多 Skills