.claude/skills/ts-expo-router/SKILL.md
Build native mobile apps with file-based routing using Expo Router — React Native navigation that works like Next.js. Use when someone asks to "add navigation to React Native", "Expo Router", "file-based routing for mobile", "deep linking in React Native", "mobile app navigation", or "React Native routing like Next.js". Covers file-based routes, layouts, deep linking, tabs, stacks, and universal links.
npx skillsauth add eliferjunior/Claude expo-routerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Expo Router brings file-based routing to React Native — the same pattern as Next.js but for mobile apps. Drop a file in app/, get a screen. Folder structure defines navigation hierarchy: stacks, tabs, drawers, and modals. Deep linking works automatically — every route has a URL. Build iOS, Android, and web from one codebase with the same routing system.
npx create-expo-app@latest my-app --template tabs
cd my-app
npx expo start
app/
├── _layout.tsx # Root layout (wraps all screens)
├── index.tsx # / (home screen)
├── about.tsx # /about
├── (tabs)/ # Tab navigation group
│ ├── _layout.tsx # Tab bar configuration
│ ├── index.tsx # First tab (home)
│ ├── explore.tsx # Second tab
│ └── profile.tsx # Third tab
├── settings/
│ ├── _layout.tsx # Stack layout for settings
│ ├── index.tsx # /settings
│ ├── account.tsx # /settings/account
│ └── notifications.tsx # /settings/notifications
├── [id].tsx # /123 (dynamic route)
├── post/
│ └── [slug].tsx # /post/my-first-post
└── +not-found.tsx # 404 screen
// app/_layout.tsx — Root layout with stack navigation
import { Stack } from "expo-router";
export default function RootLayout() {
return (
<Stack>
<Stack.Screen name="(tabs)" options={{ headerShown: false }} />
<Stack.Screen name="settings" options={{ title: "Settings" }} />
<Stack.Screen
name="modal"
options={{ presentation: "modal", title: "Info" }}
/>
</Stack>
);
}
// app/(tabs)/_layout.tsx — Bottom tab bar
import { Tabs } from "expo-router";
import { Ionicons } from "@expo/vector-icons";
export default function TabLayout() {
return (
<Tabs screenOptions={{ tabBarActiveTintColor: "#007AFF" }}>
<Tabs.Screen
name="index"
options={{
title: "Home",
tabBarIcon: ({ color }) => <Ionicons name="home" size={24} color={color} />,
}}
/>
<Tabs.Screen
name="explore"
options={{
title: "Explore",
tabBarIcon: ({ color }) => <Ionicons name="compass" size={24} color={color} />,
}}
/>
<Tabs.Screen
name="profile"
options={{
title: "Profile",
tabBarIcon: ({ color }) => <Ionicons name="person" size={24} color={color} />,
}}
/>
</Tabs>
);
}
// app/(tabs)/index.tsx — Home screen with navigation
import { Link, router } from "expo-router";
import { View, Text, Pressable, FlatList } from "react-native";
export default function HomeScreen() {
const posts = usePosts();
return (
<View>
{/* Declarative navigation */}
<Link href="/about">About</Link>
<Link href="/settings">Settings</Link>
<Link href="/post/hello-world">My Post</Link>
{/* Programmatic navigation */}
<Pressable onPress={() => router.push("/settings/account")}>
<Text>Go to Account</Text>
</Pressable>
{/* Dynamic routes */}
<FlatList
data={posts}
renderItem={({ item }) => (
<Link href={`/post/${item.slug}`}>
<Text>{item.title}</Text>
</Link>
)}
/>
</View>
);
}
// app/post/[slug].tsx — Dynamic route screen
import { useLocalSearchParams } from "expo-router";
export default function PostScreen() {
const { slug } = useLocalSearchParams<{ slug: string }>();
const post = usePost(slug);
return (
<View>
<Text style={{ fontSize: 24 }}>{post?.title}</Text>
<Text>{post?.content}</Text>
</View>
);
}
// app.json — Deep linking just works
{
"expo": {
"scheme": "myapp",
"web": { "bundler": "metro" }
}
}
Every route automatically gets a URL:
myapp:// → Home screenmyapp://post/hello-world → Post screenhttps://myapp.com/post/hello-world → Same screen (universal links)User prompt: "Set up navigation for a social app — tabs for feed/search/profile, stack for post details, and modal for creating posts."
The agent will create tab layout, nested stack routes, and a modal route with proper animations and deep linking.
User prompt: "Add login/signup screens that show before the main app tabs."
The agent will create a route group for auth screens, use layout redirection based on auth state, and protect tab routes.
app/about.tsx = /about screen_layout.tsx for navigation containers — Stack, Tabs, Drawer(group) for route groups — organize without affecting URL[param] for dynamic routes — access via useLocalSearchParamsLink for declarative, router for programmatic — navigation+not-found.tsx for 404 — catches unmatched routeshref autocompletes with TypeScriptexpo-routerpresentation: "modal" in options — for modal screensdevelopment
Expert guidance for Fireworks AI, the platform for running open-source LLMs (Llama, Mixtral, Qwen, etc.) with enterprise-grade speed and reliability. Helps developers integrate Fireworks' inference API, fine-tune models, and deploy custom model endpoints with function calling and structured output support.
development
Convert any website into clean, structured data with Firecrawl — API-first web scraping service. Use when someone asks to "turn a website into markdown", "scrape website for LLM", "Firecrawl", "extract website content as clean text", "crawl and convert to structured data", or "scrape website for RAG". Covers single-page scraping, full-site crawling, structured extraction, and LLM-ready output.
tools
Expert guidance for Firebase, Google's platform for building and scaling web and mobile applications. Helps developers set up authentication, Firestore/Realtime Database, Cloud Functions, hosting, storage, and analytics using Firebase's SDK and CLI.
development
When the user needs to build file upload functionality for a web application. Use when the user mentions "file upload," "image upload," "upload endpoint," "multipart upload," "presigned URL," "S3 upload," "file validation," "upload to cloud storage," or "accept user files." Handles upload endpoints, file validation (type, size, magic bytes), cloud storage integration, and upload status tracking. For image/video processing after upload, see media-transcoder.