domain-glossary
Skill14 starsChanged 8 months agoMITView on GitHub
Use when a consumer project has a CONTEXT.md file — defines the domain glossary convention for consistent terminology across specs, plans, and code. Pipeline commands read CONTEXT.md during context loading and use its vocabulary in generated artifacts.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- ChariereFiedler/ronce-racinetheir own version, first seen Nov 1, 2026
- microsoft/devsquad-copilottheir own version, first seen Oct 16, 2026
- mohmaedeslam00116/waypowertheir own version, first seen Oct 15, 2026
- AlpayC/claude-skill-settheir own version, first seen Sep 14, 2026
- kambleakash0/agent-skillstheir own version, first seen Apr 6, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- microsoft/devsquad-copilot★ 50same name
- kambleakash0/agent-skills★ 10same name
- ChariereFiedler/ronce-racine★ 9same name
- AlpayC/claude-skill-set★ 0same name
- mohmaedeslam00116/waypower★ 0same name
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 repository50 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adr-conventionSkill
- architecture-vocabularySkill
- backlog-externalSkill
- backlog-localSkill
- backlogSkill
- checkpointsSkill
- design-principlesSkill
- git-practicesSkill
- grounded-claimsSkill
- knowledge-checkSkill
- policy-riskSkill
- positive-framingSkill
- receiving-code-reviewSkill
- skill-authoringSkill
- skill-awarenessSkill
- subagent-driven-developmentSkill
- test-driven-developmentSkill
- token-efficientSkill
- triageSkill
- verification-before-completionSkill
- workflow-bugSkill
- workflow-checkSkill
- workflow-commitSkill
- workflow-contractsSkill
- workflow-debugSkill
- workflow-decisionsSkill
- workflow-docsSkill
- workflow-doctorSkill
- workflow-epicSkill
- workflow-featureSkill
- workflow-flow-fix-pipelineSkill
- workflow-flowSkill
- workflow-grillSkill
- workflow-handoffSkill
- workflow-ideaSkill
- workflow-implementSkill
- workflow-planSkill
- workflow-proposalSkill
- workflow-prSkill
- workflow-refineSkill
- workflow-researchSkill
- workflow-reviewSkill
- workflow-startSkill
- workflow-statusSkill
- workflow-tech-reviewSkill
- workflow-update-workflowSkill
- workflow-validateSkill
- workflow-worktreeSkill
- workflow-yoloSkill
The file
Files
Domain Glossary Convention
What It Is
CONTEXT.md is an optional file at the repository root that defines the project's domain language. It gives the pipeline a shared vocabulary so specs, plans, and code use consistent terminology.
CONTEXT.md is optional. Commands work without it. When present, commands read it during context loading and prefer its defined terms over synonyms.
When to Create One
Create CONTEXT.md when:
- The same concept has multiple names in specs or code ("order" vs "transaction" vs "purchase")
- New team members (or AI) use wrong terms because the domain isn't documented
startoffers to scaffold it during repo initialization
Format
# Domain Context
## Language
| Term | Definition | Avoid |
|------|-----------|-------|
| [Term] | [What it means in this project] | [Synonyms to avoid] |
## Relationships
- A **[Term A]** contains one or more **[Term B]**
- A **[Term B]** references exactly one **[Term C]**
## Example Dialogue
> "When a customer places an **order**, the system creates **line items**..."
## Flagged Ambiguities
- "[Term]" — currently means both X and Y. Needs splitting when [condition].Pipeline Behavior
Commands that read CONTEXT.md:
- feature — uses vocabulary when writing the feature spec
- plan — references terms when naming phases, steps, and components
- implement — uses terms in variable names, function names, comments, and commit messages; avoids synonyms listed in the "Avoid" column
- tech-review — checks that code uses defined vocabulary consistently; flags terminology drift
Graceful Degradation
- No
CONTEXT.md→ commands proceed normally, no warning - Empty sections → skip those sections, use what's populated
- Ambiguities listed → flag them in generated artifacts when the ambiguous term appears
Related
- ADR-002 defines this convention:
docs/decisions/2026-04-29-domain-glossary-convention.md startscaffolds CONTEXT.md when the user opts in during repo initialization- The
/virtual-team:grillcommand maintains CONTEXT.md inline during grilling sessions
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.

