What problem does it solve? Integrating a third-party library or service into an Expo app often means guessing at the right dependency versions, config plugins, and wiring. This Skill gives you the canonical, version-matched integration pattern from Expo's official examples repo (~70 with-* projects like Stripe, Clerk, Supabase, maps, SQLite, and Skia) so you adapt a maintained reference instead of hand-rolling the setup. ## Core Features & Use Cases - Find the right example: Map a need (payments, auth, maps) to an example name, verify it against the live repo, and check meta.json for renames or deprecations before recommending anything. - Two working modes: Study an example as reference and port its pattern into an existing app, or scaffold a greenfield project directly with npx create-expo --example <name>. - Non-destructive adaptation: Add only missing dependencies via npx expo install, merge config plugins without overwriting existing app.json setup, and recreate env vars from the example's placeholder shape. - Use Case: You need Stripe payments in an existing Expo app. The Skill pulls with-stripe into a scratch directory, reads its server routes, client provider, and config, then ports only what your project lacks. ## Quick Start Ask the assistant to find the official Expo example for the library you want to integrate and adapt its pattern into your current project.
