What problem does it solve? Real backends rarely fail on demand, making it hard to verify how a web application behaves under failure conditions like API 500s, empty responses, aborted requests, offline mode, or blocked third-party scripts. This Skill synthesizes those failures with request interception and network throttling so you can confirm the app shows proper error UI instead of blank screens or uncaught exceptions. ## Core Features & Use Cases - Fault Injection via Routing: Fulfill matched requests with HTTP 500/503/429, empty or malformed bodies, or abort them entirely to simulate connection drops and blocked third-party hosts. - Network Throttling: Apply offline, slow-3g, fast-3g, or slow-4g presets to test loading states and timeout handling. - Graceful Degradation Assertions: Verify error banners, empty states, and retry buttons render, and confirm no uncaught console exceptions leak during failure. - Use Case: Ask what a shop page shows if the products API returns a 500 — the Skill routes the endpoint to a 500 response, navigates, asserts the error banner is visible, checks for console errors, screenshots the result, and records a pass/warning/fail verdict. ## Quick Start Test what https://shop.example.com/products shows if the products API returns a 500 error.
