What problem does it solve? Debugging failures in multi-layer systems is difficult because errors at a lower layer (like a broken route handler) surface as confusing symptoms at higher layers (like an empty dashboard). This Skill enforces a bottom-up validation sequence so each layer is verified before the next is tested, isolating failures to the layer where they actually occur. ## Core Features & Use Cases - Four-Layer Validation Model: Defines L1 (domain plugin routes), L2 (API proxy), L3 (browser and traffic capture), and L4 (dashboard UI) with per-layer curl commands and expected outputs. - Failure Diagnosis Guides: Lists common failure modes per layer, such as 503 browser-not-connected errors, unregistered routes, empty traffic buffers, and CAPTCHA-blocked pages. - Gate Sequence: Provides a four-gate checklist (routes registered, proxy works, real data returned, detail data returned) that must pass before building UI. - Use Case: After generating proxy routes for a new website, run the gate sequence to confirm each layer works before asking the dashboard builder to render the data. ## Quick Start Ask the agent to systematically validate the new domain's API routes layer by layer before building the dashboard.
