
Wayfinding Navigation
- 34 installs
- 87 repo stars
- Updated June 9, 2026
- owl-listener/inclusive-design-skills
Helps with ai & agent building tasks during AI-assisted development.
About
wayfinding-navigation is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- wayfinding-navigation
- AI & Agent Building
- AI-coding skill
Wayfinding Navigation by the numbers
- 34 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #8,855 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill wayfinding-navigationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 34 |
|---|---|
| repo stars | ★ 87 |
| Last updated | June 9, 2026 |
| Repository | owl-listener/inclusive-design-skills ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Wayfinding and Navigation
Design navigation so that people with cognitive and memory difficulties can find content, understand where they are, and get back to where they were — without relying on memory.
Core Principle
Users should always be able to answer three questions instantly: 1. Where am I? 2. Where can I go? 3. How do I get back?
If any answer requires more than 1 second of thought, the navigation has failed.
Design Patterns
Signpost Pattern
- Breadcrumbs in hierarchies deeper than 2 levels
- Step indicators in multi-step flows ("Step 2 of 4")
- Active section highlighted in navigation
- Page titles that match the link that brought the user here
Minimal Path Pattern
- Important actions reachable in 1–2 clicks from any screen
- Breadth over depth — flatten deep hierarchies
- Shortcuts to frequently used content
- "Back to [last meaningful location]" always available
Multiple Routes Pattern
- Search AND browse AND shortcuts for all important content
- Don't force a single path to any destination
- "Jump to" links for long pages
- Recently visited and frequently used sections accessible
Chunking Pattern
- Break long content into headed sections (3–5 paragraphs each max)
- Table of contents for pages longer than 3 screens
- Progressive disclosure for detail
- Group related form fields into labelled fieldsets
Assessment Checklist
- [ ] Every page has a clear, descriptive title
- [ ] Navigation is consistent across all pages (same position, same order)
- [ ] Current location is always visually indicated
- [ ] Breadcrumbs or back links are present in hierarchies
- [ ] Multi-step flows show progress and allow backward movement
- [ ] Search is available on every page
- [ ] Important actions are reachable in 2 clicks or fewer
- [ ] Headings describe content (not just categories)
- [ ] Link text describes the destination (no "click here")
Output Format
When reviewing: identify navigation failures with specific locations and recommended fixes. When designing: present the information architecture with cognitive accessibility annotations.