A free CLAUDE.md generator for Claude Code
CLAUDE.md is the file Claude Code loads at the start of every session. Put it in your project's root and Claude follows your stack, conventions and rules without you repeating them in every prompt. Without one, you keep correcting the same things: old patterns, missing types, extra dependencies, long-winded answers.
Claude Code's /init command can draft a CLAUDE.md by scanning your repository. This generator is the other half: it writes the rules you actually want enforced, such as how to approach bugs, what to never do and how answers should be formatted. Many developers combine both: run /init, then paste in the rules from here.
What to put in a CLAUDE.md file
A good CLAUDE.md is short and specific. The generated file follows a simple template: the role the assistant should take, your tech stack, coding conventions for that stack, a step-by-step workflow, hard rules, and the response format you expect.
Keep it under a page or two. Anything long or rarely needed belongs in a separate document the file links to; Claude Code can import other files with the @path syntax.
AGENTS.md vs CLAUDE.md, which do you need?
AGENTS.md is an open, plain-Markdown format that many coding agents read, including OpenAI Codex, Cursor and GitHub Copilot. CLAUDE.md is Claude Code's own file and supports Claude-specific features such as imports and nested files.
If your team uses several AI tools, keep your rules in AGENTS.md and add a CLAUDE.md that contains just the line @AGENTS.md, so Claude Code reads the same instructions. If you only use Claude Code, a CLAUDE.md on its own is enough.
Cursor rules for Next.js, React and TypeScript
Cursor's current format is one or more .mdc files in the .cursor/rules/ folder. Each file starts with a short header (description, globs and alwaysApply); the generator adds it for you, set to apply to every request. Choose Next.js, React, TypeScript, Tailwind CSS, Supabase or other chips and the matching conventions are added automatically, for example Server Components by default in the App Router, or Row Level Security for Supabase.
The single .cursorrules file in the project root is Cursor's older format. Cursor now recommends project rules instead, but .cursorrules still works in many setups, so it's available too.
GEMINI.md and GitHub Copilot instructions
Gemini CLI reads a GEMINI.md file from your project, and GitHub Copilot reads repository instructions from .github/copilot-instructions.md. Both use plain Markdown, so the same rules work everywhere. Pick the format and the file is named correctly for you.
One-off prompts for Claude, ChatGPT and Gemini
Need a single prompt instead of a project file? The Claude format wraps each part in XML tags like <role>, <task> and <rules>, which Claude follows closely. The Markdown format suits ChatGPT and Gemini, and the JSON option gives you a ready system message for API calls.
The presets read like engineering checklists, not “act as a world-class expert”: find the root cause before fixing a bug, list the files before building a feature, keep behaviour unchanged during a refactor, and give a concrete attack scenario for every security finding.