- Home
- Skills
- Mobile Development
- Expo Examples: Learn the Canonical Integration
More screenshots
Works with the AI Agents you already use
Expo Examples: Learn the Canonical Integration
Mine Expo's official with-* examples — find the right one, study it cleanly, and port the version-matched pattern by hand.
$5
Expo Examples: Learn the Canonical Integration
Example session with this skill installed
Add Stripe payments to our Expo app. Use the official example as the reference — but do not wreck our project doing it.
- Read your context and instructions
- Compiled the expo examples
Stripe added via with-stripe, project intact. Mode: study-and-adapt (existing app). Example: with-stripe, confirmed against the live repo listing. Study: read in its own directory — dependencies, Stripe config plugin, one payment-sheet screen, minimal server note. Port: dependencies added at versions aligned with the project's SDK (one newer than the example's, reason recorded), config plugin added, payment sheet wired into the existing checkout screen by hand. Omissions: the example's server stub not ported — the project already has a backend. Verification: payment flow run end to end. Drift note written. The porting record names the example (with-stripe, confirmed against the live repo), the pattern ported, the one version difference and its reason, and the deliberate omission of the example's server stub — the project already has a backend, so porting the stub would have duplicated it. The payment flow was run end to end on a device to prove the integration, not merely read. Every line that landed in the project was written by hand into the existing checkout screen, so the integration's provenance is visible in the diff and in the drift note. The working log holds the example name, the version differences, and the deliberate omissions, so the integration's provenance stays visible. Rubric score: 8/8.
Connects securely to your tools. The creator never sees your data.
About this skill
Expo maintains a library of roughly seventy small integration examples — each named with-<library> and built around exactly one integration: Stripe, Clerk, Supabase, maps, SQLite, and dozens more. They are not starter apps or architectures. Each is a managed project (no native directories; config plugins instead) with typically one screen of a hundred-odd lines, maintained against the current SDK. Their value is the pattern: which dependencies, which config plugins, which wiring — version-matched by the Expo team. This skill covers the two ways to use an example (study-and-adapt, or scaffold for a greenfield project), finding the right one, studying it without contaminating the user's project, porting the pattern by merging instead of overwriting, and the gotchas that bite when versions drift. A worked example adds Stripe by studying with-stripe and porting the pattern by hand.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Examples are single-integration donors, not architectures or starter apps.
- Snapshots of the example list drift; always confirm against the live repo.
- An example's versions match its SDK, not necessarily the project's.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Permissions
No special permissions declared or detected