glossary
Skill185 starsChanged 32 days agoMITView on GitHub
Use when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
19 other projects use a version of this.
Adopted by
Most recently taken up by
- computerlovetech/skillstheir own version, first seen Nov 8, 2026
- harlan-zw/brundleflytheir own version, first seen Nov 8, 2026
- jeremy-farnault/claude-skillstheir own version, first seen Nov 3, 2026
- AcKeskin/contexturetheir own version, first seen Nov 1, 2026
- mrzli/skillstheir own version, first seen Nov 1, 2026
- TakaGoto/rag-learning-academytheir own version, first seen Oct 28, 2026
Used with
Projects with it also use recap and review.
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.Other versions19 projects use a version of this.
Word for word · 1
- intent-driven-dev/skills★ 9100% same
Edited · 0
None found.
Wrote their own version · 18
- chattocorp/chatto★ 2.9ksame name
- lightly-ai/lightly-studio★ 901same name
- genkovich/sdd★ 187same name
- aspi6246/Claude-Code-Skills-for-Academics★ 153same name
- tdimino/claude-code-minoan★ 41same name
- TakaGoto/rag-learning-academy★ 24same name
- Azure/azure-functions-agents-runtime★ 13same name
- harlan-zw/brundlefly★ 7same name
- computerlovetech/skills★ 4same name
- AcKeskin/contexture★ 2same name
8 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
- acceptance-test-authoringSkill
- architectural-decision-recordsSkill
- c4-diagramsSkill
- gherkin-authoringSkill
- grill-meSkill
- openspec-git-disciplineSkill
- spec-as-sourceSkill
- test-driven-developmentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
11
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 8
Use existing repository terms before creating new ones.
- Very specific: line 13
Read glossary/business.md and/or glossary/technical.md when present.
- Distinctive: line 16
If existing terms look close, ask the user whether to reuse one or define a new term.
- Distinctive: line 17
Use the chosen term consistently in the artifact.
- Distinctive: line 18
Add new terms to the appropriate glossary file.
- Distinctive: line 21
Do not add generic dictionary words or one-off implementation details.
- Distinctive: line 28
If a needed glossary file is missing, create it with this table:
- Distinctive: line 39
Ask before creating a new term when existing terms may fit:
- Distinctive: line 50
Do not proceed with a new term until the user answers, unless no plausible existing term exists.
- Distinctive: line 60
Every authored or edited non-glossary artifact gets a companion file in the same directory.
- Very specific: line 62
Do not create companion glossary reference files for glossary source files themselves, such as glossary/business.md or …
- Distinctive: line 80
If no glossary terms are used, write:
- Distinctive: line 88
Do not copy definitions into companion files.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Glossary
Use existing repository terms before creating new ones.
Workflow
- Identify the artifact being authored or reviewed.
- Read
glossary/business.mdand/orglossary/technical.mdwhen present. - Extract project-specific, technical, overloaded, ambiguous, or repeated concepts.
- Compare extracted concepts with existing glossary terms.
- If existing terms look close, ask the user whether to reuse one or define a new term.
- Use the chosen term consistently in the artifact.
- Add new terms to the appropriate glossary file.
- For non-glossary artifacts, create or update the artifact's companion glossary reference document.
Do not add generic dictionary words or one-off implementation details.
Glossary Files
glossary/business.md: domain, product, workflow, and business terms.glossary/technical.md: architecture, implementation, platform, and protocol terms.
If a needed glossary file is missing, create it with this table:
| Term | Definition | Use When | Avoid |
| --- | --- | --- | --- |New entries use the same table format. Keep definitions to one concise sentence.
Close-Term Question
Ask before creating a new term when existing terms may fit:
These glossary terms look close to "<concept>":
- `<existing-term>`: <why it may fit>
- `<another-term>`: <why it may fit>
Do you want to use one of these existing terms, or define a new term?Do not proceed with a new term until the user answers, unless no plausible existing term exists.
Marking Terms in Artifacts
In non-glossary artifacts, such as proposals, designs, specs, ADRs, and tasks, bold glossary terms that appear in the artifact's companion glossary reference.
Apply bolding in prose only. Do not bold terms in code blocks, frontmatter, links, or places where markdown formatting would make the artifact harder to read.
Companion Reference
Every authored or edited non-glossary artifact gets a companion file in the same directory.
Do not create companion glossary reference files for glossary source files themselves, such as glossary/business.md or glossary/technical.md.
Name: remove .md, then append -glossary-reference.md.
Examples: proposal-glossary-reference.md, design-glossary-reference.md, spec-glossary-reference.md, adr-glossary-reference.md, tasks-glossary-reference.md.
Format:
# Glossary Reference
| Term | Source Glossary | Context |
| --- | --- | --- |
| <Term> | `glossary/business.md` | <Short context for how the artifact uses this glossary term.> |Source Glossary is the glossary file the term came from or was added to, such as glossary/business.md or glossary/technical.md.
If no glossary terms are used, write:
# Glossary Reference
No glossary terms referenced.Do not copy definitions into companion files.
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.

