Next.js 16.3 AI Improvements：结束 Agent 盲改代码
Next.js 16.3 Preview 让 AGENTS.md、Skills、Agent Browser、actionable errors、focused MCP 和 Markdown docs 变成 Agent 可读反馈。
Agent-readable framework loop
风险：仍是 Preview。应先在 branch 演练，UX、data freshness 和 scope 仍需人类判断。
What happened
Next.js 16.3 通过 @preview 发布。Instant Navigations 之后，第二篇文章聚焦 AI Improvements。
Why it matters
重点不是让 Agent 写更多代码，而是让它读取匹配版本的 docs、browser state、React runtime 和 route diagnostics 后再修改。
Community signal
GitHub Discussion 已出现 build performance、static export、partial prefetching、canary 差异和 memory 行为等反馈。
Checklist
Checklist：检查 AGENTS.md block，限制 Skills scope，要求 browser verification，记录 Stream/Cache/Block 理由，并隔离 credentials。
Risks
风险：仍是 Preview。应先在 branch 演练，UX、data freshness 和 scope 仍需人类判断。
Feedback loop map
| Problem | Next.js 16.3 surface | Operational effect |
|---|---|---|
| Version drift | Managed AGENTS.md docs pointer | Agents read docs bundled with the installed framework version. |
| Workflow adoption | First-party Skills | Cache Components and instant navigation work move route by route. |
| Runtime truth | agent-browser React introspection | Agents inspect DOM, console, network, React tree, renders, and Suspense. |
| Fix choice | Actionable errors and Copy as prompt | Stream, Cache, and Block stay explicit product decisions. |
| Fast diagnostics | Focused DevTools MCP tools | Route compilation status can come from the running dev server. |
| Readable docs | .md, llms.txt, llms-full.txt | Agents get structured documentation without scraping UI pages. |
Checklist：检查 AGENTS.md block，限制 Skills scope，要求 browser verification，记录 Stream/Cache/Block 理由，并隔离 credentials。
• Checklist：检查 AGENTS.md block，限制 Skills scope，要求 browser verification，记录 Stream/Cache/Block 理由，并隔离 credentials。