What problem does it solve? When a feature "almost works" or behaves unexpectedly, developers often check only one layer and miss where the flow actually breaks. This Skill infers the complete user story being built and systematically verifies every boundary — browser, server, API route, data source, and response rendering — with concrete evidence instead of guesswork. ## Core Features & Use Cases - Story Inference: Reads recently edited files, routes, and environment files to state the exact user story before checking anything. - Layer-by-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 handler, external dependencies, and back to rendered response, flagging common breaks like missing awaits, wrong HTTP methods, and absent env vars. - Structured Verification Report: Produces a status table per boundary with evidence, issues found, and confirmed-working items. - Use Case: After starting a Next.js dev server, ask the agent to verify the full flow; it will trace a form submission from the page through the API route to the database and report exactly which boundary fails. ## Quick Start Start your dev server and ask the agent to verify the full flow end to end and confirm everything works.
