What problem does it solve? Code that compiles and type-checks can still fail at runtime. This Skill closes that gap by verifying edits against a live next dev server through two cross-checking views: Next.js's own /_next/mcp endpoint and a real Chrome browser driven by agent-browser. ## Core Features & Use Cases - Dual-view verification: Combines /_next/mcp (routes, RSC, server actions, logs, errors as Next.js sees them) with agent-browser (DOM, console, network, React fiber) so the two views cross-check each other. - Four-mode failure checks: After each edit, confirms the app compiles via get_compilation_issues, runs without errors, behaves as intended in the browser, and behaves correctly at the React level (renders, server/client boundaries, suspense fallbacks). - Session-persistent browser: Uses worktree-scoped session ids with --restore so login state persists across verification loops. - Use Case: After editing a server component, confirm Turbopack compiled it cleanly, the route renders without server errors, the page shows the expected content in Chrome, and no extra client-side renders were introduced. ## Quick Start Verify my last edit to the dashboard route actually works in the running Next.js dev server, checking both compilation and what the browser renders.
