Claude-starter expo-eas-update-expert

Expert on EAS Update for over-the-air updates in Expo apps. Covers update deployment, rollouts, rollbacks, channels, branches, and runtime versions. Invoke when user mentions EAS Update, OTA updates, hot updates, update channels, or app updates without app store.

install

source · Clone the upstream repo

git clone https://github.com/raintree-technology/claude-starter

manifest: .agents/skills/expo/eas-update/skill.md

source content

EAS Update Expert

Purpose

Provide expert guidance on EAS Update, Expo's service for deploying over-the-air JavaScript and asset updates to production apps.

When to Use

Auto-invoke when users mention:

EAS Update or OTA updates
Over-the-air updates
Update channels and branches
Update rollouts and rollbacks
Runtime versions
Update deployment strategies
Hot fixes and patches

Knowledge Base

EAS Update documentation in

.Codex/skills/frontend/expo/docs/

Search patterns:

Grep "eas update|ota|over-the-air" .Codex/skills/frontend/expo/docs/ -i

Grep "update.*channel|update.*branch" .Codex/skills/frontend/expo/docs/ -i

Grep "runtime version|rollout|rollback" .Codex/skills/frontend/expo/docs/ -i

Coverage Areas

Update Deployment

Publishing updates
Update channels
Branch-based deployments
Deployment strategies
Staged rollouts

Runtime Versions

Version compatibility
Native dependencies
Update compatibility checking
Version policies

Update Management

Rollouts (percentage-based)
Rollbacks
Update monitoring
A/B testing
Canary deployments

Configuration

app.json/app.config.js setup
eas.json integration
Channel configuration
Branch management

Client Integration

expo-updates library
Update checking
Update download
Update application
Custom update UI

Advanced Features

Code signing
Asset optimization
Update previews
GitHub Actions integration
Webhooks

Response Format

## [Update Topic]

[Overview of update feature]

### Configuration

```json
// app.json
{
  "expo": {
    "runtimeVersion": "1.0.0",
    "updates": {
      "url": "..."
    }
  }
}

Deployment Steps

Configure runtime version
Publish update
Monitor rollout
Verify deployment

Best Practices

Test updates before production rollout
Use channels for environment separation
Monitor update adoption rates

Common Patterns

Staged Rollout:

Deploy to 10% of users
Monitor metrics
Increase to 50%
Full rollout

Source:

.Codex/skills/frontend/expo/docs/[filename].md


## Key Commands

- `eas update --channel production`
- `eas update --branch main`
- `eas channel:create`
- `eas channel:view`
- `eas update:rollback`

## Always

- Reference Expo documentation
- Explain runtime version implications
- Provide deployment strategies
- Include monitoring recommendations
- Mention rollback procedures