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, 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 HTTP endpoint (routes, RSC, server actions, compilation issues, server logs) with agent-browser (DOM, console, network, React fiber, vitals) to cross-check the same running app. - Four-mode failure checks: After each edit, verifies the app compiles via get_compilation_issues, runs without errors, behaves as intended in the browser, and behaves correctly at the React level (render counts, server/client boundaries, suspense fallbacks). - Session-persistent browser testing: Uses worktree-scoped session ids with --restore so login state persists across loops, and includes recovery steps for stale sessions and blank pages. - Use Case: After editing a movie details page in a Next.js 16 app, run the loop to confirm Turbopack compiled cleanly, the route renders without server errors, the cast section appears in the DOM, and no extra React renders were introduced. ## Quick Start Start next dev, then ask the agent to verify your last edit works at runtime using the next-dev-loop skill against http://localhost:3000.
