Set up EAS
Link the app to Expo and separate development, preview, and production builds.
EAS is Expo's cloud build and update system. The starter already has the profile shape; you connect it to your Expo account and final app identity.
Prompt
Read agent-skills/setup-eas.md. Confirm my Expo account/organization and final
app identifiers, then link this project with EAS. Preserve separate development,
preview, and production profiles, matching channels, and app-version runtime
policy. Explain credentials and external account actions before performing them.The three profiles
| Profile | Purpose |
|---|---|
| Development | Your installable development client with hot reload |
| Preview | Production-like internal build for QA and stakeholder testing |
| Production | Store artifact for App Store Connect or Play Console |
Keep environment values separate across development, preview, and production.
Public client configuration may use EXPO_PUBLIC_*; server secrets do not belong
in EAS public app values. Let EAS manage signing credentials unless your
organization already has a deliberate credential policy.
Verify identity before shipping
Ask the agent to check EAS project owner, project ID, app name, slug, iOS bundle ID, Android package, scheme, channel, runtime, and environment. Changing the bundle/package identifier after store records exist is costly.
Build one development client per platform and record the install links for your team. Never commit downloaded credentials.