What problem does it solve? Debugging end-to-end test failures across a Flutter web app, Firebase Emulators, and Stripe webhooks is slow and error-prone because failures can originate in infrastructure setup, backend Cloud Functions, or test assertions. This Skill provides a systematic methodology and a catalog of known failure patterns to pinpoint root causes quickly. ## Core Features & Use Cases - Infrastructure Verification: Checklists and commands to confirm Firebase Emulators (Auth, Firestore, Functions, Hosting, Storage) and Stripe CLI are running with correct ports, project ID, and webhook signing secrets. - Failure Pattern Catalog: Nine documented root causes with symptoms and fixes, including SERVER_TIMESTAMP in arrays, paymentStatus auto-capture mismatches, multi-seller status restrictions, CallableRequest vs Flask Request errors, and stock field naming. - Debugging Workflow: Step-by-step process from isolating a failing Playwright test to querying Firestore directly via REST, resetting stock, and comparing test assertions against backend handler code. - Use Case: A Playwright test asserting paymentStatus: 'authorized' fails after checkout. The Skill identifies the auto-capture behavior and directs you to assert 'captured' instead. ## Quick Start Ask the assistant to debug a failing Playwright E2E test by name, for example to investigate why the shipping-lifecycle suite fails on payment status assertions.