ux-navigation
Skill21 starsChanged 5 months agoMITView on GitHub
App navigation UX: tab bars, back buttons, deep links, gesture navigation, scroll behavior, modal vs push, and the 3-tap rule. Use when designing or auditing a navigation system, screen hierarchy, or information flow in a mobile or web app.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- alexj11324/Mikka★ 87same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- ux-accessibilitySkill
- ux-ai-automationSkill
- ux-contentSkill
- ux-error-handlingSkill
- ux-formsSkill
- ux-generalSkill
- ux-help-onboardingSkill
- ux-information-architectureSkill
- ux-networkSkill
- ux-notificationsSkill
- ux-reviewSkill
- ux-safety-privacySkill
- ux-searchSkill
- ux-settingsSkill
- ux-user-accountSkill
- ux-utilitySkill
- ux-visual-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 51
Deep linking strategy: Every major content screen should have a stable URL or URI scheme.
- Distinctive: line 59
When applying this checklist to a screen, flow, or codebase:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Navigation UX
Navigation is the skeleton of the app. When it is invisible and predictable, users feel in control. When it is broken or confusing, they leave.
Checklist
| Item | Guidance |
| Home accessible anywhere | Logo or home tab always returns to the root screen from anywhere in the app. |
| Persistent navigation | Tab bar or bottom navigation is visible on all primary screens. |
| Max 3 taps to content | Any piece of content is reachable in 3 taps or fewer from the home screen. |
| Current location indicator | The active tab is highlighted. Deep screens show a breadcrumb or clear title. |
| Android back button | Follows the back stack correctly. Never exits the app unexpectedly. |
| Back button on every screen | Every pushed screen has a back or close button in the top-left corner. |
| Logical flow | Navigation order matches the user's mental model and task sequence. |
| Deep link support | Every major screen has a URI scheme or Universal Link for direct access. |
| Tab bar badge counts | Unread count badges are accurate and clear when the content is viewed. |
| Scroll padding | Content at the bottom is padded above the tab bar height and safe area. |
| Status bar visible | Status bar is shown during normal app use. Hidden only in full-screen media. |
Navigation Patterns
Bottom tab bar (iOS): 3 to 5 items maximum. Icon and label together. Badge for notification counts. Not used for destructive actions.
Side drawer (Android): Suitable for apps with 5 or more top-level sections. Opened by a hamburger icon or a left-edge swipe. User avatar and name at the top.
Top navigation bar: Single screen title centered or left-aligned. Action icons on the right, maximum 2 visible. Back or close on the left.
Modal vs push: Push (drill-down) is for content that is part of the hierarchy. Modal (sheet or dialog) is for tasks that interrupt the main flow such as creating, editing, or confirming something. Never push where you should modal — it breaks the expected back stack behavior.
Deep linking strategy: Every major content screen should have a stable URL or URI scheme. This enables sharing, notifications, and marketing links to land users directly in the right place without going through the home screen.
How to Review
When applying this checklist to a screen, flow, or codebase:
- Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
- Cite specific evidence for each finding: the screen, component, file, or line it applies to.
- Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
- End the review with the top 3 recommended fixes, ranked by user impact.
Related Skills
ux-information-architecture— the structure the navigation exposesux-notifications— notifications that deep-link into the right screenux-general— cross-platform navigation parity
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.