expo-router

Topics in the source

• Expo Router Navigation
• References
• Code Style
• Routes
• Library Preferences
• Behavior
• Navigation
• Link

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. Consult these resources as needed: 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. 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. 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) Prefer Stack.SearchBar to add a search bar to a screen Use from 'expo-router' for navigation b

This is an excerpt. Refer to the complete source and its current requirements.