What problem does it solve? Expo mobile development sessions often fail due to stale Metro state, offline emulators, corrupted node_modules, or confusion about when a native rebuild is required. This Skill provides a deterministic startup and troubleshooting workflow so agents and developers reach a working dev client without guesswork. ## Core Features & Use Cases - Clean State Reset: Force-stops the app, clears ADB reverse mappings, and verifies port 8081 and emulator status before starting. - Native Rebuild Decision Tree: A question table determines whether changes to native modules, app.config.ts plugins, bundle IDs, or entitlements require a full rebuild versus a Metro-only restart. - Emulator and Metro Startup: Boots the verified AVD, configures adb reverse port mappings, starts Metro in development build mode, and launches the dev client via ADB intent. - Diagnostic Checklist: Systematic checks for Metro reachability, emulator connectivity via 10.0.2.2, dev client currency, and EXPO_PUBLIC_API_URL configuration. - Use Case: When a redbox appears after installing a new dependency, run the diagnostic checklist to confirm Metro is serving a development build, the emulator can reach the host, and node_modules are not corrupted. ## Quick Start Use the mobile-dev skill to reset my Expo dev environment, start the Android emulator and Metro, and verify the app loads in the development build.