AI Rules Generator: AGENTS.md, CLAUDE.md & Cursor Rules from One Form

Claude Code, Cursor, GitHub Copilot, Windsurf, Gemini CLI — the more AI coding tools you adopt, the thornier the question becomes: which file do the project rules go in? The AI Rules Generator fills in that answer: one form, and it generates rules files for six major tools at once, entirely in your browser.

The “every tool has its own rules file” problem

Each AI coding tool reads project conventions from its own location:

Tool	File it reads
OpenAI Codex / Google Jules and others	AGENTS.md
Claude Code	CLAUDE.md
Cursor	.cursor/rules/*.mdc
GitHub Copilot	.github/copilot-instructions.md
Windsurf	.windsurfrules
Gemini CLI	GEMINI.md

When team members use different tools, the same rules get copy-pasted across multiple files. A few weeks later comes the classic incident: “CLAUDE.md got updated, but the Cursor rules are still the old version.”

Making AGENTS.md the single source of truth

The practical answer is to derive every tool-specific file from one canonical source.

AGENTS.md is the natural choice for that canonical file: an open standard for describing your project to AI coding agents — a “README for agents” — with adoption spreading across tools like OpenAI Codex and Google Jules.

This tool follows exactly that design. Your form input builds the AGENTS.md first, and the other five files are derived from it. CLAUDE.md, copilot-instructions.md, .windsurfrules and GEMINI.md share the body verbatim; only Cursor’s .mdc gets an MDC frontmatter block (description plus alwaysApply: true) prepended. Because the content always matches across all files, copy-paste drift is structurally impossible.

How to use it

1. Open the AI Rules Generator and fill in the form:
   • Project name & overview — the first context the AI reads
   • Tech stack — comma- or newline-separated (e.g. TypeScript, React, Vite)
   • Commands — dev server, build, test and lint commands
   • Coding conventions / do-nots — one item per line
   • Directory structure & notes — optional (empty sections are omitted from the output automatically)
2. Choose the output language (English / Japanese) and click generate.
3. Six files appear in tabs. Copy them individually, or use the ZIP download — the archive includes the .cursor/rules/ and .github/ directory structure, so extracting it at the repository root puts everything in place.

Generation runs entirely in browser JavaScript; your project details are never sent to a server.

What belongs in a rules file

The content with the biggest impact on agent output quality is the knowledge that’s hard to read out of the code:

• Verification commands — how to run tests, lint and build. This lets the agent verify its own changes
• Project-specific conventions — “function components only”, “all date handling via dayjs” — the house style of the codebase
• Do-nots — “never use any”, “never edit generated files”, “never commit .env” — explicit statements of what you don’t want

Conversely, information the agent can read from the code (file listings, function descriptions) doesn’t need spelling out. Overlong rules bury the instructions that matter, so start with those three categories, kept concise.

Operating tips

• Treat the output as a scaffold — review it as a team and adjust to reality
• Merge, don’t overwrite, existing files — if you already maintain a CLAUDE.md, diff before integrating
• No secrets — rules files get committed. Keep API keys and internal URLs out
• Update through the tool — when rules change, regenerate; the six files stay in sync

Summary

• Each AI coding tool reads a different rules file, so manual maintenance drifts
• Deriving everything from AGENTS.md keeps rules identical across tools
• Write down what code can’t express: verification commands, house conventions, do-nots

If you’re running more than one AI tool, start by generating a complete, consistent set with the AI Rules Generator. For a deeper dive into the file formats and what to write, see our guide to AI coding agent rules files.