Catalog
expo/expo-overview

expo

expo-overview

Entry point for Expo and EAS tasks. Load first when the request mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an expo dependency. Identify the goal, apply shared SDK and setup rules, and select the relevant skill. Includes fully specified tasks; excludes React Native projects without Expo or EAS signals.

NewUpdated Nov 20, 2026

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.

  1. Confirm this is Expo or EAS work — the request mentions Expo or EAS, or package.json has an expo dependency. Otherwise this skill does not apply. A native app using EAS for delivery qualifies without an Expo runtime.
  2. Read the user's goal — what outcome do they want, in plain terms?
  3. Classify it using the Skill Map below, translating casual phrasing to a goal.
  4. Confirm intent if ambiguous ("Sounds like you want to ship to the stores — that's eas-app-stores. Right?"), then load that skill's SKILL.md and follow it.
  5. 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, layout
  • expo-router — navigation: file-based routes, tabs / stacks / modals / sheets, links, headers
  • expo-animation — motion and gestures: Reanimated worklets, Gesture Handler, screen transitions, sheet and press feedback, haptics, and fixing animation that stutters on device
  • expo-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 styling
  • expo-data-fetching — network requests, React Query / SWR, caching, offline, route loaders
  • expo-dom — run web code or reuse a web library inside native
  • expo-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-ui first to check whether @expo/ui has a native equivalent before reaching for a React Native built-in or a community library. Native @expo/ui components give the best platform fit, and on SDK 56+ the universal ones run in Expo Go with no custom build. Load expo-ui alongside expo-native-ui for any app that renders lists, detail sheets, or form controls. One exception: @expo/ui List renders native grouped rows (an iOS Settings screen), not a virtualized list — use FlatList / FlashList for 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 metadata
  • eas-hosting — deploy the web bundle to EAS Hosting; also author Expo Router API routes (+api.ts handlers) and their environments / domains
  • eas-workflows — EAS Workflow YAML and CI/CD pipelines
  • eas-simulator — run and drive the app on a remote iOS / Android simulator with Expo Simulators (also called EAS Simulator)
  • expo-dev-client — custom development builds
  • eas-update — configure, publish, test, and debug compatible over-the-air updates
  • eas-update-insights — OTA update health: crash rate, adoption, payload size
  • eas-observe — startup / launch / TTI performance with EAS Observe

Extend natively

  • expo-module — native modules and views (Swift / Kotlin) with the Expo Modules API
  • expo-brownfield — embed Expo / React Native screens in native SwiftUI/UIKit or Android apps; isolated artifacts and integrated builds
  • expo-app-clip — iOS App Clip target (AASA, smart app banner)

Maintain & learn

  • expo-upgrade — upgrade the Expo SDK and fix dependency conflicts
  • expo-examples — canonical, version-matched integration examples (Stripe, Clerk, Supabase, …)

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), with expo-native-ui for 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.

  • Run Expo commands through the agent CLI. Run npx --yes @expo/agent-cli@latest <command> where you would run npx expo <command>, including commands shown in other skills. Run npx --yes @expo/agent-cli@latest --help before your first command. It shows two kinds of commands:

    • Expo CLI commands (the "Expo CLI" group) go to the project's expo unchanged and take the same flags.
    • Agent CLI commands (all other groups) exist only in the agent CLI. They read the project state, get the app onto a device, check the running app, and search the docs for the project's SDK. Prefer them to manual steps. Read a command's --help before its first use, and run help workflow for the order to run them in.

    EAS commands (eas build, eas update, eas submit) stay on eas-cli. The agent CLI is experimental: if a command fails because of the CLI itself, run the underlying command directly. You can offer to report the failure with --category agent-cli (see Submitting Feedback).

  • Native app using EAS for delivery? Route to eas-app-stores; its references/native-ios.md covers 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 --yes @expo/agent-cli@latest new <directory> (it accepts --template and --example), laying out folders per expo-project-structure. Then classify the user's goal and route.

  • Detect the SDK version before giving version-specific advice: run npx --yes @expo/agent-cli@latest status, or read the expo version in package.json (and app.json / app.config.{js,ts}). Many APIs and defaults differ by SDK.

  • Read the docs for that SDK, not latest. npx --yes @expo/agent-cli@latest docs:search <query> searches local Markdown docs for the project's SDK. Otherwise use the version-pinned URL, e.g. https://docs.expo.dev/versions/v56.0.0/sdk/ui/ on SDK 56 instead of https://docs.expo.dev/versions/latest/sdk/ui/ — the latest pages 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-upgrade instead of bumping versions by hand.

  • Managed vs. bare/prebuild: the presence of committed ios/ and android/ 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 --yes @expo/agent-cli@latest install <pkg>, not raw npm/yarn/pnpm add, so versions stay compatible with the project's SDK. It runs expo install and links the agent skills that the package ships.

  • Launching the app yourself? When you open Expo Go or a development build to look at, screenshot, or drive it, skip the first-launch onboarding, the dev menu that opens at launch, and the floating Tools button. On SDK 58+, Expo CLI does this for launches it starts from a non-interactive shell. On SDK 57 and earlier, and for any URL you open yourself (simctl openurl, adb, a controller), follow ./references/launch-without-dev-menu.md.

  • EAS auth & linking (only needed for build/submit/update/observe/workflows): check login with npx --yes eas-cli@latest whoami, log in with npx --yes eas-cli@latest login. A project is linked when extra.eas.projectId exists in the app config; create it with npx --yes eas-cli@latest init if 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

