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
- 参考文档ADR-FORMAT.md232 B
- 参考文档agents/openai.yaml101 B
- 参考文档CONTEXT-FORMAT.md2.5 KB
- 许可证LICENSE1.0 KB
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
writing-for-humans
Load before writing any reader-facing text, including messages, and follow its rules as you write. Also use to rewrite or audit existing prose for plain language, clarity, readability, or actionability.
writing-for-agents
Write agent-facing documents. Use when creating or editing skills, AGENTS.md, or CLAUDE.md.
write-adr
Write, revise, or supersede architecture decision records (ADRs) documenting an architectural choice and its rationale.
wizard
Wizard scripts for human-only provisioning, credential/CI setup, unfamiliar dashboards, migrations, or cutovers; use only for steps the agent cannot perform.
verify
Check whether the current task's claimed outcome is confirmed.
verb-tense
Choose verb tense and mood by when each event happens and how certain it is. Use when writing or reviewing any text, and when a reader asks for a tense review.