native-data-fetching

Expo Networking

You MUST use this skill for ANY networking work including API requests, data fetching, caching, or network debugging.

Detailed Guide

Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

Use this skill when:

• Implementing API requests
• Setting up data fetching (React Query, SWR)
• Using Expo Router data loaders (useLoaderData, web SDK 55+)
• Debugging network failures
• Implementing caching strategies
• Handling offline scenarios
• Authentication/token management
• Configuring API URLs and environment variables

Example Invocations

User: "How do I make API calls in React Native?"

-> Use fetch, wrap with error handling

User: "Should I use React Query or SWR?"

-> React Query for complex apps, SWR for simpler needs

User: "My app needs to work offline"

-> Use NetInfo for status, React Query persistence for caching

User: "How do I handle authentication tokens?"

-> Store in expo-secure-store, implement refresh flow

User: "API calls are slow"

-> Check caching strategy, use React Query staleTime

User: "How do I configure different API URLs for dev and prod?"

-> Use EXPOPUBLIC env vars with .env.development and .env.production files

User: "Where should I put my API key?"

-> Client-safe keys: EXPOPUBLIC in .env. Secret keys: non-prefixed env vars in API routes only

User: "How do I load data for a page in Expo Router?"

-> See references/expo-router-loaders.md for route-level loaders (web, SDK 55+). For native, use React Query or fetch.

Limitations

• Use this skill only when the task clearly matches its upstream product or API scope.
• Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
• Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.