Integrate third-party services into Expo apps

This skill works with expo/examples, Expo's official library of roughly 70 integration examples - directories named with-<library> (e.g. with-stripe, with-maps) each built around one library or service such as Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, or NativeWind. These are managed projects (no ios//android/ directories - native setup goes through config plugins) and typically a single screen of 100-200 lines, meant to be mined for the canonical integration pattern - the dependency set, app.json config plugins, and minimal wiring Expo maintains against the current SDK - rather than treated as a full application architecture to lift wholesale. It defines two modes: inspiration/adapt, where the user already has a project and the example is read as reference material to apply by hand, and scaffold, where a fresh project is started directly from the example. For inspiration mode it walks through finding the right example by mapping the user's need to an example name, confirming against the live repo listing (since a local catalog snapshot drifts and meta.json is the source of truth for renamed/deprecated examples), listing the whole example recursively since integration code is often nested (Stripe's server routes live under app/api/), and reading high-signal files in order: README, package.json, app.json, the integration code itself, then .env for required secret shapes. For larger integrations it recommends pulling the whole example into a throwaway gitignored directory via degit or a sparse git checkout rather than making per-file API calls.

Use it when integrating a third-party library or service into an existing Expo app and you want the canonical, Expo-maintained pattern rather than hand-rolling the integration from a library's generic docs - reach for an example before hand-rolling. Also use it to scaffold a fresh greenfield project directly from an example. Do NOT expect to lift an application architecture from these examples - they are intentionally minimal single-screen demos of one integration, not reference apps. Also don't copy an example's pinned dependency versions into an existing project (examples track the latest SDK) or overwrite the user's existing app.json/config - only add what the example introduces and never replace what's already there.

Inputs: the user's integration need (which library or service to wire in) and, in inspiration mode, the target project's current structure. Outputs: a mapped example name, the example's dependency list, its app.json config plugins and permissions, its integration code adapted into the user's app via npx expo install <pkg> for version-correct dependencies, and a recreated .env shape with the required secret keys (never working secrets, since the example's own .env only holds placeholders). Work is considered done when every dependency, config plugin, permission, and env var the example needs is accounted for in the user's app - not merely when it looks wired up.

npx create-expo --example with-stripe

Relies on the GitHub CLI (gh api) or raw GitHub URLs to browse and fetch example files (the repo's default branch is master, not main), degit or a sparse git clone --filter=blob:none for pulling a whole example locally, and npx expo install for SDK-correct dependency resolution. Every example also has a single-click deploy launch URL (launch.expo.dev). It links to companion skills for Tailwind/NativeWind styling, native UI components, authoring a native module, and upgrading the Expo SDK before adopting a latest-SDK example.

Expo/React Native developers who need Expo's own canonical wiring for a third-party integration - the correct config plugins, dependency set, and minimal code - rather than reverse-engineering it from generic library documentation.