Expo Toolkit
by rahulkeerthi
Expo Toolkit transforms your Claude Code environment into a full-lifecycle React Native development command center, covering everything from initial project scaffolding to app store submission and post-launch OTA updates. Instead of juggling scattered documentation, terminal commands, and submission checklists, you get a single unified plugin that walks you through each stage of mobile app development with interactive wizards, pre-flight validation, and expert guidance baked in. The plugin ships with seven slash commands that map directly to the milestones every Expo developer hits. The /init command sets up your project with EAS configuration, environment-specific bundle identifiers, and build profiles tailored to development and production. When you are ready to ship, /build runs configuration validation before triggering EAS builds, catching mismatches in app.config.js, credentials, and native module compatibility before they cost you a failed build cycle. The /ios-preflight and /android-preflight commands provide structured submission checklists for App Store Connect and Google Play Console respectively, walking you through every requirement so nothing slips through. Beyond builds, the toolkit includes three specialized agents: a build troubleshooter that diagnoses EAS build failures, an Expo documentation researcher, and a RevenueCat integration guide for monetization. The /changelog command converts your git history into polished store-ready release notes, while /screenshots sets up Fastlane automation for generating device screenshots across required dimensions. For teams shipping frequently, /update handles EAS Update deployments with environment verification and compatibility checks, making over-the-air updates safer and more predictable. The plugin covers six core skill areas including EAS configuration, Fastlane automation, App Store Connect procedures, Google Play submission requirements, RevenueCat SDK integration, and Expo best practices.
Installation
Key Features
- ✓Full project scaffolding with EAS configuration, environment-specific bundle IDs, and build profiles through an interactive /init wizard
- ✓Pre-flight submission checklists for both App Store Connect and Google Play Console that catch missing assets, metadata gaps, and compliance issues before you submit
- ✓Build validation that checks your app.config.js, credentials, and native module compatibility before triggering EAS builds, saving failed build cycles
- ✓Automated changelog generation that transforms raw git history into polished, store-ready 'What's New' copy for both platforms
- ✓Fastlane screenshot automation setup that generates device screenshots across all required App Store and Play Store dimensions
- ✓Safe OTA update deployments with EAS Update environment verification and backward compatibility checks
Use Cases
- →You are launching your first Expo app and staring at the EAS documentation trying to figure out build profiles, environment variables, and bundle ID conventions. You run /init and the wizard configures everything in minutes, setting up development and production profiles with the correct naming patterns so your first EAS build succeeds on the first try.
- →Your app is feature-complete and you need to submit to both the App Store and Google Play this week. You run /ios-preflight and /android-preflight to get structured checklists that walk through every submission requirement, from privacy nutrition labels and export compliance on iOS to content ratings and data safety forms on Android, so nothing gets rejected.
- →You shipped a critical bug fix and need to push an OTA update to production users without going through a full app store review cycle. You run /update, which verifies your EAS Update configuration, checks runtime version compatibility, and confirms the correct environment target before deploying, preventing accidental updates to the wrong channel.
- →Your app is growing and you want to add a subscription paywall using RevenueCat. The built-in RevenueCat docs agent guides you through SDK integration, entitlement configuration, and testing purchase flows without leaving your Claude Code session.
- →Release day is here and your product manager needs polished release notes for both stores. You run /changelog and it pulls your recent git commits, filters out internal changes, and generates user-friendly 'What's New' text formatted for each platform's character limits and style conventions.