mobile-emulator-start — Metro + Android emulator in a sane order

Degree of freedom: MIXED. Reuse vs fresh Metro [HIGH freedom]; port kill, boot, reverse, /status, then intent [LOW freedom — run exactly].

Deliver a working dev loop (emulator online → tunnel → bundler ready → app intent) without burning time on duplicate Metros, stale caches, or racing the dev client ahead of /status.

Pair with mobile-emulator-test for full QA; this skill focuses on bring-up + terminal hygiene.

How to reason

1. Inspect — existing terminals, curl /status, adb devices
2. Decide — reuse a healthy Metro vs one explicit fresh wipe
3. Order — free ports → boot AVD → reverse → Metro → wait /status
4. Launch — intent only after packager-status:running

Worked example