Convert .cursorrules to CLAUDE.md

Trying Claude Code (or adding it alongside Cursor) and don't want to rewrite the rules you've refined in .cursorrules? Our free generator does the migration properly: your existing rules are carried over verbatim into a Project rules section, and around them we generate what a .cursorrules file usually lacks — your repo's exact commands (install, build, lint, single-test invocation), stack conventions, and known gotchas, detected from your package.json / pyproject.toml / Cargo.toml / go.mod.

How to convert

1. Open the generator and paste your manifest (e.g. package.json).
2. Click Open file (or drag & drop) and add your .cursorrules — Cursor's newer .mdc rule files work too; MDC frontmatter is stripped automatically.
3. Copy or download the resulting CLAUDE.md and AGENTS.md and commit them.

Or in the terminal, from your repo root — it picks up .cursorrules automatically:

npx getagentready

Why not just rename the file?

• .cursorrules files are usually style rules only. Agents fail most often on commands — the generated CLAUDE.md includes the exact ones for your toolchain, including how to run a single test.
• You get AGENTS.md as well — the open format read by many coding agents — so the same rules cover your whole toolchain, Cursor included.
• Everything runs client-side in your browser. Your rules and manifests are never uploaded.

Keep both tools happy

Nothing forces a choice: keep .cursorrules for Cursor, commit CLAUDE.md + AGENTS.md for everything else, and treat one of them as the source of truth when you update rules. See our CLAUDE.md guide for what belongs in the file long-term.