Expo Router Navigation Guide
Design file-based routes and native navigation for Expo apps.
The material is primarily navigation guidance; there is no evidence of malware, credential handling, exfiltration, or high-risk external actions. The README discloses that telemetry is off by default and describes its data scope, and MIT licensing is clear. Points are deducted because the skill itself lacks user-confirmation, rollback, dependency-security, and data-flow-boundary guidance; publisher maintenance responsibility is also not clear, although the publisher is merely unverified rather than suspicious.
Routes, links, stacks, sheets, tabs, and search have concrete examples and some troubleshooting guidance. Points are deducted for SDK 54/55/56 and iOS-version differences that can cause API or import failures when mismatched, plus the absence of key-path tests, type checks, or reproducible execution evidence. Static calibration also limits the score.
The audience and scenarios are clear, covering route structure, dynamic routes, NativeTabs, search, form sheets, and iOS toolbars, with several platform and SDK limitations stated. Points are deducted because non-fit boundaries, trigger conditions, input/output contracts, and Chinese-language support are under-specified. Some capabilities require Expo Router and specific SDK versions, but the core does not depend entirely on unreachable overseas services.
Front matter provides name, description, version, and MIT license; topic-specific references provide examples, limitations, and troubleshooting, while the README documents installation and update paths and the repository has basic CI checks. Points are deducted for the lack of a skill-level changelog, named maintainer, stable compatibility matrix, and complete prerequisite notes; some referenced material is also outside the supplied skill path.
The skill can directly provide common Expo Router structures and code patterns across a broad feature set, offering practical value over manual lookup. Points are deducted because examples were not executed in this static review, several APIs are SDK-, platform-, or experimental-status-dependent, and there is no end-to-end validation guidance; project-specific adaptation and review remain necessary.
Evidence includes structured source files, concrete code examples, version constraints, limitations, and links to Expo primary documentation; the repository also contains generic skill-limit and version-check CI. Points are deducted because there are no skill-specific tests, execution logs, or third-party reproduction results, and the supplied material cannot independently verify most API examples.
- Check the project's Expo SDK, expo-router version, and target platforms before applying examples; the material mixes SDK 54, 55, 56, and iOS 18/26 capabilities.
- NativeTabs uses an unstable API, while toolbars and some zoom/form-sheet features have explicit platform or SDK limits; do not assume cross-platform equivalence.
- The guidance says to remove old route files during restructuring but provides no backup, confirmation, or rollback procedure.
- Use current Expo documentation and project type checks as the final authority because static skill content may lag dependency versions.
What does this skill do, and when should you use it?
This open-source skill focuses on navigation and routing for Expo Router applications. It covers file-based routes, dynamic routes, route groups, folder organization, Link components, native stacks, page titles, modal screens, form sheets, NativeTabs, headers, toolbars, and search bars. It also points to reference material for route structure, tabs, sheets, search, headers, and Apple Zoom transitions. It is a good fit for building or restructuring Expo Router navigation, but it does not cover screen styling, colors, controls, animations, or visual effects.
It uses the supplied Expo Router reference material to guide route organization under the app directory, _layout.tsx stack definitions, dynamic routes, shared route groups, and navigation code using Link, Link.Preview, Link.Menu, Stack, Stack.Title, modal presentations, form sheets, and NativeTabs. It specifies kebab-case file naming, path-alias preferences, route migration practices, and configuration patterns for headers, toolbars, search bars, and Apple Zoom transitions.
- An Expo developer creating an app and needing a file-based route and folder structure.
- A developer needing multiple tabs to share detail screens or other common routes.
- A developer adding iOS-style link previews, long-press context menus, native headers, or search bars.
- A developer presenting a screen as a modal or an adjustable-height form sheet.
- A developer restructuring navigation and removing obsolete route files safely.
What are this skill's strengths and limitations?
- Covers major Expo Router navigation patterns, including file routes, native stacks, tabs, modals, and sheets.
- Includes concrete TypeScript/TSX examples and organization rules.
- Distributed under the MIT license as part of an official Expo team skill collection.
- Its scope is navigation and routing; styling, colors, controls, animations, media, and visual effects are explicitly outside it.
- The source provides no test suite, platform verification matrix, or troubleshooting case studies.
- Some recommendations are iOS-specific or version-dependent, including search bars and Apple Zoom transitions.
How do you install this skill?
This skill is one of 23 skills in the expo/skills repository. Install the full collection with Skills CLI using npx skills@latest add expo/skills --skill '*', run it from the project root, then restart or refresh the agent session. For Claude Code, use claude plugin install expo@claude-plugins-official; for Codex, use codex plugin add expo@openai-curated. The source does not document an initial CLI command that installs only expo-router.
How do you use this skill?
After installation, give the agent a concrete Expo Router navigation request, for example: Build a native-feeling Expo Router screen with tabs, modals, and headers. The agent can then select this skill from context and consult its route-structure.md, tabs.md, toolbar-and-headers.md, form-sheet.md, search.md, and zoom-transitions.md references.