More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Expo Router: Navigation That Follows the Filesystem

    1

    Design navigation for Expo Router apps: file-based routes and groups, native stacks and tabs, modals and form sheets, links with previews, and deep links verified cold-start.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Expo Router: Navigation That Follows the Filesystem

    Expo Router: Navigation That Follows the Filesystem

    Example session with this skill installed

    Design navigation for a recipe app: tabs for Browse, Search, and Saved; a recipe detail pushed from Browse and Search; a "New collection" form; and a deep link that opens a recipe from a shared URL.

    • Read your context and instructions
    • Compiled the expo router

    Recipe app — navigation produced with the skill

    Route tree: root _layout.tsx holds NativeTabs (Browse, Search, Saved). A shared group (browse,search)/ holds one stack with large titles; recipe/[id].tsx lives in the group, so Browse and Search push the same detail screen from a single definition. Saved is its own stack. "New collection" is a formSheet route at half detent with a grabber — it interrupts and returns, so it is a sheet, not a pushed screen.

    Links: recipe cards are Links with Link.Preview (peek on long-press) and a context menu (Save, Share, Add to collection). Titles and the search bar are declared in the group layout, not per screen. Route params: [id] is read in recipe/[id].tsx and passed as props, so the detail screen renders in a story with plain props and no router mock.

    Deep link verified: recipes.app/recipe/42 cold-starts into the detail screen on iOS and Android with a back button to the list — not a dead end. The gated case is handled: a link to a Saved collection while signed out lands on sign-in, then continues to the destination instead of dropping it. Rubric score: 9/10 — one point held back because the Saved tab's search bar is declared per screen; it moves to the group layout before ship.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    In Expo Router the filesystem is the navigation graph — and the skill is knowing which primitive to reach for. This skill designs navigation from flows, not feature lists: stacks for destinations, native tabs for top-level sections, modal and formSheet routes for flows that interrupt and return, and Link with previews and context menus so the app feels platform-native. It shows how shared groups let two tabs push the same detail screen from one definition, how header and search configuration belongs in the layout instead of per screen, and why route params are read in the route file so screens stay testable without router mocks.

    You get a navigation decision table for the seven signals that say "wrong primitive," a route-tree template, a navigation checklist, and a scoring rubric with a ship threshold of 8/10. Edge cases cover the modal that should have been a screen, the tab that swallows its back stack, deep links into gated screens, and the search bar that disappears on push. A worked example builds a podcast app end to end — shared group, large titles, preview links, half-detent playlist sheet, cold-start deep link into the player — so every rule lands on a real app.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    • It assumes Expo Router on SDK 56+; older SDKs and other navigators differ.
    • It does not decide folder layout for non-route code, state management, or backend routing — navigation only.
    • Deep-link verification needs real devices or simulators; the skill names what to test, it cannot run the test for you.
    • The modal-vs-screen judgment is a heuristic — a flow can genuinely sit on the boundary, and the skill says how to spot it, not how to settle every argument.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    When it interrupts the main flow to collect input and return — create, filter, confirm. When the destination is shareable, bookmarkable, or deep-linkable, it is a pushed screen. A modal that users want a link to was misclassified.

    Because the copies diverge within a month and one becomes a stale route nobody maintains. A shared group lets both tabs push the same screen from one definition.

    So the screen renders from plain props — in a story, in a test, anywhere — without a router mock. A screen that reads its own params cannot be tested in isolation.

    New in Mobile Development