No Terminology Drift
A concept must be named identically throughout a single user flow — switching between synonyms or related terms mid-flow (e.g., 'Workspace' → 'Project' → 'Team') is forbidden.
$ aoe install @community/rule-no-terminology-driftProjection
Always in _index.xml · the agent never has to ask for this.
NoTerminologyDrift [rule] v1.0.0
A concept must be named identically throughout a single user flow — switching between synonyms or related terms mid-flow (e.g., 'Workspace' → 'Project' → 'Team') is forbidden.
Loaded when retrieval picks the atom as adjacent / supporting.
NoTerminologyDrift [rule] v1.0.0
A concept must be named identically throughout a single user flow — switching between synonyms or related terms mid-flow (e.g., 'Workspace' → 'Project' → 'Team') is forbidden.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
medium
Loaded when retrieval picks the atom as a focal / direct hit.
NoTerminologyDrift [rule] v1.0.0
A concept must be named identically throughout a single user flow — switching between synonyms or related terms mid-flow (e.g., 'Workspace' → 'Project' → 'Team') is forbidden.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
medium
Examples
- Violation: step 1 says 'Create a Project', step 3 says 'Your Workspace is ready'
- Violation: button says 'Delete Account', confirmation dialog says 'Remove Profile'
- Correct: create a terminology glossary before building; freeze labels at design system level
Relations
related: [@community/principle-nielsen-consistency]
Rationale
Term inconsistency forces users to mentally track whether 'Workspace', 'Project', and 'Team' are the same thing. This creates cognitive overhead and leads to errors, especially in multi-step flows where users carry context from prior steps.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
medium
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/rule-no-terminology-drift/atom.yaml