Name Destination, Not Direction
DOCS-NAME-DESTINATION-NOT-DIRECTION
Summary
Use labels that name the section, object, or decision the reader will reach. Directional labels make readers follow the page order before knowing whether it is relevant.
Rule
Name the destination, decision, artifact, or work area instead of directing the reader.
Why
Reference pages, indexes, cards, and navigation labels should help readers choose by recognition. Phrases such as "start here," "use this when," "open this guide," or "go here to" turn a reference surface into a tutorial path. They make the page sound like it is coaching the reader instead of naming the thing the reader can inspect.
Descriptive labels such as "Change scope and handoff," "Rust API review," "Agent instructions," or "Rule IDs and review comments" keep the reader's attention on the decision or artifact.
Helps
- Keeps navigation copy scannable, reference-like, and grounded in the reader's task.
Limits
Directional phrasing belongs in procedures, tutorials, setup steps, and checklists where the reader is following an ordered path. Use direct instructions there. On catalogs and landing pages, prefer labels that identify the destination without telling the reader what to do next.
Agent Instruction
Write navigation and index copy as destination, decision, artifact, or work-area labels; avoid
directive phrases such as "start here," "use this guide," and "open this guide" on reference
surfaces.Mechanisms
Supported by heading review, card-copy review, rendered landing-page review, and checks that flag directional navigation phrases on reference or index pages.