mobile-app-developer — Claude Code skill: setup and features
mobile-app-developer guides Claude Code through scaffolding, previewing, and shipping Expo or React Native apps via EAS cloud builds without needing Xcode or a Mac.
MIT ★ 138 updated 2026-09-03
npx skills add happycapy-ai/Happycapy-skills --skill mobile-app-developer -a claude-codeWhat mobile-app-developer does
This skill structures mobile app delivery from initial scaffolding to store distribution. It splits guidance across three modular guides: development.md covers app.json configuration, dependencies, and asset generation; preview.md handles web previews with device mockups and Expo Go QR codes; publishing.md manages EAS Build and EAS Submit execution.
Workflows target Linux sandboxes and CI environments. For iOS distribution, the skill relies on App Store Connect API keys (.p8) to bypass Apple two-factor authentication, removing any need for macOS hardware. Android releases use Google Play Console Service Account keys, though Google requires uploading the initial AAB manually before automation can take over.
Local toolchains and native builds via expo prebuild fall outside this playbook. The hosting environment requires Node.js 18+, npm 9+, curl, ImageMagick for graphic conversion, and expect for non-interactive credential setups.
What it helps with
- Scaffold an Expo application and resolve peer dependency issues
- Generate an in-browser phone preview with an Expo Go QR code
- Automate TestFlight distribution without Xcode or Apple 2FA prompts
- Prepare application icons and splash images matching app store standards
- Diagnose EAS Build failures involving lock files or credentials
Example prompts for the agent
- Scaffold a new Expo project and generate a web preview with a phone frame
- Configure eas.json submit settings using my ASC API key and deploy to TestFlight
- Check the EAS build failure logs and resolve the broken lock-file dependencies
How to install mobile-app-developer
1Skills CLI (Vercel)
npx skills add happycapy-ai/Happycapy-skills --skill mobile-app-developer -a claude-code2Manually: put the files in place
~/.claude/skills/mobile-app-developer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mobile-app-developer/
1Skills CLI (Vercel)
npx skills add happycapy-ai/Happycapy-skills --skill mobile-app-developer -a codex2Manually: put the files in place
.agents/skills/mobile-app-developer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add happycapy-ai/Happycapy-skills --skill mobile-app-developer -a cursor2Manually: put the files in place
.cursor/skills/mobile-app-developer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install happycapy-ai/Happycapy-skills skills/mobile-app-developer2Manually: put the files in place
.github/skills/mobile-app-developer/SKILL.md1Skills CLI (Vercel)
npx skills add happycapy-ai/Happycapy-skills --skill mobile-app-developer -a gemini-cli2Platform CLI
gemini skills install https://github.com/happycapy-ai/Happycapy-skills --path skills/mobile-app-developerManually: put the files in place
.devin/skills/mobile-app-developer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mobile-app-developer
How to install mobile-app-developer in Claude Code?
Run npx skills add happycapy-ai/Happycapy-skills --skill mobile-app-developer -a claude-code in your terminal.
What does mobile-app-developer do?
It orchestrates the React Native and Expo delivery pipeline, covering project setup, assets, web previews, and automated EAS publishing to TestFlight and Google Play.
Can I publish iOS builds from a Linux environment?
Yes. EAS handles builds in the cloud, while an App Store Connect .p8 API key authenticates submissions without macOS or 2FA prompts.
Source text
SKILL.md · MIT
--- name: mobile-app-developer description: End-to-end mobile app development and publishing using Expo + EAS. Covers project scaffolding, asset preparation, peer-dep / lock-file troubleshooting (development.md), web preview with phone frame and Expo Go QR code (preview.md), AND automated build + submit to TestFlight / App Store (publishing.md), with full automation via Apple ASC API Key (no Mac, no Xcode, no 2FA required). Use when the user wants to build, test, preview, publish, or automate the release pipeline of a React Native / Expo iOS or Android app. --- # mobile-app-developer End-to-end playbook for shipping an Expo / React Native app — from scaffolding to TestFlight / Play Store — fully automated from a Linux sandbox. ## When to Trigger Trigger this skill when the user wants to: - Scaffold or modify a React Native / Expo project - Run / test / debug the app locally (Expo Go, dev client, simulator) - **Generate a web preview page** with phone frame + Expo Go QR code - Configure EAS Build (cloud build) for iOS or Android - Publish to **TestFlight** (iOS internal testing) or **Google Play Internal Testing** - Submit to App Store / Play Store public release - Set up ASC API Key auth (bypass Apple 2FA) - Replace icons / splash screens for store compliance - Diagnose EAS build failures (peer deps, lock files, credentials, fingerprint, etc.) Do NOT trigger for: pure native iOS/Android (no Expo), Flutter, Cordova/Capacitor, KMP/Compose Multiplatform. ## Skill Layout This skill is split into focused documents. Read the relevant one(s) on demand — do NOT preload all. | File | Read when… | |---|---| | **`development.md`** | Setting up project, installing deps, configuring `app.json`, preparing icons/splash, running on simulator/device, fixing peer-dep / lock-file errors, managing env vars / secrets | | **`publishing.md`** | Configuring `eas.json` submit profile, ASC API Key / Play Service Account, running build + submit, diagnosing submit failures, App Store / Play Store metadata checklists | | **`preview.md`** | Generating a web preview page with phone frame + Expo Go QR code. Uses Expo Web (react-native-web) static export for browser preview and Expo dev server for real-device QR scanning | If the user's task spans multiple (e.g. "build a new Expo app and ship it to TestFlight"), read `development.md` first, then `publishing.md`. ## Default Tech Stack | Layer | Choice | |---|---| | Framework | Expo (latest stable — check `https://docs.expo.dev/versions/latest/` before scaffolding) | | Build / Distribution | EAS Build + EAS Submit (Expo cloud) | | Auth (Apple) | App Store Connect API Key (`.p8`) — bypasses 2FA | | Auth (Google) | Play Console Service Account JSON | | Auth (Expo) | Personal Access Token via `EXPO_TOKEN` | ## Hard Preconditions Before starting **any** build or publish work, confirm with the user: - Expo account + `EXPO_TOKEN` (https://expo.dev/accounts/<user>/settings/access-tokens) - For iOS: - Apple Developer account (paid, $99/year) - ASC API Key: `.p8` file + Issuer ID + Key ID (role ≥ App Manager; ≥ Admin to create certs) - Apple Team ID + ASC App ID + Bundle Identifier - For Android: - Google Play Console account ($25 one-time) - Service Account JSON key (created in Play Console → API access) - Package name + Play Console app already created - **First AAB must be uploaded manually to Play Console** before automation works If anything is missing, **ask the user** before proceeding. Do not guess. ## Sandbox Requirements The sandbox/CI must have: ```bash node --version # >= 18 npm --version # >= 9 convert -version # ImageMagick — for icon/splash conversion expect -v # for first-time non-interactive credential setup curl --version # for fetching build logs ``` Quick check: ```bash for cmd in node npm convert expect curl; do command -v $cmd >/dev/null 2>&1 && echo "[OK] $cmd" || echo "[MISSING] $cmd" done ``` If anything is missing, install before continuing (`apt-get install imagemagick expect`). ## Architecture Recommendation | Phase | AI/API key location | Why | |---|---|---| | Internal testing (TestFlight / Play Internal) | OK to call AI Gateway directly from client | Speed of iteration; risk is bounded by closed tester pool | | Public release | **MUST** proxy through your own backend | Embedded keys can be extracted from any IPA/AAB | ## Useful URLs - Expo SDK matrix: https://docs.expo.dev/versions/latest/ - EAS dashboard: `https://expo.dev/accounts/<owner>/projects/<slug>/builds` - ASC API Keys: https://appstoreconnect.apple.com/access/integrations/api - Play Console API access: https://play.google.com/console → Setup → API access - Expo PAT: https://expo.dev/accounts/<user>/settings/access-tokens ## Notes - All commands tested on Linux. macOS users get extra options (local Xcode, simctl) which this skill avoids for portability. - Treat `.p8` files and Service Account JSONs like passwords. Always gitignore (`*.p8`, `*-service-account.json`). - This skill assumes EAS cloud build. Local builds (`expo prebuild` + native toolchain) are out of scope.
© happycapy-ai · MIT · happycapy-ai/Happycapy-skills