Read root terminology.md and only the topic files the task touches. Use each adopted name with its recorded meaning in answers, documents, and code explanations. Terms stay in the field's language and explanations in the reader's language. Keep confirmed local names for their recorded audience, and honor wording decisions within their scope and exceptions. Quotations, code identifiers, and APIs keep their original form.
When the user asks about a term, answer with the adopted name, its meaning here, what other sources call it, and the reference.
Hand off to curate-terminology when a needed term is missing or contested, an entry looks wrong or stale, or a local name has no confirmation. Until then, describe the thing plainly and keep an unconfirmed local name as observed without asserting its meaning. This skill does not write the glossary.