Building Shared Vocabulary

Overview

A project's domain glossary (CONTEXT.md) and architecture decision records (docs/adr/) are not documentation written after the fact — they are operational artifacts that the agent reads to stay aligned with the project, and updates inline as the conversation produces new shared meaning.

Core principle: Vocabulary is built up one resolved term at a time, in the moment the resolution happens. Batched glossary writes go stale.

CONTEXT.md is a domain artifact, not an agent directive. guarding-agent-directives does not apply — that skill protects CLAUDE.md / AGENTS.md and the documents they reference. This skill owns CONTEXT.md and docs/adr/.

When to Use

• A domain term is being pinned down during conversation (especially during grilling)
• A term in the user's plan conflicts with how the codebase uses it
• A decision that is hard-to-reverse, surprising-without-context, AND the result of a real trade-off has been made — record an ADR
• User explicitly asks to "build a glossary," "set up CONTEXT.md," "add an ADR"

Do NOT use for