| name | expo-examples |
| description | Maps a need to Expo's official expo/examples with-* integrations and adapts the canonical pattern (deps, config plugins, wiring) into an existing managed app, or scaffolds via create-expo --example. Use when integrating Stripe, Clerk, maps, Reanimated, SQLite, Skia, or NativeWind into Expo. Not for authoring native modules or upgrading the Expo SDK. Do not scaffold an example on top of a populated project. |
| version | 1.0.1 |
| risk | unknown |
| source | https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples |
| source_repo | expo/skills |
| source_type | official |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/expo/skills/blob/main/LICENSE |
Expo Examples
When to Use
Use this skill when you need Expo's official example projects — the expo/examples repo of ~70 with-* integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Reach for it when:
- Integrating a third-party library or service into an existing Expo app and you want the canonical pattern Expo maintains against the current SDK.
- Scaffolding a greenfield project directly from an official example.
- Triaging which example matches a user's need (payments →
with-stripe, auth → with-clerk, etc.).
expo/examples is Expo's official library of ~70 integration examples — directories named with-<library> (e.g. with-stripe, with-maps), each built around one library or service. These are not full apps: they're managed projects (no ios//android/ dirs — native setup is via config plugins), and the typical one is a single screen of ~100–200 lines. Mine them for the canonical integration pattern — the dependency set, app.json config plugins, and minimal wiring Expo maintains against the current SDK — and adapt that into the user's app. Don't expect to lift an application architecture from them.
Reach for an example before hand-rolling an integration. (Kinds — full-stack, showcases, starters — are noted in ./references/catalog.md.)
Two modes
- Inspiration / adapt (most common) — the user already has a project. Find the matching example, read its key files, and apply the pattern to their code.
- Scaffold — greenfield. Start a fresh project directly from the example.
Prerequisites
gh (GitHub CLI) for API calls, OR curl/git as fallbacks.npx (Node) or bun for scaffolding via create-expo.- For adapting into an existing app: the user's project must already be an Expo managed project on a known SDK version.
Procedure
1. Find the right example
Map the user's need to an example name (e.g. payments → with-stripe, auth → with-clerk). is a categorized snapshot for fast triage — — but it drifts, so confirm against the live list:
