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 every change 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, server logs, compile issues) with agent-browser (DOM, console, network, React fiber) so framework-level and browser-level behavior are checked together. - 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 renders correctly at the React component level. - Session-persistent browser testing: Uses worktree-scoped agent-browser sessions with saved login state, so gated pages stay authenticated across edit/verify loops. - Use Case: After editing a server action in a Next.js 16 app, run the loop to confirm Turbopack compiled cleanly, the route renders without server errors, the page behaves correctly in Chrome, and no extra React renders were introduced. ## Quick Start Ask the assistant to verify that your recent Next.js code change actually works in the running dev server using the next-dev-loop skill.