Post

Next.js
@nextjs.org

Next.js 16.3 Preview: AI Improvements More and more Next.js is written by coding agents, so we're building a framework that helps them succeed. • Auto-managed 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 • First-party Skills • Agent Browser with React introspection • Actionable error messages nextjs.org/blog/next-1...

nextjs.orgNext.js 16.3: AI ImprovementsActionable errors with paste-ready fix prompts, first-party Skills for the dev loop and Cache Components, and tooling that keeps coding agents in sync with your project.
Next.js
@nextjs.org

We've retired our knowledge Skills. The auto-managed 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 teaches agents the framework's APIs now. We have new Skills that drive multi-step workflows instead. For example, 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙 verifies each change in a real browser via 𝚊𝚐𝚎𝚗𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛.

Next.js
@nextjs.org

The 𝚗𝚎𝚡𝚝-𝚌𝚊𝚌𝚑𝚎-𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜-𝚊𝚍𝚘𝚙𝚝𝚒𝚘𝚗 Skill migrates your app to Cache Components, feature by feature. It reads the Instant Insights, applies the fixes, and verifies each route with 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙, checking in so you stay in control.

Next.js
@nextjs.org

The 𝚗𝚎𝚡𝚝-𝚌𝚊𝚌𝚑𝚎-𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜-𝚘𝚙𝚝𝚒𝚖𝚒𝚣𝚎𝚛 Skill grows a route's shell so more of the page is ready before the request lands. It builds on 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙, screenshotting each change and rolling back anything that didn't help.

Next.js
@nextjs.org

Each fix on an Instant Insight comes with a prompt your agent can run end to end. It walks the agent through the whole flow: read the docs page for the patterns and trade-offs, apply the fix, then verify it in the browser with 𝚗𝚎𝚡𝚝-𝚍𝚎𝚟-𝚕𝚘𝚘𝚙.

0 reposts4 likes

Next.js
@nextjs.org

Some agents never see the dev overlay. They don't drive a browser, and read errors from the terminal instead. So the same labeled fixes show up in the console too, during 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 and 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍.