Need
Mobile framework
Default options
Expo and React Native
Why it's needed
Expo gives Codex a managed React Native path with fast iteration, compatible packages, and deployment tooling.
Codex use case
Go from a mobile-app idea to a working Expo app with the dedicated plugin.
Use Codex with the Expo plugin to scaffold React Native apps, stay inside Expo Router and Expo-native package conventions, test quickly with Expo Go, and move to dev clients or EAS builds only when the app needs them.
Go from a mobile-app idea to a working Expo app with the dedicated plugin.
Use Codex with the Expo plugin to scaffold React Native apps, stay inside Expo Router and Expo-native package conventions, test quickly with Expo Go, and move to dev clients or EAS builds only when the app needs them.
Use Codex with the Expo plugin to scaffold React Native apps, stay inside Expo Router and Expo-native package conventions, test quickly with Expo Go, and move to dev clients or EAS builds only when the app needs them.
Related links
| Skill | Why use it |
|---|---|
| Expo | Use Expo-authored skills for Expo Router UI, native-feeling components, data fetching, dev clients, deployment, upgrades, modules, and Codex Run action wiring. |
Expo is a strong default when you want Codex to move from a mobile-app idea to a
tested React Native app. The useful loop is expo start first, Expo Go
on a device next, and then a dev client or EAS build only when the app needs
custom native code, store distribution, or a capability that Expo Go can’t run.
That keeps Codex focused on the app workflow instead of spending the first pass on native IDE setup, simulator setup, provisioning, or build configuration.
Expo published an Expo plugin that gives Codex Expo-native guidance for Expo Router, native UI, forms, navigation, animations, data fetching, NativeWind setup, Expo modules, dev clients, deployment, upgrades, and Codex Run action wiring.
Use it when Codex is building new Expo screens, adding packages, wiring API calls, preparing a dev client, or getting an app ready for TestFlight, App Store, Play Store, or EAS Hosting.
Optionally, add the Expo MCP Server when the task needs current Expo documentation lookup, compatible package installation, EAS build and workflow operations, screenshots, simulator interaction, React Native DevTools, or TestFlight data.
npx expo install when adding
Expo packages.Need
Default options
Why it's needed
Need
Mobile framework
Default options
Expo and React Native
Why it's needed
Expo gives Codex a managed React Native path with fast iteration, compatible packages, and deployment tooling.
Need
Routing
Default options
Why it's needed
Expo Router keeps navigation file-based and predictable, which helps Codex add screens and flows without inventing a custom routing layer.
| Need | Default options | Why it's needed |
|---|---|---|
| Mobile framework | Expo and React Native | Expo gives Codex a managed React Native path with fast iteration, compatible packages, and deployment tooling. |
| Routing | Expo Router | Expo Router keeps navigation file-based and predictable, which helps Codex add screens and flows without inventing a custom routing layer. |
Use Codex with ImageGen to turn a rough idea into a visual direction, implement the smallest...
Use Codex to turn a game brief into first a well-defined plan, and then a real browser-based...
Use Codex and the Build iOS Apps plugin to identify the actions and entities your app should...