# Use Terminology > Use on every task alongside curate-terminology, even when the user does not ask about wording. Read and apply accepted English terms, verbs, collocations, sentence patterns, company names, local meanings, and project explanations throughout responses and artifacts. NOT a standalone research workflow: curate-terminology owns source selection, new definitions, expression records, and corrections to the shared reference. - Skill: `gigio1023/use-terminology` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add gigio1023/use-terminology` - Raw SKILL.md: https://api.skillmd.com/api/skills/gigio1023/use-terminology/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Research & Search - Author: gigio1023 (https://skillmd.com/u/gigio1023) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/gigio1023/use-terminology --- # Use Terminology Apply this skill on every task alongside `curate-terminology`, without waiting for a wording request. Use the project's accepted terms and expressions while completing the requested task. Give the reader an accurate explanation or a corrected artifact, not an unnecessary glossary report. Established English terms come first; explain their meaning in the reader's language without literal translation that changes the field's meaning. ## Read the relevant reference Read the project's instructions and root `terminology.md` at the start of every task. Apply its representative definitions and use its index to load only the relevant detailed documents under `docs/terminology/`. Follow each entry's citation to `docs/terminology/references.md` when checking its source, version, or supporting passage. An explicitly configured legacy layout is read through its current index until migrated; lookup alone does not move files. If no reference exists, use `curate-terminology` to establish relevant entries from eligible sources as needed; continue the original task without inventing entries or requiring a glossary first. Resolve those links from the document's location. Search within that material before widening to the project's source index; do not load the entire literature collection or a historical glossary merely because it is longer. Apply entries to their documented domain, version, conditions, and level of claim. Keep an internal identifier distinct from a reader-facing name, a source-specific metric distinct from a general concept, and an editorial restriction distinct from a claim about all industry usage. Explicit project wording decisions take precedence over a generic preference to retain a familiar term; preserve the protected quotations and identifiers specified by that decision. Preserve confirmed company proper names and local meanings even when industry usage differs. Use local shorthand for internal readers and clarify ambiguous terms for external or mixed readers within the sharing scope. If a small number of local terms remain unclear after checking records, use `curate-terminology` to ask the user and record the answer. While waiting, preserve the observed name without asserting an unconfirmed meaning; do not repeatedly ask about settled conventions. A legitimate local name is not an anti-pattern by itself. When the user asks about a term, return the accepted English expression, its contextual meaning, the distinction that resolves the question, and a useful source pointer. Do not turn an ordinary phrase into a named method. When drafting, apply the accepted verbs, collocations, and sentence patterns as well as nouns. Explain who acts on what, under which conditions, and with what observable effect. Reuse how established sources explain a project's purpose and component relationships only when the underlying behavior matches; do not import their architecture or guarantees. Retain the qualifiers that determine meaning. Consult [application pitfalls](references/application-pitfalls.md) when a familiar label hides a different operation or a stronger claim. ## Correct what the task authorizes The standing policy covers every task: fix confirmed terminology and expression problems in directly managed documents encountered or edited during the work, and use `curate-terminology` for related reference updates without another correction request. Respect an explicit read-only or review-only restriction: return the exact problem and proposed correction without modifying files. Quotes, collected originals, archived records, APIs, schemas, and identifiers retain their original form; correct the explanation around them. External edits and publication use the existing authorization for that service. If the original cannot be changed, describe the correction and, when local recording is authorized, put it in the project's correction record. If the accepted reference is wrong, stale, contradictory, or missing the needed concept, do not pretend it settles the answer. Identify the narrow gap and inspect the available primary source needed for the immediate task. Use a qualified plain-language description while uncertainty remains. Use `curate-terminology` for the focused source research and record update needed to resolve it. Do not start a broad survey or parallel glossary to answer one question. With no relevant gap or change, apply the existing reference and continue without artificial edits. ## Return to the work Check the final answer or edited passages for stable names, preserved qualifiers, source fit, and compliance with project-specific expressions. Verify navigation and reference anchors plus the project's required document checks for files changed. Any new or changed definition or expression must have its source recorded in `docs/terminology/references.md` through `curate-terminology`; unchanged usage reuses the existing record. State material corrections and unresolved meaning briefly, then continue the original task. `curate-terminology` owns reusable definition and expression records; this skill owns applying them.