Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When integrating a third-party library/service into an existing Expo app and you need the canonical version-matched pattern, or when scaffolding a new project from an official example via npx create-expo --example.
with-* example in expo/examples using gh api or the catalog reference.npx degit).npx create-expo --example <name> to start fresh.npx expo install, merge config plugins, port code, recreate env shape.The user gets the official, SDK-correct integration pattern adapted into their app, or a new project bootstrapped from a proven example — avoiding hand-rolled, version-mismatched setups.
Use Cases
A developer maintains an Expo app and needs to add Stripe payments. Instead of guessing the setup, they use the skill to locate `with-stripe`, read its config plugins and deps via gh, and adapt the pattern with `npx expo install`. The skill ensures SDK-correct versions and a non-destructive merge, saving hours of trial and error and preventing broken builds.
A founder wants a quick Supabase-backed Expo starter. They trigger scaffold mode and run `npx create-expo --example with-supabase` to get a fresh, official project with auth and DB wiring already correct for the current SDK. They skip boilerplate and start building features immediately on a maintained base.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File