Make your AI coding agent follow your stack.
Pick your stack and get ready-to-commit AGENTS.md, CLAUDE.md, Cursor .mdc rules and Copilot instructions, with commands, conventions and the mistakes agents usually make on that stack.
Rules file generator
Loading generator…
Tip: using several tools? Keep AGENTS.md as the source of truth. CLAUDE.md then imports it with @AGENTS.md, and Gemini gets a settings file instead of a copy.
Popular stacks
Next.js (App Router) + Tailwind CSS v4 + shadcn/ui + Supabase + Zod validation
The default vibe-coding SaaS stack: Next.js App Router, Supabase for auth and Postgres, Tailwind and shadcn/ui for the interface.
Next.js (App Router) + Tailwind CSS v4
A plain Next.js + TypeScript + Tailwind v4 starter, the most common front-end setup in 2026.
Next.js (App Router) + Tailwind CSS v4 + Prisma + Stripe payments + Zod validation
A paid SaaS on Next.js with Prisma and Stripe subscriptions.
Next.js (App Router) + Tailwind CSS v4 + Drizzle ORM + Clerk auth + Zod validation
Next.js with Clerk for auth and Drizzle ORM on Postgres: fast to build, type-safe end to end.
Next.js (App Router) + Tailwind CSS v4 + shadcn/ui + Vercel AI SDK + Zod validation
Build an AI chat app or agent UI with Next.js and the Vercel AI SDK.
Next.js (App Router) + Tailwind CSS v4 + Supabase + Stripe payments + Zod validation + Vitest
The full indie-hacker SaaS kit: auth, database, payments and tests.
Next.js (App Router) + Tailwind CSS v4 + Firebase
Next.js with Firebase Auth and Firestore.
Next.js (App Router) + Tailwind CSS v4 + Vitest + Playwright E2E
A Next.js app with a proper test setup: Vitest for units, Playwright for end-to-end.
React + Vite + Tailwind CSS v4 + TanStack Query + Vitest + Zod validation
A classic single-page app: React + Vite with TanStack Query for server data.
React + Vite + Tailwind CSS v4 + Supabase + Zustand
A client-only React app talking straight to Supabase, popular for quick prototypes and internal tools.
React + Vite + Tailwind CSS v4 + Firebase + Vitest
A React SPA on Firebase Auth and Firestore.
Astro + Tailwind CSS v4
Content sites, blogs and landing pages with Astro and Tailwind.
Which rules file does each tool read?
| File | Read by | Guide |
|---|---|---|
AGENTS.md | Codex, Cursor, GitHub Copilot, Jules, Zed, Warp, opencode, Aider (via config) and 20+ more | AGENTS.md guide |
CLAUDE.md | Claude Code | CLAUDE.md guide |
.cursor/rules/*.mdc | Cursor | Cursor rules (.mdc) guide |
.cursorrules | Cursor (legacy single file) | .cursorrules (legacy) guide |
.github/copilot-instructions.md | GitHub Copilot (Chat, coding agent, code review, CLI) | Copilot instructions guide |
.windsurf/rules/*.md | Windsurf / Devin Desktop | Windsurf rules guide |
GEMINI.md | Gemini CLI | GEMINI.md guide |
FAQ
What is an AI rules file?
A Markdown file in your repo (AGENTS.md, CLAUDE.md, .cursor/rules/*.mdc, .github/copilot-instructions.md) that AI coding agents load automatically. It tells them your stack, the commands to run and the conventions to follow, so they stop guessing.
Which file should I use?
Use AGENTS.md as the shared file: Codex, Cursor and GitHub Copilot read it directly, Claude Code reads it via a one-line CLAUDE.md import, and Gemini CLI via a setting. Add Cursor .mdc rules or Copilot .instructions.md files when you want rules scoped to certain files.
Is the generator free?
Yes. It runs entirely in your browser; nothing you type is sent to a server.
How are the rules written?
Each stack and library has a hand-written rule module based on official docs and the mistakes AI agents commonly make on that stack. Modules are reviewed regularly and dated.