Expo Builder

Expo/EAS non-prompting setup checklist (env, SDK/beta status, CNG, pnpm pins and override, eas.json images, sign-in state, budget). Run at the start of any Expo task, after expo-builder-core, or on "check setup".

Expo Builder's first chat with a new owner: read expo-builder-core, introduce the bot, ask setup questions one at a time (name, account, budget, package manager, Apple/Google, GitHub, guidance level), save them, run preflight and offer routines.

Expo Builder shared reference: box env.sh, pnpm conventions, SDK 58 pnpm-workspace.yaml, eas.json image pins, testing ladder, autonomy guards, default budgets, evidence contract. Read when another Expo skill points here.

Expo Builder routine prompts and cron schedules (EAS failure watch, simulator janitor, weekly SDK/tooling check, release health, store review watch, Launch follow-up, credit watch). Use when creating or adjusting routines.

Expo/EAS: show or test an app on a remote iOS/Android EAS Simulator (fingerprint dev-build reuse, live tunnel or static build, agent-device screenshots and recordings, mandatory cleanup). Use for "show me on iOS", PR evidence or bug repro.

Expo/EAS: set up an EAS Workflows PR preview pipeline (fingerprint → reuse or repack a build → PR-branch EAS Update → GitHub comment), validated with eas workflow:validate. Use for "set up CI" or onboarding an Expo repo.

Expo: first App Store/TestFlight, Play, web or Meta VR release via Expo Launch (create-launch CLI): ask first, upload a clean staged copy, hand over the link, follow up via EAS. Use for "launch it" / "get it on TestFlight" with no store setup yet.

Expo: native look-and-feel checklist (native headers, tabs, sheets, menus, @expo/ui, SF Symbols, semantic colors, safe areas, motion, haptics, keyboard, data states). Use when building or reviewing UI, on "make it feel native" / "polish this", and in expo-verify-change.

Expo/EAS: publish an over-the-air EAS Update to a preview or PR channel with runtime-compatibility and rollout checks; production updates are drafted with rollout and rollback commands only. Use for "push an update".

Expo/EAS: read-only production release health (update insights, channel insights, EAS Observe, TestFlight/Play crashes). Use after a production rollout or weekly; recommends but never performs rollbacks.

Expo/EAS: just-in-time sign-in for eas-cli (device login in chat), Expo Launch, Expo MCP, GitHub and App Store/Play credentials. Run before an EAS step that needs auth, after a failed auth probe, or on agent-cli exit 7.

Expo: create a new Expo app (SDK 58 default, SDK 57 fallback) with pnpm, the SDK 58 beta react-native override, pinned EAS images and a green lint/tsc baseline. Use for "new app" / "start a project" requests.

Expo: upgrade a project's SDK (e.g. 57 → 58) on a branch with a draft PR: pnpm react-native override and its removal at stable, EAS image switch, breaking-change checklist. Use for "upgrade to SDK N" or when the weekly check finds a newer SDK.

Expo/EAS: produce an installable EAS build (simulator/dev or internal preview) with fingerprint reuse, pinned build images, queue and budget awareness, and build polling. Use for "build it", "make a preview build", "get me an APK".

Expo: fetch the official expo/skills library on demand (shallow clone, daily update, pinned fallback), pick the matching upstream skill, read it and apply Expo Builder's correction overlay. Use before Expo/EAS work an upstream skill covers.

Expo/EAS: diagnose a failed EAS build, workflow run or submission (error codes, build-log phases, pnpm install failures, SDK 58 failure classes) and propose or open a fix. Use when an EAS job failed or a routine finds one.

Expo: verify a code change before claiming it's done: lint, tsc, expo-doctor, dependency checks, frozen pnpm install, iOS/Android export, web screenshot and the JS-only vs native-rebuild verdict. Use before any "done" in an Expo project.