Expo Router

作者 expocd752143d19eMIT2.6K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库昨天更新

Framework (OSS). Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars.

仅含说明Software Development

AI 生成的概览

为 Expo Router 应用提供导航与路由实现指导，涵盖路由、链接、堆栈、标签页、页眉和表单页。

功能: 该技能提供在 Expo Router 应用中实现导航与路由的参考说明。内容涵盖基于文件的路由、分组与动态路由、目录组织、带预览和上下文菜单的 Link 组件、原生 Stack 布局、页面标题、模态与表单页、NativeTabs、页眉与工具栏以及页眉搜索栏。它还给出代码风格与库使用偏好，例如文件名使用 kebab-case，以及使用 expo-router 导出而非直接从 @react-navigation 导入。它产出的是指导与代码模式，而非可运行脚本。
适用场景: 当你在开发 Expo Router 应用并需要搭建或重构导航、路由、标签页、堆栈、页眉、模态、表单页或搜索栏时使用。它也适用于决定如何组织路由文件，或应优先使用哪些导航 API 与导入方式。
运行要求: 不包含脚本，仅为说明与参考文档。它假定存在使用 React Native 与 TypeScript 的 Expo Router 项目，并提到可选的样式与动画相关技能。反馈部分提到一个 npx 命令，但运行它并非使用该技能指导所必需。

Expo Router Navigation

Navigation and routing for Expo Router apps. For screen styling, colors, controls, media, and visual effects, use the expo-native-ui skill; for motion and gestures, use expo-animation.

References

Consult these resources as needed:

references/  route-structure.md     Route conventions, dynamic routes, groups, folder organization  tabs.md                NativeTabs, migration from JS tabs, iOS 26 features  toolbar-and-headers.md Stack headers and toolbar buttons, menus, search (iOS only)  form-sheet.md          Form sheets in expo-router: configuration, footers and background interaction.  search.md              Search bar with headers, useSearch hook, filtering patterns  zoom-transitions.md    Apple Zoom: fluid zoom transitions with Link.AppleZoom (iOS 18+)

references/  route-structure.md     Route conventions, dynamic routes, groups, folder organization  tabs.md                NativeTabs, migration from JS tabs, iOS 26 features  toolbar-and-headers.md Stack headers and toolbar buttons, menus, search (iOS only)  form-sheet.md          Form sheets in expo-router: configuration, footers and background interaction.  search.md              Search bar with headers, useSearch hook, filtering patterns  zoom-transitions.md    Apple Zoom: fluid zoom transitions with Link.AppleZoom (iOS 18+)

Code Style

Always use kebab-case for file names, e.g. comment-card.tsx
Always remove old route files when moving or restructuring navigation
Never use special characters in file names
Configure tsconfig.json with path aliases, and prefer aliases over relative imports for refactors.

Routes

See ./references/route-structure.md for detailed route conventions.

Routes belong in the app directory.
Never co-locate components, types, or utilities in the app directory. This is an anti-pattern.
Ensure the app always has a route that matches "/", it may be inside a group route.

Library Preferences

