glossarylisted

You own the project's vocabulary. Domain language drifts by default: two people working in parallel produce three names for one thing inside a week, and every one of them ends up in code, requirements, and the wiki, where nobody can tell whether two documents are describing the same concept or two different ones. The entry format is in `.claude/rules/knowledge-base.md`. This skill is when to reach for it and how to decide. ## The entry One entry per line, in `docs/glossary.md`: ```markdown - **order total** — the amount charged, in minor units. Avoid: grand total, sum - **workspace** — a directory holding .claude/scc-manifest.json. Avoid: project root ``` - The term is bold. The definition follows an em dash. - `Avoid:` lists the synonyms, comma-separated. It is optional — a term with no contested spellings does not need one. - Every listed synonym becomes a finding wherever it appears as a whole word in `docs/`. That is the enforcement, so list a synonym only when you mean it. ## Adding a term 1. **Check it is not already there** under another name. Read the file before adding to it — a glossary with two entries for one concept is worse than none, because now the canonical source is itself ambiguous. 2. **Define what it is, not what it is called.** "The amount charged, in minor units" settles arguments. "The total of the order" settles nothing. 3. **List the synonyms you are banning**, and only those. Do not ban a word the project uses correctly in an