mcpField
E
expo-deployment

expo-deployment

github.com/sickn33Cloud & DevOps48.8k120 installsUpdated today
Repository

About expo-deployment

expo-deployment is a skill for deploying Expo apps with EAS, covering production builds and submissions for iOS and Android as well as web deployment. It is intended for teams preparing releases, configuring build profiles, and managing versions and store metadata.

Key features

  1. 01Build production iOS and Android apps
  2. 02Submit builds to app stores and TestFlight
  3. 03Configure EAS build and submit profiles
  4. 04Manage app versions and build numbers
  5. 05Deploy web bundles and API routes
  6. 06Automate deployment with EAS Workflows

Use cases

  1. 01Prepare an Expo app for App Store or Google Play release
  2. 02Publish an iOS beta build through TestFlight
  3. 03Deploy an Expo web app and API routes
  4. 04Set up automated build and deployment workflows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill expo-deployment

After installing, type/expo-deploymentin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
app-store-metadata.md
ios-app-store.md
play-store.md
testflight.md
workflows.md

Details

From the project README

Deployment

When to Use

Use this skill when you need deploy Expo apps to production with EAS — build and submit to the iOS App Store, Google Play Store, and TestFlight, configure eas.json build and submit profiles, manage app versions and build numbers, publish App Store metadata and ASO, and deploy web bundles and API routes via EAS...

This skill covers deploying Expo applications across all platforms using EAS (Expo Application Services).

References

Consult these resources as needed:

  • ./references/workflows.md -- CI/CD workflows for automated deployments and PR previews
  • ./references/testflight.md -- Submitting iOS builds to TestFlight for beta testing
  • ./references/app-store-metadata.md -- Managing App Store metadata and ASO optimization
  • ./references/play-store.md -- Submitting Android builds to Google Play Store
  • ./references/ios-app-store.md -- iOS App Store submission and review process

Before cloud builds, submissions, metadata pushes or deployments, confirm the exact project/account, artifact, track/channel and cost. Prepare configuration first; publishing requires the user’s authorized scope. Pin a reviewed CLI version for automation rather than floating @latest.

Quick Start

Install EAS CLI
npm install -g eas-cli
eas login
Initialize EAS
npx eas-cli@latest init

eas init links/creates the EAS project. Run eas build:configure to configure build profiles and review the resulting eas.json.

Build Commands

Production Builds
# iOS App Store build
npx eas-cli@latest build -p ios --profile production

# Android Play Store build
npx eas-cli@latest build -p android --profile production

# Both platforms
npx eas-cli@latest build --profile production
Submit to Stores
# iOS: Build and submit to App Store Connect
npx eas-cli@latest build -p ios --profile production --auto-submit

# Android: Build and submit to Play Store
npx eas-cli@latest build -p android --profile production --auto-submit

# Shortcut for iOS TestFlight
eas build -p ios --profile production --auto-submit

Web Deployment

Deploy web apps using EAS Hosting:

# Deploy to production
npx expo export -p web
npx eas-cli@latest deploy --prod

# Deploy PR preview
npx eas-cli@latest deploy

Expo Router API routes deploy together with the web bundle on EAS Hosting — eas deploy ships both. To author or configure the API routes themselves, use the expo-api-routes skill.

EAS Configuration

Standard eas.json for production deployments:

{
  "cli": {
    "version": ">= 16.0.1",
    "appVersionSource": "remote"
  },
  "build": {
    "production": {
      "autoIncrement": true,
      "ios": {
        "resourceClass": "m-medium"
      }
    },
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    }
  },
  "submit": {
    "production": {
      "ios": {
        "appleId": "[email protected]",
        "ascAppId": "1234567890"
      },
      "android": {
        "serviceAccountKeyPath": "./google-service-account.json",
        "track": "internal"
      }
    }
  }
}

Platform-Specific Guides

iOS
  • Use eas build -p ios --profile production --auto-submit for quick TestFlight submissions
  • Configure Apple credentials via eas credentials
  • See ./references/testflight.md for credential setup
  • See ./references/ios-app-store.md for App Store submission
Android
  • Set up Google Play Console service account
  • Configure tracks: internal → closed → open → production
  • See ./references/play-store.md for detailed setup
Web
  • EAS Hosting provides preview URLs for PRs
  • Production deploys to your custom domain
  • See ./references/workflows.md for CI/CD automation

Automated Deployments

EAS Workflows automate the build → submit → update → deploy pipeline for CI/CD. See ./references/workflows.md for deployment-oriented examples. To author or validate workflow YAML, use the expo-cicd-workflows skill — it works from the live workflow schema.

Version Management

EAS manages version numbers automatically with appVersionSource: "remote":

# Check current versions
eas build:version:get

# Manually set version
eas build:version:set -p ios  # interactive; verify selected project/value

Monitoring

# List recent builds
eas build:list

# Check build status
eas build:view

# View submission status
# Inspect the exact submission in the EAS project dashboard

Limitations

  • Use this skill only when the task clearly matches its upstream product or API scope.
  • Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
  • Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Comments

Markdown supported