Color from expo-router for native semantic colors, not raw PlatformColor (type-safe, auto-adapts to light/dark). See expo-native-ui for the full color palette pattern.
In SDK 56+, never import from @react-navigation/* directly — use expo-router/react-navigation instead (covers @react-navigation/native, /core, /elements, /routers)

Behavior

Prefer Stack.SearchBar to add a search bar to a screen

Navigation

Link

Use <Link href="/path" /> from 'expo-router' for navigation between routes.

tsx

import { Link } from 'expo-router';
// Basic link<Link href="/path" />
// Wrapping custom components<Link href="/path" asChild>  <Pressable>...</Pressable></Link>

import { Link } from 'expo-router';
// Basic link<Link href="/path" />
// Wrapping custom components<Link href="/path" asChild>  <Pressable>...</Pressable></Link>

Whenever possible, include a <Link.Preview> to follow iOS conventions. Add context menus and previews frequently to enhance navigation.

Stack

ALWAYS use _layout.tsx files to define stacks
Use Stack from 'expo-router/stack' for native navigation stacks

Page Title

Set the page title with Stack.Title:

Context Menus

Add long press context menus to Link components:

tsx

import { Link } from "expo-router";
<Link href="/settings" asChild>  <Link.Trigger>    <Pressable>      <Card />    </Pressable>  </Link.Trigger>  <Link.Menu>    <Link.MenuAction      title="Share"      icon="square.and.arrow.up"      onPress={handleSharePress}    />    <Link.MenuAction      title="Block"      icon="nosign"      destructive      onPress={handleBlockPress}    />    <Link.Menu title="More" icon="ellipsis">      <Link.MenuAction title="Copy" icon="doc.on.doc" onPress={() => {}} />      <Link.MenuAction        title="Delete"        icon="trash"        destructive        onPress={() => {}}      />    </Link.Menu>  </Link.Menu></Link>;

import { Link } from "expo-router";
<Link href="/settings" asChild>  <Link.Trigger>    <Pressable>      <Card />    </Pressable>  </Link.Trigger>  <Link.Menu>    <Link.MenuAction      title="Share"      icon="square.and.arrow.up"      onPress={handleSharePress}    />    <Link.MenuAction      title="Block"      icon="nosign"      destructive      onPress={handleBlockPress}    />    <Link.Menu title="More" icon="ellipsis">      <Link.MenuAction title="Copy" icon="doc.on.doc" onPress={() => {}} />      <Link.MenuAction        title="Delete"        icon="trash"        destructive        onPress={() => {}}      />    </Link.Menu>  </Link.Menu></Link>;

Link Previews

Use link previews frequently to enhance navigation:

tsx

<Link href="/settings">  <Link.Trigger>    <Pressable>      <Card />    </Pressable>  </Link.Trigger>  <Link.Preview /></Link>

<Link href="/settings">  <Link.Trigger>    <Pressable>      <Card />    </Pressable>  </Link.Trigger>  <Link.Preview /></Link>

Link preview can be used with context menus.

Modal

Present a screen as a modal:

Prefer this to building a custom modal component.

Sheet

Present a screen as a dynamic form sheet:

tsx

<Stack.Screen  name="sheet"  options={{    presentation: "formSheet",    sheetGrabberVisible: true,    sheetAllowedDetents: [0.5, 1.0],    contentStyle: { backgroundColor: "transparent" },  }}/>

<Stack.Screen  name="sheet"  options={{    presentation: "formSheet",    sheetGrabberVisible: true,    sheetAllowedDetents: [0.5, 1.0],    contentStyle: { backgroundColor: "transparent" },  }}/>

Using contentStyle: { backgroundColor: "transparent" } makes the background liquid glass on iOS 26+.

Common route structure

A standard app layout with tabs and stacks inside each tab:

app/  _layout.tsx — <NativeTabs />  (index,search)/    _layout.tsx — <Stack />    index.tsx — Main list    search.tsx — Search view

app/  _layout.tsx — <NativeTabs />  (index,search)/    _layout.tsx — <Stack />    index.tsx — Main list    search.tsx — Search view

tsx

// app/_layout.tsximport { NativeTabs } from "expo-router/unstable-native-tabs";import { ThemeProvider, DarkTheme, DefaultTheme } from "expo-router/react-navigation";import { useColorScheme } from "react-native";
export default function Layout() {  const colorScheme = useColorScheme();  return (    <ThemeProvider value={colorScheme === "dark" ? DarkTheme : DefaultTheme}>      <NativeTabs>        <NativeTabs.Trigger name="(index)">          <NativeTabs.Trigger.Icon sf="list.dash" md="list" />          <NativeTabs.Trigger.Label>Items</NativeTabs.Trigger.Label>        </NativeTabs.Trigger>        <NativeTabs.Trigger name="(search)" role="search" />      </NativeTabs>    </ThemeProvider>  );}

// app/_layout.tsximport { NativeTabs } from "expo-router/unstable-native-tabs";import { ThemeProvider, DarkTheme, DefaultTheme } from "expo-router/react-navigation";import { useColorScheme } from "react-native";
export default function Layout() {  const colorScheme = useColorScheme();  return (    <ThemeProvider value={colorScheme === "dark" ? DarkTheme : DefaultTheme}>      <NativeTabs>        <NativeTabs.Trigger name="(index)">          <NativeTabs.Trigger.Icon sf="list.dash" md="list" />          <NativeTabs.Trigger.Label>Items</NativeTabs.Trigger.Label>        </NativeTabs.Trigger>        <NativeTabs.Trigger name="(search)" role="search" />      </NativeTabs>    </ThemeProvider>  );}

Create a shared group route so both tabs can push common screens:

tsx

// app/(index,search)/_layout.tsximport { Stack } from "expo-router/stack";import { colors } from "@/theme/colors";
export default function Layout({ segment }) {  const screen = segment.match(/\((.*)\)/)?.[1]!;  const titles: Record<string, string> = { index: "Items", search: "Search" };
  return (    <Stack      screenOptions={{        headerTransparent: true,        headerShadowVisible: false,        headerLargeTitleShadowVisible: false,        headerLargeStyle: { backgroundColor: "transparent" },        headerTitleStyle: { color: colors.label },        headerLargeTitleEnabled: true,        headerBlurEffect: "none",        headerBackButtonDisplayMode: "minimal",      }}    >      <Stack.Screen name={screen} options={{ title: titles[screen] }} />      <Stack.Screen name="i/[id]" options={{ headerLargeTitleEnabled: false }} />    </Stack>  );}

// app/(index,search)/_layout.tsximport { Stack } from "expo-router/stack";import { colors } from "@/theme/colors";
export default function Layout({ segment }) {  const screen = segment.match(/\((.*)\)/)?.[1]!;  const titles: Record<string, string> = { index: "Items", search: "Search" };
  return (    <Stack      screenOptions={{        headerTransparent: true,        headerShadowVisible: false,        headerLargeTitleShadowVisible: false,        headerLargeStyle: { backgroundColor: "transparent" },        headerTitleStyle: { color: colors.label },        headerLargeTitleEnabled: true,        headerBlurEffect: "none",        headerBackButtonDisplayMode: "minimal",      }}    >      <Stack.Screen name={screen} options={{ title: titles[screen] }} />      <Stack.Screen name="i/[id]" options={{ headerLargeTitleEnabled: false }} />    </Stack>  );}

headerLargeTitleEnabled is the SDK 56+ option name; older SDKs use headerLargeTitle, which is deprecated upstream.

Submitting Feedback

If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:

bash

npx --yes submit-expo-feedback@latest --category skills --subject "expo-router" "<actionable feedback>"

npx --yes submit-expo-feedback@latest --category skills --subject "expo-router" "<actionable feedback>"

Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

来源与署名

来源：expo/skills位于plugins/expo/skills/expo-router提交cd75214

许可证： MIT

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

Expo Router

Expo Router Navigation

References

Code Style

Routes

Library Preferences

Behavior

Navigation

Link

Stack

Page Title

Context Menus

Link Previews

Modal

Sheet

Common route structure

Submitting Feedback

来源与署名

更多来自 expo/skills 的技能

Expo Migrate Module

Expo Upgrade

Expo Overview

Expo Module

Expo Dom

Expo Dev Client

更多Software Development技能

Playground

M5 Onboard

Cardputer Buddy

Dpop Adoption

Gemini Live Api

Gemini Api