If you build with Claude Code, Cursor, or Codex, the template you start from matters in a new way: the agent reads the repo before it writes a line, and what it finds there decides whether its first change fits your codebase or fights it. More templates now ship agent instruction files - AGENTS.md, CLAUDE.md, Cursor rules, Claude skills, even MCP servers - but a file existing tells you very little. This roundup opens them up. Every template below was checked in November 2026, with line counts and contents taken from the files themselves, and our own templates are included and held to the same standard.
Short version: the most thorough free option is Kiranism's next-shadcn-dashboard-starter (an 800-line AGENTS.md plus eight Claude skills). For a store, Your Next Store and vercel/shop both ship detailed, project-specific guides. Among paid kits, MakerKit goes furthest (AGENTS.md, CLAUDE.md, GEMINI.md, Claude skills and agents, and an MCP server). TheKitBase templates are shorter and skip skills, but tell the agent exactly what's mocked and which file to change to make it real.
First: every new Next.js app already gets an AGENTS.md
Since Next.js 16.2, the framework ships version-matched documentation inside node_modules/next/dist/docs, and both create-next-app and next dev write a managed block into AGENTS.md at the project root telling agents to read those docs before writing code. The block is headed 'This is NOT the Next.js you know', is regenerated by next dev, and can be turned off with the agentRules option in next.config. Claude Code, Cursor, Codex, and Copilot all read AGENTS.md; many templates add a one-line CLAUDE.md that imports it.
That changes the question. Any template on Next.js 16.2 or later gets that baseline the first time you run it. What a template adds on top - the parts specific to its own code - is what's worth comparing.
What to look for in a template's agent files
- A map of the project: commands to run, where things live, and the conventions an agent should copy rather than reinvent.
- Boundaries: files the agent must not edit (generated code, platform-managed files) and which layer owns what.
- What's mocked: if the AI, payments, or data are demo stubs, the agent needs to know before it builds on them - and ideally which file to replace.
- How to verify a change: the lint, test, or accessibility command the agent should run before it calls a task done.
- Tool-specific extras: Claude skills (.claude/skills) and MCP servers are genuinely useful, but skills only work in Claude Code. AGENTS.md is the one file Claude Code, Cursor, Codex, and Copilot all read.
- One source of truth: a CLAUDE.md that imports AGENTS.md stays in sync; a CLAUDE.md that copies it can drift.
| Template | Price | Agent files | AGENTS.md size | Skills / MCP |
|---|---|---|---|---|
| create-next-app (baseline) | Free | AGENTS.md | Managed block only | No |
| next-shadcn-dashboard-starter | Free (MIT) | AGENTS.md, CLAUDE.md, .claude | ~800 lines | 8 Claude skills |
| Your Next Store | Free (MIT) | AGENTS.md, CLAUDE.md, .claude | ~440 lines | Claude skills |
| vercel/shop | Free (MIT) | AGENTS.md, .claude | ~160 lines | Claude skills |
| Next.js Boilerplate (ixartz) | Free (MIT) | AGENTS.md, CLAUDE.md | ~70 lines | No |
| MakerKit | $349 one-time (list) | AGENTS.md, CLAUDE.md, GEMINI.md, .claude, .mcp.json | Not public | 5 skills, agents, MCP |
| supastarter | $349 one-time (list) | AGENTS.md, .cursor rules, skills | Not public | Agent skills |
| DirStarter | Paid | MCP server; AI skills on Pro | Not public | Skills (Pro), MCP |
| TheKitBase | From $19 one-time | AGENTS.md, CLAUDE.md, .cursorrules | ~70 lines | No |
Free templates
next-shadcn-dashboard-starter - github.com/Kiranism/next-shadcn-dashboard-starter
The most thorough agent setup we found in a free template. AGENTS.md runs to about 800 lines - project overview, stack details, structure, commands, and patterns - with a CLAUDE.md alongside it and eight Claude skills in .claude/skills covering shadcn, TanStack Query and Form, Next.js best practices, and the project's own conventions. It's a working admin dashboard (MIT, Next.js 16); auth, organizations, and billing run on Clerk.
Your Next Store - github.com/yournextstore/yournextstore
An e-commerce template built with agents in mind. Its 440-line AGENTS.md covers commands, key files, a 'platform-managed files - do not modify' list, project patterns, the prerendered shell, a performance and accessibility baseline, and its commerce SDK, with CLAUDE.md importing it and Claude skills in .claude. MIT and on Next.js 16; it needs an API key from the YNS commerce service to run.
vercel/shop - github.com/vercel/shop
Vercel's Shopify storefront has the clearest architecture guidance of the group: AGENTS.md is organised around three owners - Shopify for commerce, Next.js for the app, eve for the shopping agent - with boundary rules for each layer, release and testing policy, and the Next.js managed block. It also ships Claude skills. MIT, Next.js 16, and new, so expect it to change.
Next.js Boilerplate by ixartz - github.com/ixartz/Next-js-Boilerplate
A compact example of doing it well: about 70 lines of principles, commands, commit conventions, environment, styling, React, i18n, and testing rules - including a short section on token efficiency - with CLAUDE.md importing AGENTS.md. No skills, but nothing wasted either. MIT, Next.js 16.
Paid kits
MakerKit
MakerKit's Next.js kits (Supabase, Drizzle, or Prisma) ship the widest agent setup we found. Its Drizzle kit docs list AGENTS.md for project rules, a CLAUDE.md entry point, GEMINI.md for Gemini, a .claude folder with agents, commands, and skills (drizzle-expert, frontend-design, playwright-e2e-expert, react-form-builder, server-actions-expert), and an MCP server wired through .mcp.json; the exact skills vary by kit. MakerKit notes the skills are Claude Code only; other agents use AGENTS.md and the MCP server. $349 one-time list price for Pro.
supastarter
supastarter says every starter kit - Next.js, Nuxt, and TanStack Start - ships a maintained AGENTS.md plus Agent Skills, with Cursor rules alongside. It's a SaaS starter kit from $349 one-time list for Solo. We couldn't inspect the files themselves since the repo is private, so this is from supastarter's own documentation.
Get the free template, plus new drops
DocsKit Free lands in your inbox right away. New templates after that.
DirStarter
A Next.js 16 directory template with a different angle on agents: an MCP server so Claude Code or Cursor can add, describe, and schedule directory listings from a URL, and AI skills for Claude, Cursor, and Codex on the Pro plan. Useful if the agent is going to run the directory, not just build it. Paid; pricing was on sale when we checked, so see the site for current numbers.
TheKitBase (ours)
All 14 of our paid templates ship AGENTS.md, CLAUDE.md, and .cursorrules - about 70 lines each covering commands, where things live, the design system, conventions, how to add a page, and accessibility. The part we'd point to is the 'Payments and AI' section: it tells the agent plainly what's real and what's a demo, and where to change it. Keel's, for example, says the assistant runs on a mock engine in src/lib/ai.ts that makes no model calls, that billing has no payment provider attached, and that startCheckout() in src/lib/billing.ts is where to connect one. Each one also gives the agent the accessibility test to run after UI changes (npm run test:a11y).
Where we fall short of the best on this list: no Claude skills, no MCP server, CLAUDE.md is a copy of AGENTS.md rather than an import, and .cursorrules is Cursor's older format (Cursor also reads AGENTS.md). The Next.js managed block isn't committed, but next dev adds it on first run. Our /ai-ready page lists every template's agent files next to its actual AI status - which run a real model, which run a rule-based or canned demo, and which have no AI features at all.
See every TheKitBase template's agent files and its real AI status - real model, demo, or none.
View AI-ready templatesThings to watch for
- Library repos versus templates: Fumadocs and shadcn/ui have AGENTS.md files too, but they're for contributors to the library, not for the app you build with it.
- Copied files: TailAdmin's free Next.js dashboard ships an AGENTS.md titled 'TailAdmin Pro', so check that an agent file describes the code you actually have.
- Rules that are only lint rules: vercel/chatbot's .cursor/rules contains Ultracite's formatting and linting rules - useful, but not a guide to the project.
- Skills are tool-specific: .claude/skills help Claude Code and nothing else. If your team mixes tools, AGENTS.md is what they all share.
Which should you pick?
If you want the richest agent context for free, start with Kiranism's dashboard starter or, for commerce, Your Next Store or vercel/shop. If you're paying for a full SaaS kit and use several agents, MakerKit's setup (with MCP) is the most complete we found. If what you want is a finished, designed product where the agent knows exactly which parts are demo stubs and how to make them real, that's what our templates are built around.
TheKitBase templates ship AGENTS.md, CLAUDE.md, and Cursor rules that say what's real, what's mocked, and where to wire it - from $19 one-time.
Browse Templates