$npx -y skills add Owl-Listener/inclusive-design-skills --skill wayfinding-navigationDesign navigation and information architecture for cognitive accessibility. Use when designing or reviewing navigation, site maps, page hierarchies, breadcrumbs, search, multi-step flows, or any structure where users need to find content and know where they are. Triggers on: user
| 1 | # Wayfinding and Navigation |
| 2 | |
| 3 | Design navigation so that people with cognitive and memory difficulties |
| 4 | can find content, understand where they are, and get back to where they |
| 5 | were — without relying on memory. |
| 6 | |
| 7 | ## Core Principle |
| 8 | |
| 9 | Users should always be able to answer three questions instantly: |
| 10 | 1. **Where am I?** |
| 11 | 2. **Where can I go?** |
| 12 | 3. **How do I get back?** |
| 13 | |
| 14 | If any answer requires more than 1 second of thought, the navigation |
| 15 | has failed. |
| 16 | |
| 17 | ## Design Patterns |
| 18 | |
| 19 | ### Signpost Pattern |
| 20 | - Breadcrumbs in hierarchies deeper than 2 levels |
| 21 | - Step indicators in multi-step flows ("Step 2 of 4") |
| 22 | - Active section highlighted in navigation |
| 23 | - Page titles that match the link that brought the user here |
| 24 | |
| 25 | ### Minimal Path Pattern |
| 26 | - Important actions reachable in 1–2 clicks from any screen |
| 27 | - Breadth over depth — flatten deep hierarchies |
| 28 | - Shortcuts to frequently used content |
| 29 | - "Back to [last meaningful location]" always available |
| 30 | |
| 31 | ### Multiple Routes Pattern |
| 32 | - Search AND browse AND shortcuts for all important content |
| 33 | - Don't force a single path to any destination |
| 34 | - "Jump to" links for long pages |
| 35 | - Recently visited and frequently used sections accessible |
| 36 | |
| 37 | ### Chunking Pattern |
| 38 | - Break long content into headed sections (3–5 paragraphs each max) |
| 39 | - Table of contents for pages longer than 3 screens |
| 40 | - Progressive disclosure for detail |
| 41 | - Group related form fields into labelled fieldsets |
| 42 | |
| 43 | ## Assessment Checklist |
| 44 | |
| 45 | - [ ] Every page has a clear, descriptive title |
| 46 | - [ ] Navigation is consistent across all pages (same position, same order) |
| 47 | - [ ] Current location is always visually indicated |
| 48 | - [ ] Breadcrumbs or back links are present in hierarchies |
| 49 | - [ ] Multi-step flows show progress and allow backward movement |
| 50 | - [ ] Search is available on every page |
| 51 | - [ ] Important actions are reachable in 2 clicks or fewer |
| 52 | - [ ] Headings describe content (not just categories) |
| 53 | - [ ] Link text describes the destination (no "click here") |
| 54 | |
| 55 | ## Output Format |
| 56 | |
| 57 | When reviewing: identify navigation failures with specific locations |
| 58 | and recommended fixes. When designing: present the information |
| 59 | architecture with cognitive accessibility annotations. |