⚡ Perfect for Vibe Coding — Skip weeks of setup. Browse 100+ production-ready boilerplates.
Browse boilerplates →AGENTS.md Generator
Pick your project type and get a complete agent instruction file: the commands your agent may run, the conventions it must follow, and the files it must leave alone. Everything is generated in your browser, nothing is uploaded.
Rules to include
# AGENTS.md This project is a Next.js app project. Read this file before making changes. ## Project - Stack: Next.js (App Router), TypeScript, Tailwind - Package manager: pnpm - Tests: Vitest ## Commands These are the commands you may run. Do not invent others. | Task | Command | | --- | --- | | Install | `pnpm install` | | Dev server | `pnpm dev` | | Build | `pnpm build` | | Test | `pnpm test` | | Lint | `pnpm lint` | | Typecheck | `pnpm typecheck` | ## Code style - TypeScript strict mode, no `any` without a comment explaining why. - Server Components by default. Add `use client` only when a component needs state, effects or browser APIs. - Colocate components with the route that uses them until a second route needs them. - Use strict typing throughout. Do not silence the type checker to make something compile. - Keep files focused. If a file does two unrelated things, split it. - Add or update tests for any change to auth, billing or data handling. - Never hardcode secrets, keys or credentials. Read them from the environment. - Ask before adding a dependency. Prefer the standard library or an existing utility. - Follow the naming conventions already present in neighbouring files. - Do not refactor unrelated code while fixing a bug. Keep diffs reviewable. ## Boundaries Do not change these without a human deciding first. - Do not edit files in `.next/`, `node_modules/` or any generated types. - Do not modify database migrations that are already applied. - Do not add a dependency without saying why in the PR description. ## Testing - Tests run with Vitest. Run them before saying a change is done. - A failing test is a blocker, not a warning. Fix the cause, do not skip the test. - New behaviour needs a test that would fail without the change. ## Git workflow - Commit messages follow Conventional Commits: `feat:`, `fix:`, `chore:`, `docs:`. - One logical change per commit. Do not bundle a refactor with a fix. - Do not commit directly to the default branch unless told to.
BoilerplateHub ⚡ Perfect for Vibe CodingYou have the idea. Now get the code.
Ready to build? Skip months of setup with a production-ready boilerplate that has auth, billing, and email already wired up.
Prefer to start from a full example?
The template library has complete AGENTS.md files for twelve project types, each with a breakdown of what every section is for.
Browse AGENTS.md templates →Working mainly in Cursor?
The .cursorrules generator is the quicker path when you want a Cursor rules file from a list of toggles rather than a project-type preset.
Open the .cursorrules generator →Frequently asked questions
What is an AGENTS.md file?
It is a plain markdown file in your repository root that tells an AI coding agent how the project works: which commands it may run, the conventions it must follow, and which files it must not touch. Agents read it before they start, so it prevents the same corrections being typed into every session.
Is AGENTS.md the same as CLAUDE.md?
The content is the same. The filename differs by tool: Claude Code reads CLAUDE.md, while most other agents and editors read AGENTS.md. Generate one file here and symlink the other so the two never drift apart.
How is this different from the .cursorrules generator?
The cursorrules generator produces a rules file quickly from a list of toggles. This one starts from your project type, so the commands, code style and boundaries arrive pre-filled with what that ecosystem actually uses, and you edit rather than compose from scratch.
Where do I put the generated file?
In the repository root, committed to version control. In a monorepo you can also add package-level files for rules that only apply inside one package, since agents read the nearest file as well as the root one.