Expo Build logo

Expo Build

Organization
TheBushidoCollective
expo-build

Use when building and deploying Expo apps with EAS Build. Covers build configuration, development builds, production builds, and app store submission.

Overview

PublisherTheBushidoCollective
Repositoryhan
Skill nameexpo-build
Stars
195
Forks
20
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by TheBushidoCollective on GitHub. Read the source before you install it.

Installation

Install the Expo Build AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/TheBushidoCollective/han.git /tmp/han
mkdir -p .claude/skills
cp -r /tmp/han/plugins/frameworks/expo/skills/expo-build .claude/skills/expo-build
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Expo Build in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Expo Build on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Expo Build is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Expo Build with EAS

Use this skill when building and deploying Expo applications using EAS (Expo Application Services) Build.

Key Concepts

EAS Build Configuration

json
// eas.json
{
  "cli": {
    "version": ">= 5.9.0"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "ios": {
        "simulator": true
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {
      "autoIncrement": true
    }
  },
  "submit": {
    "production": {}
  }
}

Build Commands

bash
# Development build
eas build --profile development --platform ios
eas build --profile development --platform android

# Preview build
eas build --profile preview --platform all

# Production build
eas build --profile production --platform all

# Local build
eas build --profile production --platform ios --local

Development Builds

json
{
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "env": {
        "NODE_ENV": "development"
      }
    }
  }
}

Best Practices

Environment Variables

json
// eas.json
{
  "build": {
    "production": {
      "env": {
        "APP_ENV": "production",
        "API_URL": "https://api.myapp.com"
      }
    },
    "staging": {
      "env": {
        "APP_ENV": "staging",
        "API_URL": "https://staging-api.myapp.com"
      }
    }
  }
}

Secrets Management

bash
# Set secrets
eas secret:create --scope project --name API_KEY --value your_api_key
eas secret:create --scope project --name GOOGLE_SERVICES_JSON --value "$(cat google-services.json)" --type file

# List secrets
eas secret:list

# Use in eas.json
{
  "build": {
    "production": {
      "env": {
        "API_KEY": "$(EAS_SECRET_API_KEY)"
      }
    }
  }
}

Version Management

json
// eas.json
{
  "build": {
    "production": {
      "autoIncrement": true,
      "ios": {
        "buildNumber": "1"
      },
      "android": {
        "versionCode": 1
      }
    }
  }
}

Build Hooks

json
{
  "build": {
    "production": {
      "prebuild": "npm run generate-assets",
      "postbuild": "npm run cleanup"
    }
  }
}

Common Patterns

Multi-Environment Builds

json
// eas.json
{
  "build": {
    "development": {
      "developmentClient": true,
      "channel": "development",
      "distribution": "internal"
    },
    "staging": {
      "channel": "staging",
      "distribution": "internal",
      "ios": {
        "bundleIdentifier": "com.myapp.staging"
      },
      "android": {
        "package": "com.myapp.staging"
      }
    },
    "production": {
      "channel": "production",
      "autoIncrement": true
    }
  }
}

Custom Native Code

json
{
  "build": {
    "production": {
      "ios": {
        "buildConfiguration": "Release"
      },
      "android": {
        "gradleCommand": ":app:bundleRelease"
      }
    }
  }
}

App Store Submission

bash
# iOS
eas submit --platform ios

# Android
eas submit --platform android

# Configure submission
# eas.json
{
  "submit": {
    "production": {
      "ios": {
        "appleId": "your.apple.id@example.com",
        "ascAppId": "1234567890",
        "appleTeamId": "AB12CD34EF"
      },
      "android": {
        "serviceAccountKeyPath": "./service-account.json",
        "track": "production"
      }
    }
  }
}

Build Monitoring

bash
# View build status
eas build:list

# View specific build
eas build:view [build-id]

# Cancel build
eas build:cancel [build-id]

Anti-Patterns

Don't Commit Secrets

json
// Bad - Secrets in eas.json
{
  "build": {
    "production": {
      "env": {
        "API_KEY": "sk_live_1234567890"
      }
    }
  }
}

// Good - Use EAS Secrets
eas secret:create --scope project --name API_KEY --value sk_live_1234567890

Don't Skip Version Increments

json
// Bad - Manual version management
{
  "build": {
    "production": {
      "autoIncrement": false
    }
  }
}

// Good - Auto increment
{
  "build": {
    "production": {
      "autoIncrement": true
    }
  }
}

Related Skills

  • expo-config: Configuring app for builds
  • expo-updates: OTA updates after builds

Frequently asked questions

What does the Expo Build AI skill do?

Use when building and deploying Expo apps with EAS Build. Covers build configuration, development builds, production builds, and app store submission.

Why use Expo Build on TypingMind?

Because you install it once and use it with any model. Expo Build is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Expo Build in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TheBushidoCollective/han/tree/main/plugins/frameworks/expo/skills/expo-build. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Expo Build?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Expo Build?

As many as you like. As long as a model supports skills, you can use Expo Build with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Expo Build AI skill free?

It is published on GitHub by TheBushidoCollective. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