All user-facing UI changes must be mobile-responsive. Before completing a UI change, verify it at a narrow mobile viewport and a desktop viewport. Check for page-level horizontal overflow, clipped content, unreadably narrow columns, overlapping controls, and whether dense navigation should wrap or scroll horizontally.
- Read
node_modules/@vercel/geistdocs/docs/agents.mdand the focused pages undernode_modules/@vercel/geistdocs/docs/pages/before changing package-backed behavior. - Keep
createGeistdocsfrom@vercel/geistdocs/nextas thenext.config.tswrapper. It composes Fumadocs MDX and generates the app-route manifest used bycreateProxy; do not replace it withcreateMDXdirectly. - Keep
cacheComponents: trueandpartialPrefetching: trueinnext.config.ts. - Restart
next devafter adding, deleting, or renaming an App Router page or route socreateGeistdocsregenerates its route manifest. - Do not export
dynamic,dynamicParams,revalidate, orfetchCachefrom App Router pages or route handlers. - Generate every supported root language. Read
[lang]throughnext/root-paramsonly in Server Components; retain route contextparamsin Route Handlers and Server Actions. - Set
prefetch={true}on app-owned links to statically generated docs, integrations, and templates so navigation reveals the complete destination immediately. - Keep package adapters thin. Do not deep-import package internals or edit generated
.source,.next, ornode_modulesfiles.
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices.
This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.