What problem does it solve? Code that compiles and type-checks can still fail at runtime. This Skill closes that gap by verifying every edit against a live next dev server, cross-checking Next.js's own introspection endpoint with a real browser session so you confirm actual behavior, not just build health. ## Core Features & Use Cases - Dual-view verification: Combines the /_next/mcp endpoint (routes, RSC, server actions, compilation issues, server-side errors) with agent-browser (DOM, console, network, React fiber, render counts) to cross-check the same running app. - Structured preflight and loop: Enforces version floors (Next.js 16.3+ with Turbopack, agent-browser >= 0.31.1), probes tool availability, then runs an edit/verify cycle covering compilation, runtime errors, user-visible behavior, and React-level rendering. - Session-persistent browser testing: Uses worktree-scoped session ids with cookie/storage restore so authenticated pages stay logged in across verification loops. - Use Case: After editing a server component, confirm via get_compilation_issues that Turbopack compiled cleanly, check get_errors for runtime failures, then drive the page in a real Chrome session to assert the user actually sees the updated UI. ## Quick Start Verify my last edit to the dashboard route actually works in the running Next.js dev server, checking both compilation and what renders in the browser.
