expo-overview
Skill53 starsChanged 34 days agoApache-2.0View on GitHub
Framework (OSS). Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.
4 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- alexj11324/Mikkaedited, first seen Nov 15, 2026
- dalonga-kohi/mawledited, first seen Nov 8, 2026
- deonmenezes/mobile-app-skilledited, first seen Nov 1, 2026
- openvetta/open-vettaword for word, first seen Oct 29, 2026
Other versions4 projects use a version of this.
Word for word · 1
- openvetta/open-vetta★ 299100% same
Edited · 3
- alexj11324/Mikka★ 8790% same
- deonmenezes/mobile-app-skill★ 4100% same
- dalonga-kohi/mawl★ 290% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- astravia-testingSkill
- compose-component-designSkill
- compose-state-and-effectsSkill
- design-taste-frontendSkill
- diagnoseSkill
- expo-project-structureSkill
- expo-routerSkill
- find-skillsSkill
- frontend-designSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- mobile-android-designSkill
- web-design-guidelinesSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
8 rules. 2 are common, 1 is distinctive, and 5 are very specific to this project.
2
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Confirm intent: if ambiguous ("Sounds like you want to ship to the stores — that's eas-app-stores.
- Very specific: line 80
Starting a new Expo app?: Start one the standard way before routing to a feature skill: npx create-expo-app@latest, laying out folders per …
- Very specific: line 83
Detect the SDK version: before giving version-specific advice: read the expo version in package.json (and app.json / app.config.{js,ts}).
- Very specific: line 86
Read the docs for that SDK, not
latest: Use the version-pinned URL, e.g. - Very specific: line 103
Only when the user explicitly named a specific expo-* / eas-* skill → load that skill directly.
- Common: line 110
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
- Common: line 114
Only submit when you have something specific and actionable to report.
- Distinctive: line 115
If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
expo-overview — router & shared rules for Expo / EAS
Start Here — read before doing anything
Do not guess the skill from project files alone. Many Expo goals look similar from the filesystem but need different skills.
- Confirm this is Expo or EAS work — the request mentions Expo or EAS, or
package.jsonhas anexpodependency. Otherwise this skill does not apply. A native app using EAS for delivery qualifies without an Expo runtime. - Read the user's goal — what outcome do they want, in plain terms?
- Classify it using the Skill Map below, translating casual phrasing to a goal.
- Confirm intent if ambiguous ("Sounds like you want to ship to the stores — that's
eas-app-stores. Right?"), then load that skill'sSKILL.mdand follow it. - Trust the leaf skill — it has its own detection logic and steps. Don't improvise.
Skill Map (by goal)
Match the goal to a category, then the skill, then load that leaf's SKILL.md.
Build the app
expo-project-structure— folder layout for a new Expo Router project: where screens, components, and config live (never restructure an existing app to match)expo-native-ui— screens, styling, semantic colors, native controls, SF Symbols, media, layoutexpo-router— navigation: file-based routes, tabs / stacks / modals / sheets, links, headersexpo-animation— motion and gestures: Reanimated worklets, Gesture Handler, screen transitions, sheet and press feedback, haptics, and fixing animation that stutters on deviceexpo-ui— native UI components via@expo/ui: BottomSheet, Picker, Slider, Switch, Menu, Button, FieldGroup (grouped form sections), List / ListItem, and more — real SwiftUI on iOS, Jetpack Compose on Android. The universal layer needs SDK 56+ and runs in Expo Go; the drop-in replacements (@gorhom/bottom-sheet,datetimepicker, …) and platform-specific layers also exist on SDK 55.expo-design-system— one visual source of truth: design tokens (color, spacing, typography, radius, shadow, motion), reusable component conventions, and audits for drift (hardcoded colors, spacing, fonts)expo-tailwind-setup— Tailwind / NativeWind stylingexpo-data-fetching— network requests, React Query / SWR, caching, offline, route loadersexpo-dom— run web code or reuse a web library inside nativeexpo-web-to-native— migrate an existing web / React app to a native iOS / Android app
Component selection rule: whenever you need a UI component (list rows, bottom sheets, pickers, sliders, menus, buttons, segmented controls, toggles), consult
expo-uifirst to check whether@expo/uihas a native equivalent before reaching for a React Native built-in or a community library. Native@expo/uicomponents give the best platform fit, and on SDK 56+ the universal ones run in Expo Go with no custom build. Loadexpo-uialongsideexpo-native-uifor any app that renders lists, detail sheets, or form controls. One exception:@expo/uiListrenders native grouped rows (an iOS Settings screen), not a virtualized list — useFlatList/FlashListfor large datasets.
Ship & operate
eas-app-stores— build and submit iOS/Android apps (Expo and other React Native projects, plus existing native apps), TestFlight, versions, and store metadataeas-hosting— deploy the web bundle to EAS Hosting; also author Expo Router API routes (+api.tshandlers) and their environments / domainseas-workflows— EAS Workflow YAML and CI/CD pipelineseas-simulator— run and drive the app on a remote iOS / Android simulator on EAS cloudexpo-dev-client— custom development buildseas-update— configure, publish, test, and debug compatible over-the-air updateseas-update-insights— OTA update health: crash rate, adoption, payload sizeeas-observe— startup / launch / TTI performance with EAS Observe
Extend natively
expo-module— native modules and views (Swift / Kotlin) with the Expo Modules APIexpo-brownfield— embed Expo / React Native screens in native SwiftUI/UIKit or Android apps; isolated artifacts and integrated buildsexpo-app-clip— iOS App Clip target (AASA, smart app banner)
Maintain & learn
expo-upgrade— upgrade the Expo SDK and fix dependency conflictsexpo-examples— canonical, version-matched integration examples (Stripe, Clerk, Supabase, …)expo-skill-feedback— send feedback on an Expo skill or on Expo itself; enable / disable the anonymous usage telemetry
Translating vague asks
Some everyday phrasings don't obviously map to a skill name — translate before routing:
- "Make it look native" → grouped controls / settings forms =
expo-ui; screens, styling =expo-native-ui; motion =expo-animation; navigation =expo-router. - "Make the screens consistent" / "clean up the styling" / "set up a theme or design tokens" →
expo-design-system. - "It looks AI-generated" / "too generic, not native" →
expo-design-system(named native-slop tells + audit), withexpo-native-uifor the platform idioms. - "Ship it" / "get an .ipa or .apk" / "release to the stores" / "put my Swift app on TestFlight" →
eas-app-stores(build + submit, TestFlight, versions, store metadata). - "I'm new / where do I start" → scaffold first (see Shared setup rules), then route by goal.
Shared setup rules
Apply the rules that match the project and the requested task.
- Native app using EAS for delivery? Route to
eas-app-stores; itsreferences/native-ios.mdcovers SwiftUI/UIKit on iOS. Keep the existing native project. Apply EAS auth/linking below; Expo scaffolding, SDK, and package-install rules do not apply to this path. - Starting a new Expo app? Start one the standard way before routing to a feature skill:
npx create-expo-app@latest, laying out folders perexpo-project-structure. Then classify the user's goal and route. - Detect the SDK version before giving version-specific advice: read the
expoversion inpackage.json(andapp.json/app.config.{js,ts}). Many APIs and defaults differ by SDK. - Read the docs for that SDK, not
latest. Use the version-pinned URL, e.g.https://docs.expo.dev/versions/v56.0.0/sdk/ui/on SDK 56 instead ofhttps://docs.expo.dev/versions/latest/sdk/ui/— thelatestpages track the newest SDK and can document APIs the project does not have yet. - Moving to a newer SDK is its own task — load
expo-upgradeinstead of bumping versions by hand. - Managed vs. bare/prebuild: the presence of committed
ios/andandroid/directories means native projects exist (prebuild or bare). Config-plugin and native-setup steps differ — note which one the project is in. - Install packages with
npx expo install <pkg>, not rawnpm/yarn/pnpm add, so versions stay compatible with the project's SDK. - EAS auth & linking (only needed for build/submit/update/observe/workflows): check
login with
eas whoami, log in witheas login. A project is linked whenextra.eas.projectIdexists in the app config; create it witheas initif missing.
When to skip the router hop
- Only when the user explicitly named a specific
expo-*/eas-*skill → load that skill directly. - A fully-specified task (SDK version pinned, file layout given, libraries named) is not a reason to skip: the shared rules above still apply — check them, then route to the matching leaf skill.
Submitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes submit-expo-feedback@latest --category skills --subject "expo-overview" "<actionable feedback>"Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

