Lore UL (Ubiquitous Language)

Read ${CLAUDE_PLUGIN_ROOT}/reference/lore-spec.md first — its Glossary section defines the file location, the term-entry meta, collision handling, and the split rule.

The other lore skills key knowledge by code location; this one keys it by concept. A shared vocabulary is what lets rules hang off concepts instead of file paths, lets the user and the agent challenge each other's wording, and gives lore-guard something to check names against.

Which file, and whose flow

Resolve the glossary source per lore-spec before reading or writing anything. When a root CONTEXT.md / CONTEXT-MAP.md exists — or a dedicated domain-modeling / grilling skill is available in this session — let that system lead: a relentless-interview flow extracts terms better than reactive alignment, so this skill's job shrinks to spotting the drift signals below and kicking that flow off. When a term settles mid-conversation without a full interview, apply the alignment moves yourself but write into CONTEXT.md in its native format (**Term**: + _Avoid_: — rejected candidates go to _Avoid_: instead of not:, and no lore meta is injected). Never create docs/lore/glossary.md alongside an external glossary. Everything below assumes the fallback case: no external glossary and no such skill, so lore's own format applies.

When to use

• A conversation hits a vague or overloaded term ("account" — the Customer or the User?).
• The user's words and the code's names disagree, or the same word is being used for two different things.
• The project has no glossary yet and wants one (bootstrap).
• The user explicitly asks to define, align, or clean up terminology.

Softer, earlier signals count too — by the time a term is visibly overloaded, the language has already drifted. Any of these is reason enough to start aligning: