domain-modeling
Use when building or sharpening a project's domain model — challenging terminology, writing or editing GLOSSARY.md, or recording an ADR.
- License 许可
- MIT
- 所属仓库
- jratlee/FDI
- 最近更新
- 2026-10-19
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- domain-modeling
- author
- Matt Pocock (mattpocock/skills, MIT); adapted for Hermes
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "domain-modeling", "glossary", "adr", "terminology", "design-review" ], "related_skills": [ "engineering/grill-with-docs", "productivity/grilling" ] } }
- description
- Use when building or sharpening a project's domain model — challenging terminology, writing or editing GLOSSARY.md, or recording an ADR.
02 资源文件 4
- 许可证LICENSE1.0 KB
- 参考文档PROVENANCE.md659 B
- 参考文档references/ADR-FORMAT.md2.7 KB
- 参考文档references/GLOSSARY-FORMAT.md2.2 KB
03 SKILL.md 正文
Domain Modeling
Adapted from mattpocock/skills -> skills/engineering/domain-modeling (MIT).
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 GLOSSARY.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:
/
├── GLOSSARY.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
If a GLOSSARY-MAP.md exists at the root, the repo has multiple contexts. The map points to where
each one lives:
/
├── GLOSSARY-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── GLOSSARY.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── GLOSSARY.md
│ └── docs/adr/
Create files lazily: only when you have something to write. If no GLOSSARY.md exists, create one
when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.
During the session
Challenge against the glossary
When the user uses a term that conflicts with the existing language in GLOSSARY.md, call it out
immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?"
Sharpen fuzzy language
When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things."
Discuss concrete scenarios
When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
Cross-reference with code
When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?"
Update GLOSSARY.md inline
When a term is resolved, update GLOSSARY.md right there. Don't batch these up: capture them as they
happen. Use the format in GLOSSARY-FORMAT.md.
GLOSSARY.md should be totally devoid of implementation details. Do not treat GLOSSARY.md as a
spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
Offer ADRs sparingly
Only offer to create an ADR when all three are true:
- Hard to reverse: the cost of changing your mind later is meaningful
- Surprising without context: a future reader will wonder "why did they do it this way?"
- The result of a real trade-off: there were genuine alternatives and you picked one for specific reasons
If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.
Hermes notes
- Read the existing files before writing:
GLOSSARY.md,GLOSSARY-MAP.md, anddocs/adr/*are context, and silently contradicting them is worse than not documenting at all. - Use
patch/write_fileand show the path you changed. Never invent a glossary entry for a term the user has not settled. - Outside a repo (Obsidian vault, business docs), keep the same filenames beside the work being planned and state the absolute path in your summary.
04 同仓库更多 Skills
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
grilling
Use when the user wants a plan stress-tested.