expo-dev-client · openai — Claude skill: build and ship Expo dev clients
A Claude skill that walks the agent through building an Expo development client and getting it onto TestFlight or a device.
npx skills add openai/plugins --skill expo-dev-client -a codexWhat expo-dev-client does
The skill tells the agent when a development client is actually required. Most apps run fine in Expo Go, so start with npx expo start and see if anything breaks. You need a dev client for local Expo modules with custom native code, Apple targets like widgets and extensions, or third-party native modules that Expo Go does not include.
From there it covers EAS setup: eas.json needs a development profile with developmentClient: true, autoIncrement: true and appVersionSource: "remote". One command builds the iOS client and submits it to TestFlight: eas build -p ios --profile development --submit. Add --local to build on your own machine. Local iOS builds need Xcode, and installing on a physical device needs signing. When signing errors kill a build, the skill points at eas credentials.
Installing finished builds is covered too: .ipa onto a simulator with xcrun simctl install booted, onto a device with ideviceinstaller, .apk on Android with adb install. To connect the client to your dev server, run npx expo start --dev-client and scan the QR code. Build status comes from eas build:list and eas build:view.
What it helps with
- build an Expo dev client with custom native code
- submit an iOS build to TestFlight in one command
- install a local build on a simulator or device
- decide whether a dev client is needed or Expo Go will do
- fix a build that fails on signing errors
Example prompts for the agent
- build a development client for iOS and submit it to TestFlight
- does my app need a dev client or can I stay on Expo Go?
- install the local Android build on the connected device
How to install expo-dev-client
1Skills CLI (Vercel)
npx skills add openai/plugins --skill expo-dev-client -a codex2Manually: put the files in place
.agents/skills/expo-dev-client/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill expo-dev-client -a claude-code2Manually: put the files in place
~/.claude/skills/expo-dev-client/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/expo-dev-client/
Manually: put the files in place
.cursor/skills/expo-dev-client/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins expo-dev-client2Manually: put the files in place
.github/skills/expo-dev-client/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/expo/skills/expo-dev-clientManually: put the files in place
.devin/skills/expo-dev-client/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: Codex skills: how to install, where they live, how to call them
Questions about expo-dev-client
How do I install expo-dev-client in Claude?
Run npx skills add openai/plugins --skill expo-dev-client -a codex. The skill file then lives at .agents/skills/expo-dev-client/SKILL.md.
What does expo-dev-client do?
It guides the agent through building an Expo development client locally or on EAS and submitting it to TestFlight. It also explains when a dev client is needed and when Expo Go is enough.
What do I need for a local build?
An iOS build on your own machine requires Xcode. Installing on a physical device requires signing, and Android builds go on with adb install.
Source text
SKILL.md · MIT
---
name: expo-dev-client
description: Build and distribute Expo development clients locally or via TestFlight
version: 1.0.0
license: MIT
---
Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.
## Important: When Development Clients Are Needed
**Only create development clients when your app requires custom native code.** Most apps work fine in Expo Go.
You need a dev client ONLY when using:
- Local Expo modules (custom native code)
- Apple targets (widgets, app clips, extensions)
- Third-party native modules not in Expo Go
**Try Expo Go first** with `npx expo start`. If everything works, you don't need a dev client.
## EAS Configuration
Ensure `eas.json` has a development profile:
```json
{
"cli": {
"version": ">= 16.0.1",
"appVersionSource": "remote"
},
"build": {
"production": {
"autoIncrement": true
},
"development": {
"autoIncrement": true,
"developmentClient": true
}
},
"submit": {
"production": {},
"development": {}
}
}
```
Key settings:
- `developmentClient: true` - Bundles expo-dev-client for development builds
- `autoIncrement: true` - Automatically increments build numbers
- `appVersionSource: "remote"` - Uses EAS as the source of truth for version numbers
## Building for TestFlight
Build iOS dev client and submit to TestFlight in one command:
```bash
eas build -p ios --profile development --submit
```
This will:
1. Build the development client in the cloud
2. Automatically submit to App Store Connect
3. Send you an email when the build is ready in TestFlight
After receiving the TestFlight email:
1. Download the build from TestFlight on your device
2. Launch the app to see the expo-dev-client UI
3. Connect to your local Metro bundler or scan a QR code
## Building Locally
Build a development client on your machine:
```bash
# iOS (requires Xcode)
eas build -p ios --profile development --local
# Android
eas build -p android --profile development --local
```
Local builds output:
- iOS: `.ipa` file
- Android: `.apk` or `.aab` file
## Installing Local Builds
Install iOS build on simulator:
```bash
# Find the .app in the .tar.gz output
tar -xzf build-*.tar.gz
xcrun simctl install booted ./path/to/App.app
```
Install iOS build on device (requires signing):
```bash
# Use Xcode Devices window or ideviceinstaller
ideviceinstaller -i build.ipa
```
Install Android build:
```bash
adb install build.apk
```
## Building for Specific Platform
```bash
# iOS only
eas build -p ios --profile development
# Android only
eas build -p android --profile development
# Both platforms
eas build --profile development
```
## Checking Build Status
```bash
# List recent builds
eas build:list
# View build details
eas build:view
```
## Using the Dev Client
Once installed, the dev client provides:
- **Development server connection** - Enter your Metro bundler URL or scan QR
- **Build information** - View native build details
- **Launcher UI** - Switch between development servers
Connect to local development:
```bash
# Start Metro bundler
npx expo start --dev-client
# Scan QR code with dev client or enter URL manually
```
## Troubleshooting
**Build fails with signing errors:**
```bash
eas credentials
```
**Clear build cache:**
```bash
eas build -p ios --profile development --clear-cache
```
**Check EAS CLI version:**
```bash
eas --version
eas update
```
© Expo Team · MIT · openai/plugins
Similar skills
Everything for Mobile →expo-dev-client by other authors comes first.