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 the change actually works, not just that it builds. ## Core Features & Use Cases - Dual-view verification: Combines the /_next/mcp endpoint (routes, RSC, server actions, server logs, compilation issues) with agent-browser (DOM, console, network, React fiber) 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 agent-browser sessions with cookie/storage restore so authenticated pages stay logged in across loops. - Use Case: After editing a server component, run the loop to confirm Turbopack compiled 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 Start next dev, then ask the agent to verify your last edit works at runtime using the next-dev-loop preflight and verification loop.
