launch-applisted

# Launch App for UI Verification & Debugging <WHEN-TO-USE> Invoke this skill when you need to: - **Verify UI changes** — after editing widgets, styles, or layouts - **Debug visual issues** — layout overflow, missing widgets, wrong colors/spacing - **Test navigation flows** — tap through screens, verify transitions - **Inspect runtime state** — widget tree, app logs, runtime errors Do NOT invoke for: unit tests, static analysis, code-only changes with no visual impact. </WHEN-TO-USE> <HARD-RULES> - ALWAYS navigate with the nav console when the grammar can name the destination — tapping through the tree is the fallback, not the default - NEVER guess widget finders — always inspect the widget tree first - ALWAYS screenshot after hot reload to confirm changes visually - ALWAYS clean up ALL processes on exit (flutter run + app executable + relay + agent) - Use hot_reload for UI changes, hot_restart for state/initialization changes - Prefer `ByValueKey` > `ByText` > `ByType` for finding widgets (most stable to least) </HARD-RULES> ## Startup Sequence Execute steps sequentially. Each step depends on the previous. ### Step 1: Start Relay (Optional) Run relay in background to test mobile access. ```bash cd relay && bun run dev & # start relay on :8080 ``` Verify it started by checking output. If port 8080 is in use: ```bash netstat -ano | grep ":8080" taskkill //PID <pid> //F ``` ### Step 2: Launch Flutter App The dart MCP server exposes no launch tool — start the app yo