domain-modeling
Skill1 starsChanged 3 months agoMITView on GitHub
Model the domain language, entities, states, aliases, and naming rules from code, docs, ADRs, tests, and user vocabulary. Use when the user asks for glossary work, naming cleanup, project vocabulary, system concepts, or project-language.
195 other projects use a version of this.
Adopted by
Most recently taken up by
- bmcszk/agent-skillstheir own version, first seen Nov 16, 2026
- wilbeibi/wilbeibi-skillstheir own version, first seen Nov 16, 2026
- tunnckoCore/skillstheir own version, first seen Nov 16, 2026
- devdeepjs/kobayashi-marutheir own version, first seen Nov 16, 2026
- qelphybox/tg-mcptheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-ts-deep-modules, decision-mapping and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 43 projects that use this
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 62 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 56 projects that use this
AWSSkillwizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
Also in 134 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 60 projects that use this
- +1 more from Lesani
Other versions195 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 195
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- windmill-labs/windmill★ 19ksame name
- GreyDGL/PentestGPT★ 16ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
185 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- debugSkill
- handoffSkill
- implementation-planSkill
- requirements-reviewSkill
- test-and-verifySkill
- webgl-scroll-siteSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 185 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Do one job: normalize project vocabulary from evidence.
- Very specific: line 14
Prefer plain text tables or bullets that can be pasted into CONTEXT.md, issues, or prompts.
- Distinctive: line 15
Keep the surface honest: mark uncertain terms instead of laundering guesses into canon.
- Distinctive: line 16
Stop when the current task's vocabulary is resolved.
- Very specific: line 20
Use when onboarding to a repo, reducing vague terminology, naming modules, creating CONTEXT.md, refreshing a glossary, or preparing a plan …
- Distinctive: line 30
Stop when the terms needed for the current work are clear.
- Distinctive: line 34
Prefer names already present in source and tests.
- Distinctive: line 38
Keep definitions short enough to reuse in prompts and issue titles.
- Distinctive: line 50
If editing a repo glossary, preserve existing useful terms and mark uncertainty instead of deleting aggressively.
“Common” is measured: kept by at least 6 in 10 of the 185 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
domain-modeling
Make the agent speak the project language instead of inventing one.
Unix/Pi Contract
- Do one job: normalize project vocabulary from evidence.
- Consume source, tests, docs, ADRs, and user words; emit a glossary or glossary patch.
- Prefer plain text tables or bullets that can be pasted into
CONTEXT.md, issues, or prompts. - Keep the surface honest: mark uncertain terms instead of laundering guesses into canon.
- Stop when the current task's vocabulary is resolved.
Use
Use when onboarding to a repo, reducing vague terminology, naming modules, creating CONTEXT.md, refreshing a glossary, or preparing a plan that depends on domain concepts.
Research Budget
Inspect, in order:
- Existing
CONTEXT.md,AGENTS.md,README, ADRs, and issue templates. - Public interfaces, route names, schemas, state enums, event names, tests, and docs.
- Repeated user vocabulary from the current task.
Stop when the terms needed for the current work are clear.
Glossary Rules
- Prefer names already present in source and tests.
- Include aliases only when they prevent confusion.
- Define states by observable behavior, not implementation guesses.
- Record disputed or weak terms as "avoid" or "needs decision".
- Keep definitions short enough to reuse in prompts and issue titles.
Output
Return or write, depending on the user's request:
- Canonical term.
- One-line meaning.
- Aliases or forbidden synonyms.
- Source evidence.
- Where the term should appear in code, docs, tests, or issues.
If editing a repo glossary, preserve existing useful terms and mark uncertainty instead of deleting aggressively.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

