ui-debug

# UI Debug Debug a frontend issue using Playwright automation. This skill builds the server, launches a real instance, writes Playwright scripts to reproduce and diagnose the problem, then fixes it. ## Step 0: Parse the bug description The user describes a UI bug in `$ARGUMENTS` or in the conversation. Extract: - **What happens** (e.g., "typing in the second terminal session triggers global shortcuts instead of going to the terminal") - **Expected behavior** (e.g., "keystrokes should go to the terminal") - **Repro steps** if provided (e.g., "open terminal, click +, type 'e'") ## Step 1: Read the relevant code Before writing any Playwright script, read the source files involved in the bug. Understand the code path that should handle the user's action. Form a hypothesis about what might be wrong. ## Step 2: Build and start the server 1. Stash unrelated dirty files if needed so the build succeeds: ```bash git stash push -m "temp: ui-debug stash" -- $(git diff --name-only | grep -v '<relevant-files>') ``` 2. Build the server binary to a temp location: ```bash go build -o /tmp/wallfacer-debug . ``` 3. Start the server on a temporary port (18080) with no browser: ```bash /tmp/wallfacer-debug run -addr :18080 -no-browser & ``` 4. Wait for it to be healthy: ```bash sleep 2 && curl -s http://localhost:18080/api/debug/health ``` ## Step 3: Write a Playwright repro script Write a script at `/tmp/ui-debug-repro.mjs` that: - Uses `chromium`...