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。