Mobile nav plan
Turn an app idea or an existing React Native app into a Nav Read - tab structure, route tree, push/modal/sheet decisions, deep links, Android back plan - without building any screens. Use when planning navigation for a new app, restructuring an existing app's navigation, or deciding whether something is a tab, a push, a modal, or a bottom sheet. For building the screens afterward use mobile-taste; for full-app visual redesign use mobile-redesign-app.From its SKILL.md
npx -y skills add draftbit/mobile-taste-skill --skill mobile-nav-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.2 KB, as published. Nobody here has run it
mobile-nav-plan: Navigation Architecture, Nothing Else
Navigation is information architecture. This skill produces a Nav Read - a committed
route tree that doubles as the Expo Router app/ directory plan - and stops. No screen
code.
The method lives in ../_shared/references/navigation.md (container decision tree,
Expo Router conventions, mechanical checks, three worked examples). Tells cited by
number (#24 etc.) live in ../_shared/references/tells.md. Read both in full before
producing the Nav Read.
Flow
- Stack sniff. In an existing project, read
package.json/app.json/ the currentapp/(or navigator) tree, andMOBILE-DESIGN.mdif present. In a greenfield conversation, skip to 2. - App Read essentials. App kind, audience, target platforms + tier, platform posture (one line - the full App Read belongs to mobile-taste). If the app kind is genuinely ambiguous, ask ONE question.
- Enumerate the jobs-to-be-done. List the user's recurring destinations and the create/edit tasks BEFORE picking containers. Tabs come from this list, never from the Home/Search/+/Alerts/Profile template (tell #24).
- Run the decision tree (navigation.md §2) over every screen: tab root → push → modal → bottom sheet → full-screen modal, first match wins.
- Emit the Nav Read in the canonical format (navigation.md §1): platforms, tabs, route tree with container annotations, entry points, sheets (or "none"), deep links, Android back plan, max-taps line.
- Justify the contentious calls - one sentence each for: the tab count, the FAB decision (its presence, or its ABSENCE when the app has create actions), any full-screen modal, any BackHandler exception, and every screen that is a sheet rather than a modal.
- Self-check against the mechanical list (navigation.md §4). Report any rule the plan bends and why.
- Persist. Offer to write the Nav Read into
MOBILE-DESIGN.md(create or refresh the## Nav Readsection, reporting the delta if one existed). For an existing app, also emit the DIFF between the current route tree and the proposed one, flagging every change that hits the never-change-silently list (../_shared/references/redesign-protocol.md): route names, deep links, tab order.
Rules that bind this skill
- Restructuring an existing app's navigation is a PROPOSAL - implementation belongs to mobile-redesign-app after approval.
- No screen mockups, no component code. The single artifact is the Nav Read (plus the
optional empty route-file scaffold if the user asks for it:
_layout.tsxfiles and empty screens matching the tree, nothing inside them). - Cite the decision-tree step for every container choice. "It felt right" is not a rationale.