Build a Next.js feature with a coding agent
A guard-railed way to build a Next.js feature with a coding agent: set the rules, give it live framework context, check boundaries, and verify in a real browser.
Before you start
- A Next.js App Router project you can run locally.
- A coding agent that can read project instruction files and use MCP servers.
Steps
Write the agent guide
Add an AGENTS.md (or equivalent project instructions) with commands, server/client rules and what the agent must not do.
Check before moving on
- The commands in the file actually run on your machine.
Give the agent framework context
Connect a Next.js-aware MCP server so the agent can consult current framework docs and your running app instead of relying on memory.
Uses: Next.js DevTools MCPCheck before moving on
- The agent can answer a question about your Next.js version correctly.
Implement in small steps
Ask for one component or route at a time and review each diff before the next.
Check before moving on
- Each diff is focused on the request.
Review the server/client boundary
Run the boundary review prompt on every new or moved component.
Check before moving on
- No server-only import reaches a client component.
Verify in a browser
Exercise the feature in a real browser session and check the console for errors.
Check before moving on
- The main flow works and the console is clean.
Expected outcome
A working feature with reviewed boundaries and browser-level verification.
Related resources
A starting AGENTS.md that tells coding agents how to build, test and change a Next.js App Router codebase safely: commands, boundaries and what never to do without asking.
CuratedKitLocalUpdated 2 days ago
agents-mdnextjsreactinstructions
About this catalog
Bundled snapshot · published Nov 15, 2026, 6:05 AM · Catalog revision 5bc079fe355af2214bc0
Showing the snapshot bundled with this app (no content source is configured). Newer content may exist at the source.