Mobile Nav Plan

Organization

draftbit

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.

Overview

Publisher	draftbit
Repository	`mobile-taste-skill`
Skill name	`mobile-nav-plan`
Stars	8
Forks	1
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by draftbit on GitHub. Read the source before you install it.

Installation

Install the Mobile Nav Plan AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/draftbit/mobile-taste-skill/tree/main/skills/mobile-nav-plan
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/draftbit/mobile-taste-skill.git /tmp/mobile-taste-skill
mkdir -p .claude/skills
cp -r /tmp/mobile-taste-skill/skills/mobile-nav-plan .claude/skills/mobile-nav-plan

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mobile Nav Plan in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mobile Nav Plan on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mobile Nav Plan is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 current app/ (or navigator) tree, and MOBILE-DESIGN.md if 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 Read section, 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.tsx files 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.

Frequently asked questions

What does the Mobile Nav Plan AI skill do?

Why use Mobile Nav Plan on TypingMind?

Because you install it once and use it with any model. Mobile Nav Plan is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mobile Nav Plan in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/draftbit/mobile-taste-skill/tree/main/skills/mobile-nav-plan. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Mobile Nav Plan?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mobile Nav Plan?

As many as you like. As long as a model supports skills, you can use Mobile Nav Plan with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mobile Nav Plan AI skill free?

It is published on GitHub by draftbit. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Release Openclaw Ci

openclaw

OrganizationPopular

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

mobile-nav-plan: Navigation Architecture, Nothing Else

Flow

Rules that bind this skill

Frequently asked questions

Related AI Skills

Set up your own AI workspace now