What problem does it solve? Structuring navigation in an Expo app is error-prone: developers mix React Navigation with expo-router, dump all logic into one root layout, and hardcode path strings that break silently. This Skill provides the file-based routing conventions for expo-router so screens, tabs, modals, and auth flows follow one consistent structure that mirrors Next.js App Router. ## Core Features & Use Cases - File-based route structure: Defines the app/ directory archetype with (tabs)/, (modal)/, and (auth)/ groups, per-group _layout.tsx files, dynamic segments like [id].tsx, and +not-found.tsx. - Navigation primitives and typed routes: Covers <Link> versus router.push, useLocalSearchParams for dynamic segments, and enabling experiments.typedRoutes for build-time path checking. - Deep links, modals, and auth flow: Explains automatic deep-link configuration via scheme, the modal-as-route versus modal-as-state decision, and redirecting unauthenticated users with <Redirect> in the root layout. - Use Case: When adding a contacts screen with a detail page to an Expo app in a monorepo, use this Skill to place contacts/index.tsx and contacts/[id].tsx under (tabs)/, wire the tab layout, and navigate with typed <Link> components. ## Quick Start Ask the agent to add a new screen with tab navigation and a dynamic detail route to your Expo app using expo-router conventions.
