What problem does it solve? When a feature "almost works" or breaks somewhere between the UI and the database, developers struggle to locate which layer failed. This Skill infers the complete user story being built and systematically verifies every boundary in the flow with concrete evidence instead of guessing. ## Core Features & Use Cases - User Story Inference: Reads recently edited files, route structure, and environment files to state the exact flow being built before checking anything. - Multi-Layer Evidence Gathering: Inspects browser console, dev server terminal, runtime logs, and environment variables, reporting findings at each layer. - Data Flow Tracing: Walks the path from UI trigger through client request, API route handler, external dependencies, and response rendering, flagging common breaks like missing awaits, wrong HTTP methods, and absent env vars. - Use Case: After starting a Next.js dev server, ask for a full verification and receive a structured report showing the status of each boundary (UI renders, client to API, API to data, response to UI) with evidence and specific fixes for the first broken boundary. ## Quick Start Start your dev server and ask the assistant to verify the full flow end to end for the feature you just built.
