Expo and EAS overview

Routes Expo and EAS tasks to the right Expo skill and applies shared rules: the agent CLI for Expo commands, SDK detection, version-pinned docs, SDK-matched installs and EAS login checks. Use when a task mentions Expo or EAS or the project depends on expo.

CodingPack: Expo skills135 linesexpo-overview
Author
Source
expo/skills/plugins/expo/skills/expo-overview @ 88d9bd7
License
MIT · Copyright (c) 2025-present 650 Industries, Inc. (aka Expo)

About this skill

What it does

expo-overview is the entry point to Expo's skill set and writes no app code. The agent confirms the task is Expo or EAS work (the request names Expo, EAS or an expo-* package, or package.json depends on expo), restates the goal, matches it to one of 23 Expo skills, asks when the goal is ambiguous, then loads that skill and follows it.

It also holds the shared setup rules: run Expo commands through npx --yes @expo/agent-cli@latest instead of npx expo (it adds commands that read project state and search the docs for the project's SDK), detect the SDK before giving version-specific advice, read version-pinned docs rather than latest, install packages through the agent CLI so versions match the SDK, and check the EAS login and extra.eas.projectId before builds or updates. references/launch-without-dev-menu.md shows how to open Expo Go or a development build without onboarding and the dev menu; agents/openai.yaml holds Codex display settings.

When to use it, and when not

Install it with the other Expo skills; it runs first on any Expo or EAS task, even a fully specified one. A native Swift app that uses EAS only for delivery also counts. It does not apply to React Native without Expo or EAS.

Five of the skills it routes to are in this catalog: Expo Router navigation, Native-feeling Expo screens, Expo SDK upgrade, EAS builds for the app stores and EAS Update over the air. The rest, such as expo-ui, expo-animation and eas-workflows, live only in Expo's repository, and expo-tailwind-setup is named in the map but missing even there; without them those branches of the map lead nowhere.

How to run it

The install command below puts the whole folder in place. The agent picks the skill up by its description when Expo comes up; to call it yourself:

  • Claude Code: /expo-overview, or ask for the skill by name.
  • Codex: $expo-overview.
  • Cursor: type / in the Agent chat and pick expo-overview.

Example: /expo-overview I want this app on TestFlight by Friday. Work out what is missing.

All Expo skills end with the same note: the agent may offer to send feedback to Expo through the agent CLI. The report includes project and environment details and goes out only with your consent.

How it differs from similar skills

Remotion best practices is the same kind of router for Remotion, with one difference: it carries copies of the skills it routes to in its own folder, while this overview only points to Expo skills you install separately. React Native best practices from Vercel Labs also covers Expo, but as one rulebook on lists, animation, navigation and styling. If you need a single Expo skill, call it by name; the overview steps aside only then.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/expo-overview/SKILL.md https://anymodel.org/en/skills/expo/expo-overview/SKILL.md -o ~/.claude/skills/expo-overview/LICENSE https://anymodel.org/en/skills/expo/expo-overview/LICENSE -o ~/.claude/skills/expo-overview/agents/openai.yaml https://anymodel.org/en/skills/expo/expo-overview/agents/openai.yaml -o ~/.claude/skills/expo-overview/references/launch-without-dev-menu.md https://anymodel.org/en/skills/expo/expo-overview/references/launch-without-dev-menu.md
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/expo-overview/SKILL.md https://anymodel.org/en/skills/expo/expo-overview/SKILL.md -o ~/.agents/skills/expo-overview/LICENSE https://anymodel.org/en/skills/expo/expo-overview/LICENSE -o ~/.agents/skills/expo-overview/agents/openai.yaml https://anymodel.org/en/skills/expo/expo-overview/agents/openai.yaml -o ~/.agents/skills/expo-overview/references/launch-without-dev-menu.md https://anymodel.org/en/skills/expo/expo-overview/references/launch-without-dev-menu.md
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE','agents/openai.yaml','references/launch-without-dev-menu.md') { $p = Join-Path "$HOME\.claude\skills\expo-overview" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/expo/expo-overview/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE','agents/openai.yaml','references/launch-without-dev-menu.md') { $p = Join-Path "$HOME\.agents\skills\expo-overview" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/expo/expo-overview/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/expo/expo-overview/SKILL.md

SKILL.md

Raw

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.

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack Expo skills