Expo Overview
Entry point and router for every Expo or EAS task.
Install
npx skills add expo/skills --skill expo-overview -g -a claude-code -y- Repository
- expo/skills4k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,108 tokens
- Runs scripts
- No, instructions only
What it does
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.
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.
