What problem does it solve? Code edits that pass type-checking and compilation can still fail at runtime. This Skill closes that gap by verifying changes against a live next dev server through two cross-checking views: Next.js's own /_next/mcp introspection endpoint and a real Chrome browser driven by the agent-browser CLI. ## Core Features & Use Cases - Dual-view verification: Combines framework-level data from /_next/mcp (routes, RSC, server actions, errors, compilation issues) with browser-level observations (DOM, console, network, React fiber). - Four-mode failure detection: Checks that code compiles, runs without errors, behaves as intended in the UI, and behaves correctly at the React component level (render counts, suspense fallbacks, server/client boundaries). - Session-persistent browser testing: Uses worktree-scoped agent-browser sessions with saved login state so authenticated pages stay accessible across loops. - Use Case: After editing a server action in a Next.js 16 app, confirm via get_compilation_issues that Turbopack compiled cleanly, then drive the page in Chrome to assert the user-visible result and inspect React render behavior. ## Quick Start Start next dev, then ask the agent to verify that my latest edit to the dashboard page actually renders and behaves correctly in the browser.