Both Expo loadouts guard the line between JavaScript and native code. One covers day-to-day work: npx expo install for SDK-matched versions, Expo Router, no secrets in EXPO_PUBLIC_ variables, Expo's MCP server, and a check on a simulator before calling it done. The other covers releases: a fingerprint runtime version, a check that says whether a change is safe as an EAS Update or needs a new build, CI that publishes to preview only, and production rollouts left to a person.
Every one installs for Claude Code, Codex CLI, Cursor, Gemini CLI, Antigravity CLI and GitHub Copilot unless its card says otherwise.
Expo rules for agents plus Expo's official MCP server: npx expo install, Expo Router, no secrets in EXPO_PUBLIC_, no production EAS releases, check on a simulator.
Checks whether an Expo change can ship as an EAS Update or needs a new build, using the native fingerprint; preview by CI, production rollouts by a person.
Looking for something narrower? Search within Expo or filter everything.