mobile-devlisted

# Mobile Dev Skill If running interactively (human present), output "Read Mobile Dev skill." to acknowledge. If running with --dangerously-skip-permissions (AFK/unattended), skip acknowledgement and proceed directly. Use this skill when: - Starting a new mobile dev session - Debugging a Metro or emulator issue - Deciding whether a native rebuild is needed - Setting up a fresh fork of Launch Core - Troubleshooting "Using Expo Go" or redbox errors --- ## Phase 0 — Read Context First Before touching the app, load the Expo Mobile instructions: ``` ~/dotfiles/instructions/expo-mobile.instructions.md ``` This file contains the stack reference, native module list, correct startup sequence, and all troubleshooting commands. Do not skip it. --- ## Phase 1 — Clean State Reset Always start from a known-clean state to avoid residual Metro/emulator confusion. ```bash # 1. Force-stop the app on emulator (swallows errors if not running) adb shell am force-stop com.launchhq.mobile 2>/dev/null || true # 2. Remove ADB reverse mappings adb reverse --remove-all 2>/dev/null || true # 3. Check current state adb devices -l lsof -nP -iTCP:8081 -sTCP:LISTEN 2>/dev/null || ss -ltn 2>/dev/null | grep ':8081' || true git status --short --branch ``` Expected clean state: - `adb devices` shows `emulator-5554 device` (or no devices if emulator not running) - Nothing listening on `8081` - Branch is what you expect --- ## Phase 2 — Dependency Health Check ```bash # Check for corrupted node_m