agentleFS
KinwiseNZ-DevOpsKinwiseNZ-DevOps/ui-ux-designer/skills/navigation-and-flows/SKILL.md

navigation-and-flows

Skill0 starsChanged 22 days agoMITView on GitHub

Use when choosing or reviewing app navigation (tab bar, bottom navigation, hamburger menu, sidebar, rail), structuring information architecture, designing sheets, modals and dialogs flows, back behaviour, search, gestures or a multi-step flow such as checkout or sign-up. Do not use for form fields and messages (interaction-feedback-and-forms), screen spacing (adaptive-layout-and-spacing) or documenting site maps (ux-documentation-and-handoff).

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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
  1. Distinctive:

    Use a tab bar (bottom navigation) for top-level sections only, not for actions.

    line 18
  2. Distinctive:

    Keep three to five top-level destinations, and never an overflow "More" for key sections.

    line 19
  3. Distinctive:

    Never hide or disable a tab.

    line 20
  4. Distinctive:

    Keep the bar visible while moving between sections.

    line 21
  5. Distinctive:

    Do not rely on a hamburger menu alone.

    line 22
  6. Distinctive:

    Every gesture needs a visible alternative and must not be the only route.

    line 23
  7. Distinctive:

    List tasks and sections: Write what users do, rank by frequency, group into top-level destinations.

    line 41
  8. Distinctive:

    Add secondary routes: Search where content is large, in-content links, deep links.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Navigation and Flows

Stance: frozen are visible location, predictable back, and standard gestures. Flexible are the pattern chosen, as long as it suits the number of destinations and the common tasks.

Hard rules

  • Use a tab bar (bottom navigation) for top-level sections only, not for actions. Mechanism: mixing actions into it confuses where the user is; put actions in a toolbar or button.
  • Keep three to five top-level destinations, and never an overflow "More" for key sections. Mechanism: hidden destinations are rarely found (Apple HIG, NN/g).
  • Never hide or disable a tab; show an empty state that explains. Mechanism: a tab that appears and disappears makes the interface feel unstable.
  • Keep the bar visible while moving between sections. Mechanism: hiding it makes people forget where they are. A modal may cover it.
  • Do not rely on a hamburger menu alone. Mechanism: low discoverability, many users never open it; add in-content routes.
  • Every gesture needs a visible alternative and must not be the only route. Mechanism: voice, keyboard and switch users cannot swipe; people also do not discover hidden gestures.
  • Show one sheet at a time. Mechanism: stacked sheets lose the user's place.
  • Cancel dismisses, Done confirms, Back steps back. Mechanism: mixed meanings cause lost data or stuck flows.
  • Act only on what the user asked. Before answering or changing anything, open the relevant files and check what is already done; report only what you checked, never guess, and do not redo finished work. Reason: guesses and repeated work waste the user's credit.

Gate

SituationAction
Two to five equal top-level sectionsTab bar or bottom navigation
Six or more sections, or deep contentSidebar or hierarchical lists; keep the most used five in the bar
Browse-oriented, many categoriesMenu plus in-content links
One task per visitHub or single flow
A short task needing a few inputsSheet
Long or multi-step taskFull screen flow with progress and Back

Steps

  1. List tasks and sections. Write what users do, rank by frequency, group into top-level destinations.
  2. Choose the pattern with the gate. Compact windows: bottom bar; medium: rail; expanded: sidebar (see adaptive-layout-and-spacing).
  3. Map flows. For each key task draw entry, steps, decisions, success and error paths. Keep to the fewest steps; allow resuming.
  4. Define back and exit. Back goes one level; a visible Back plus system back gesture. Confirm only when data would be lost.
  5. Add secondary routes. Search where content is large, in-content links, deep links.
  6. Verify. Walk each flow with one thumb at compact width and with a keyboard at desktop width.

Checklist (copy into the reply and tick as you go)

- [ ] Top-level destinations ranked, five or fewer in the bar
- [ ] Nav stays visible; no hidden or disabled tabs
- [ ] Back, cancel and done have one meaning each
- [ ] Each gesture has a visible alternative
- [ ] Flows mapped with success and error paths
- [ ] Navigation described per size class

Examples

Example 1: tab bar overload User says: "We have eight sections, can I put all eight in the bottom bar?" Actions: rank by use; keep the top four or five; move the rest into a profile or menu screen with in-content links; explain the More tab problem. Result: a five-destination bar and a clear home for the rest.

Example 2: swipe-only delete User says: "Delete should only be a swipe left, it is cleaner." Actions: note it is undiscoverable and unusable without gestures; keep the swipe as a shortcut, add a visible Delete in an edit mode or menu, add undo. Result: fast path kept, nobody locked out.

Common issues

  • Users get lost after several taps. Cause: hidden bar or unclear titles. Fix: keep the bar visible; title every screen.
  • Back closes the app unexpectedly. Cause: flow not pushed on a stack. Fix: define the back stack per tab.
  • Sheets nest. Cause: an action in a sheet opens another. Fix: close the first, then open the next, or move to a full screen flow.

Next

interaction-feedback-and-forms for the controls inside flows; ux-documentation-and-handoff to record the site map and flows.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.