Tab · Knowledge
Glossary
The team's shared vocabulary. Domain terms specific to this project — what they mean, where they came from, and a parallel ## Anti-glossary section for terms you deliberately don't use (and why).
See it in motion
Where to find it
- Localhost:
/glossary.html?repo=<id> - Source:
.claude/brain/glossary.md(terms +## Anti-glossarysection)
What it does for you
Onboarding velocity climbs.A new teammate (or a new agent) reads glossary.md and they know what "the Brain," "Layer B telemetry," "consent-mode watermark" mean without asking.
Anti-glossary keeps the team aligned."We don't say 'self-driving' or 'autonomous coding' — those frame the product wrong" is a critical alignment tool. Both halves matter.
The AI uses your terms.CLAUDE.md links to glossary.md; the agent inherits your vocabulary instead of generic LLM defaults.
Configure
Nothing — glossary.md is a flat .md. The anti-glossary nests under ## Anti-glossary.
Use it well
Add a term the second time you have to explain it. Add an anti-glossary entry the second time you have to correct it. Both halves keep your AI from drifting into generic-LLM language.