Inconsistent Terminology¶
Rule ID: content-inconsistent-terminology
Detect inconsistent terminology across instruction files (e.g., mixing 'directory' and 'folder')
| Severity | info (auto) |
| Autofix | llm |
| Since | v0.7.0 |
Research Basis¶
Detects inconsistent terminology across instruction files (e.g., one file says "directory" while another says "folder").
If one file says "run npm test" and another says "execute yarn test", the
model must resolve the ambiguity at inference time. The "Curse of Instructions"
paper shows that instruction conflicts compound multiplicatively — inconsistent
terminology creates implicit contradictions that degrade compliance.
Consistent terminology is a well-established principle in technical writing. For LLMs, it's even more important: the model lacks the human ability to infer that two different terms refer to the same concept from broader context.
References:
- Curse of Instructions (ICLR 2025) — Contradictions compound multiplicatively
- TextUnited: Why Consistent Terminology Matters in Technical Documentation — "Inconsistent terminology can confuse readers, forcing them to guess whether different terms refer to the same concept"