expo/skills

Why pick it

You are building or maintaining an Expo / React Native app and want the agent to follow official Expo guidance — project layout, Router, native UI, SDK upgrades, and EAS — instead of inventing generic RN patterns. Source of truth stays Expo docs, Expo CLI, and EAS CLI; these skills teach agents how to apply them.

MIT, maintained by the Expo team. Skills are labeled so open-source framework work is separate from skills whose core purpose uses paid EAS services.

What you get

Framework (open source)

• Structure & nav — expo-project-structure, expo-router (file routes, stacks, modals, sheets, tabs).
• UI — expo-native-ui, expo-ui (@expo/ui), expo-tailwind-setup (Tailwind v4 / NativeWind v5).
• Data & web bridges — expo-data-fetching, expo-dom, expo-web-to-native.
• Native & brownfield — expo-module, expo-brownfield, expo-dev-client, expo-app-clip.
• Ops — expo-examples, expo-upgrade, expo-skill-feedback (feedback + opt-in telemetry controls).

Services & paid distribution (EAS)

• eas-app-stores, eas-hosting, eas-workflows, eas-observe, eas-update-insights, eas-simulator (remote iOS sim / Android emulator with browser preview on iOS).

Experimental

• Ships via the separate expo-experiments plugin (or skills CLI individually), e.g. expo-migrate-module for Modules API 1.0 → 2.0.

Expo MCP (complements skills)

Skills teach how; the Expo MCP server gives live tools (docs on demand, npx expo install, EAS builds/workflows, TestFlight crashes, simulator screenshots). Claude Code / Codex plugin installs wire MCP automatically.

Install paths

| Path | Best for | | --- | --- | | Plugin | Claude Code (claude plugin install expo@claude-plugins-official) or Codex (codex plugin add expo@openai-curated) — updates via official marketplaces | | Skills CLI | Cursor, OpenCode, Copilot, Windsurf, Gemini, Cline, Amp, and similar |

npx skills@latest add expo/skills --skill '*'   # all Expo skills; optional --agent <agent>
npx skills@latest update                       # later updates
npx skills@latest update expo-router           # one skill

Run from the project root, then restart/refresh the agent so it picks up SKILL.md files.

Why it over the others

vs generic RN / mobile skills — Expo-authored, aligned with current SDK, Router, and EAS product surfaces; free vs paid EAS is explicit in skill groupings.

vs reading docs alone — docs remain authoritative; skills package recurring workflows (upgrade, store ship, Tailwind setup, brownfield) so the agent loads the right procedure for the task.

vs inventing EAS YAML / store config — eas-* skills encode current EAS workflows, update health, and store shipping steps instead of outdated blog patterns.

When it's not the right pick

• Pure web React / Next without Expo — use web-focused skills.
• Bare React Native without Expo workflow — less overlap; brownfield skill only if you are adding Expo.
• You only need a one-off API fact — open docs.expo.dev or Expo MCP docs tools; skills are for workflows.

Quick start

# Most agents
npx skills@latest add expo/skills --skill '*'

# Claude Code plugin
claude plugin install expo@claude-plugins-official

# Codex plugin
codex plugin add expo@openai-curated

Then ask things like: Expo Router tabs/modals, Tailwind v4 + NativeWind v5, EAS preview workflows, SDK upgrade, EAS Update rollout health.

Repo: expo/skills · docs hub: docs.expo.dev/skills · catalog: skills.sh/expo/skills. Telemetry is off by default (opt-in on Claude Code only).