Domain Context

Preserve context that a future collaborator would otherwise have to rediscover.

Work independently

1. Inspect repository instructions and search for an existing glossary, domain guide, decision log, or ADR convention.
2. Read only the relevant artifacts and code needed to verify the term or decision.
3. Update the existing artifact when one fits. Otherwise propose the smallest useful Markdown file and a location consistent with the repository.
4. Write in the repository's documentation language and style.
5. Report what became durable and what intentionally stayed task-local.

Do not require another skill, a docs/ directory, a tracker, or a workflow stage. Chat may supply evidence, but facts needed to understand or review the result must appear in the artifact.

Glossary

Add a term only when it is durable and ambiguous, overloaded, domain-specific, or repeatedly used. For each entry, capture the concise meaning, important boundaries, and aliases only when useful.

Exclude implementation mechanics, file paths likely to move, temporary task vocabulary, speculative future terms, and conversation history. Consolidate duplicate entries instead of creating parallel definitions.