What problem does it solve? AI coding agents lack live access to Next.js runtime state and official documentation, forcing developers to manually debug errors, search docs, and verify pages by hand. This Skill connects agents to the next-devtools-mcp server so they can query errors, routes, and logs directly from a running Next.js 16+ dev server. ## Core Features & Use Cases - Runtime Diagnostics: Query a running Next.js 16+ dev server for errors, route structure, logs, config, and environment variables via the nextjs_index and nextjs_call tools. - Documentation Search: Search and retrieve official Next.js docs with the nextjs_docs two-step workflow before implementing features like generateMetadata or Cache Components. - Browser Automation: Test and verify pages with Playwright through browser_eval, including navigation, form filling, screenshots, and console message inspection. - Guided Workflows: Run pre-configured prompts to upgrade from Next.js 15 to 16 or enable Cache Components mode. - Use Case: A user reports a blank page in their Next.js app; the agent initializes context, calls nextjs://errors to find a "window is not defined" server component error, searches the docs, and applies the "use client" fix. ## Quick Start Ask the agent to initialize Next.js DevTools context and show what errors are in your running Next.js application.
