What problem does it solve? Expo's default eas.json scaffold leaves developers guessing which options matter for each build profile, leading to misconfigured signing, leaked secrets in bundles, and the inability to install dev and production variants side by side. This Skill ships a proven 3-profile convention (development, preview, production) with the reasoning behind every option. ## Core Features & Use Cases - 3-Profile eas.json Template: Provides development, preview, and production profiles with correct distribution channels, build types (APK vs AAB), simulator targets, and autoIncrement settings. - Variant-Based App Configuration: Uses the APP_VARIANT environment variable with app.config.ts to switch bundle IDs, app names, and API URLs so all three variants install on one device. - Secrets and Signing Guidance: Explains how to keep secrets out of eas.json using eas secret, configure credentials with eas credentials, and set up submit config for one-command store submission. - Use Case: A mobile team needs QA to test a preview build against staging APIs while production stays installed on the same phone. Apply this Skill to generate the eas.json profiles and app.config.ts variant logic that make side-by-side installs work. ## Quick Start Ask the agent to configure EAS Build profiles for your Expo app using the development, preview, and production convention with per-variant bundle IDs.