vite-browser-core-debug

Use this skill for first-pass diagnosis only. Escalate quickly if the problem is actually runtime or network driven.

Workflow

1. Open app and detect framework.
2. Run error-first gate (errors, logs) AND vite runtime.
3. IMMEDIATE ROUTING DECISION:
   • If vite runtime shows HMR Socket closed/error/unknown → escalate to vite-browser-runtime-diagnostics
   • If errors contains "HMR", "hot", "reload", "import", "resolve", "module", "circular", "websocket" → escalate to vite-browser-runtime-diagnostics
   • If network shows 4xx/5xx/FAIL responses → escalate to vite-browser-network-regression
   • Otherwise, continue with framework state inspection
4. Inspect framework state (vue/react/svelte tree, plus router/pinia for Vue) only if the issue still looks component-driven.
5. Validate behavior with network, screenshot, and eval.
6. Return findings with command evidence and a minimal fix path.

Escalation rules