You can voluntarily report errors, misleading or outdated information in this skill, so Expo can improve it:

npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-overview" --message "<actionable feedback>"

Use --category agent-cli for a problem with the agent CLI, and --category evals when an agent repeatedly fails at an Expo task. Run feedback --help for subjects and the data that the command sends. Each report goes to Expo with project and environment details. Show the user the message, and send it only if the user agrees. If you cannot ask the user, do not send it. Do not include secrets or personal data.

Files3
3 files · 3.4 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

95

Quality

86

Clarity

92

Completeness

82

Summary

This is a router and shared rules skill for Expo/EAS projects. It guides agents to identify whether a request involves Expo or EAS work, translate vague user goals into specific skill names, apply shared SDK/setup rules (Expo CLI via agent-cli, EAS auth, version detection), and route to the appropriate leaf skill (e.g., expo-router, eas-app-stores). It is a pure classification and dispatch tool with no file writes, shell execution, or project modifications.

Detected Capabilities

read package.json and app.jsonunderstand Expo/EAS project structureclassify user intents into Expo/EAS task categoriesprovide project context and setup guidancereference external Expo documentation (docs.expo.dev)suggest appropriate skill to load based on goal matching

Trigger Keywords

Phrases that agents use to match this skill to user intent.

expo or eas requestwhich skill to useclassify expo goalroute to leaf skillexpo setup rulestranslate expo taskagent cli vs eas cli

Referenced Domains

External domains referenced in skill content, detected by static analysis.

docs.expo.dev

Use Cases

  • Determine which Expo or EAS skill to load based on a user's goal statement
  • Route a vague request like 'make it look native' or 'ship it' to the correct skill (e.g., expo-design-system, eas-app-stores)
  • Apply shared Expo project setup rules: detecting SDK version, auth, linking, package installation conventions
  • Identify when a request requires the agent CLI vs. the Expo CLI vs. the EAS CLI
  • Learn the CLI patterns and shared rules that all Expo/EAS skills depend on

Quality Notes

  • Extremely clear structure: 'Start Here' section prevents blind routing, Skill Map is comprehensive and well-organized by goal category
  • Shared setup rules are detailed and practical: covers agent CLI vs. EAS CLI distinction, SDK version detection, package installation with expo install, EAS auth flow
  • Translating vague asks section is valuable: teaches the agent how to map casual phrasing to formal skill names (e.g., 'ship it' → eas-app-stores)
  • Supporting reference file (launch-without-dev-menu.md) is comprehensive and SDK-version-aware, with platform-specific instructions
  • Component selection rule is well-documented: explains when to use @expo/ui vs. alternatives, and clarifies the distinction between @expo/ui List (grouped rows) and FlatList (virtualized)
  • Skill map is exhaustive across four domains (Build, Ship & operate, Extend natively, Maintain & learn) with 15 skills total and clear categorization
  • Warning against restructuring existing apps (line 'never restructure an existing app to match') shows good judgment about scope
  • Feedback submission pattern is documented and user-consent-aware
  • Agent CLI help text is well-integrated: agents are directed to `--help` before first use and `help workflow` for ordering
  • Potential minor clarity issue: the many cross-references to leaf skills assume those skills exist and have been implemented consistently; no way to verify those skills match the router's expectations
Model: claude-haiku-4-5-20251001Analyzed: Nov 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v3.0

    Contract changed: description

    ✦ AINarrows skill activation scope: removes design/app-building coverage, adds explicit EAS command usage

    triggering2026-11-20

    LATEST
  2. v2.6

    Content updated

    ✦ AIFeedback reporting now voluntary rather than mandatory; simplified reporting guidelines.

    2026-11-15

    View This Version
  3. v2.5

    Content updated

    ✦ AIIntegrates Expo Agent CLI as the primary command interface for Expo and agent-specific tasks; updates instructions for creating apps, detecting SDK versions, installing packages, and searching docs.

    2026-11-13

    View This Version
  4. v2.4

    Content updated

    ✦ AINo behavioral changes detected.

    2026-10-29

    View This Version
  5. v2.3

    Content updated

    ✦ AIUpdates feedback submission command from submit-expo-feedback@latest to @expo/agent-cli@latest feedback.

    2026-10-23

    View This Version
  6. v2.2

    Content updated

    ✦ AIRemoves expo-skill-feedback skill reference and replaces feedback guidance with direct command syntax.

    2026-10-22

    View This Version
  7. v2.1

    Content updated

    ✦ AIAdds guidance for launching Expo apps without interactive dev menu; provides reference for SDK 57 and earlier or manual URL launches.

    2026-10-18

    View This Version
  8. v2.0

    Contract changed: description

    ✦ AIRemoves framework label from skill description; activation criteria unchanged.

    triggering2026-10-03

    View This Version
  9. v1.3

    Content updated

    ✦ AIClarifies expo-brownfield skill scope: adds SwiftUI/UIKit/Android specificity and isolated/integrated build modes.

    2026-09-11

    View This Version
  10. v1.2

    Content updated

    ✦ AIBroadens scope to cover native apps using EAS for delivery; updates qualifying criteria and routing guidance for non-Expo projects.

    2026-09-10

    View This Version
  11. v1.1

    Content updated

    ✦ AIRemoved 'animations' from expo-native-ui description; added eas-update to skill map; refined routing guidance for native look and design genericism.

    2026-09-09

    View This Version
  12. v1.0

    2026-08-20

    View This VersionInitial version

Use expo/expo-overview in your dev environment

Command Palette

Search for a command to run...