# Terminology Normalizer

Normalize terminology across a draft (canonical terms + synonym policy) without...

- Repository: https://github.com/WILLOSCAR/research-units-pipeline-skills (517 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill terminology-normalizer -g -a claude-code -y`
Codex: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill terminology-normalizer -g -a codex -y`
Cursor: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill terminology-normalizer -g -a cursor -y`
Gemini CLI: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill terminology-normalizer -g -a gemini-cli -y`

## Description

Normalize terminology across a draft (canonical terms + synonym policy) without changing citations or meaning.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Terminology Normalizer

## Triggers & routing

- **Trigger**: terminology, glossary, consistent terms, 术语统一, 统一叫法, 术语表.
- **Use when**: the draft has concept drift (same thing called 2, 3 names) or global-review flags terminology inconsistency.


Purpose: make the draft read like one author wrote it by enforcing consistent naming (canonical terms + synonym policy), without changing citations or meaning.

## Role cards (use explicitly)

### Taxonomist (canonicalizer)

Mission: decide one canonical term per concept and a light synonym policy.

Do:
- Prefer taxonomy node names (`outline/taxonomy.yml`) as canonical labels when available.
- Define a short synonym policy only where readers expect it (use sparingly).
- Keep headings and tables aligned with canonical terms.

Avoid:
- Renaming proper nouns (paper titles, benchmark names, model names).
- Over-normalizing away meaningful distinctions (e.g., collapsing two different mechanisms into one word).

### Integrator (apply without drift)

Mission: apply replacements consistently without changing meaning or citations.

Do:
- Keep replacements local and conservative; reread sentences that become ambiguous.
- Preserve citation placement and subsection boundaries.

Avoid:
- Introducing new claims while rewriting for terminology.
- Moving citations across subsections.

## Role prompt: Terminology Editor (one voice)

```text
You are normalizing terminology in a technical survey draft.

Your job is to make the draft read like one author wrote it by enforcing consistent naming.

Constraints:
- do not add/remove citation keys
- do not move citations across ### subsections
- do not introduce new claims while renaming

Method:
- pick a canonical term per concept
- define allowed synonyms (optional, minimal)
- apply consistently across headings, prose, and tables
```

## Inputs

- `output/DRAFT.md`
- Optional (read-only context):
  - `outline/outline.yml` (heading consistency)
  - `outline/taxonomy.yml` (canonical labels)

The rest: https://github.com/WILLOSCAR/research-units-pipeline-skills/blob/HEAD/.codex/skills/terminology-normalizer/SKILL.md