CURSORRULES TO AGENTS.MD

Paste a .cursorrules file and get a structured AGENTS.md with matching wrappers for Claude Code, Gemini CLI, Copilot and current Cursor rules. Nothing is uploaded; the conversion runs in this page.

Zero retention: everything you type stays in this browser. Verify it yourself in DevTools.

24 lines, 0.6 KiB, about 161 tokens (estimate)

Lint report
FAIL Needs fixes before you commit it 2 errors, 3 warnings, 1 notes
  1. ERRORwhole fileNo build, test or lint commands

    No section or line gives the commands to install, build, test or lint.

    Add a Commands section with the exact commands. It is the highest-value part of the file: it is how an agent checks its own work.

  2. ERRORRules contradict each other

    Tabs vs spaces: line 15 and line 17 disagree.

    Keep one rule and delete the other. An agent given both picks one at random.

  3. WARNwhole fileNo headings

    24 lines with no Markdown headings.

    Group the lines under headings such as Commands, Code style and Working rules. Agents and humans both find rules faster.

  4. WARNVague rule an agent cannot check

    "Write clean code"

    Say what clean means here: a formatter command, a max function length, a naming rule.

  5. WARNVague rule an agent cannot check

    "Be careful"

    Name the risk and the rule: "ask before running migrations".

  6. INFOPersona line

    You are a senior full-stack engineer and an expert in TypeScript, React and Node.

    Persona lines cost tokens on every task and rarely change what an agent does. Replace with a concrete rule.

Converted to every formatRead as: .cursorrules (legacy Cursor)
  • Kept 1 persona line ("You are a senior full-stack engineer and an expert in TypeSc...") where it was. They cost tokens and rarely change behavior; consider replacing them with concrete rules.
AGENTS.mdFor Codex, Cursor, Copilot, Jules, Windsurf and more
# AGENTS.md

This file is the single source of truth for every coding agent working in this repository. The tool-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md and .cursor/rules/project.mdc) point here. Edit this file, not those.

## Commands

Run these from the repository root.

- `pnpm install`
- `pnpm dev`
- `pnpm test`

## Code style

- Always use TypeScript.
- Use 2 spaces for indentation.
- Use single quotes.
- Use tabs in Makefiles only.
- Named exports only, no default exports.

## Working rules

- Write clean code and follow best practices.
- Use pnpm, never npm.
- Prefer functional components and hooks.
- Never commit .env files.
- Always write tests for new features.
- Do not edit files in src/generated.

## Project-specific notes

- You are a senior full-stack engineer and an expert in TypeScript, React and Node.
- General
- Commands
- Style
- Rules
- Be careful with database migrations.
- Structure
- src/app: routes
- src/components: shared UI
- src/lib: server utilities
CLAUDE.mdFor Claude Code
# CLAUDE.md

@AGENTS.md

## Claude Code

- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file, so every agent stays in sync.
- Put Claude-only preferences below this line. Personal, uncommitted notes belong in CLAUDE.local.md.
GEMINI.mdFor Gemini CLI
# GEMINI.md

@./AGENTS.md

## Gemini CLI

- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file.
- Alternative: delete this file and set "context": { "fileName": ["AGENTS.md"] } in .gemini/settings.json so Gemini CLI reads AGENTS.md directly.
.github/copilot-instructions.mdFor GitHub Copilot
# Copilot instructions

The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.

## Commands

- `pnpm install`
- `pnpm dev`
- `pnpm test`

## Working rules

- Write clean code and follow best practices.
- Use pnpm, never npm.
- Prefer functional components and hooks.
- Never commit .env files.
- Always write tests for new features.
- Do not edit files in src/generated.
.cursor/rules/project.mdcFor Cursor
---
description: Project instructions for every task (mirrors AGENTS.md)
globs:
alwaysApply: true
---

# Project rules

The project instructions live in @AGENTS.md at the repository root, which Cursor loads automatically. They are not repeated here, so they cost context only once. Edit AGENTS.md, not this rule.

Before you change code, check the Commands and Working rules sections of AGENTS.md, and run its test and lint commands before you say a task is done.

Put Cursor-only rules below, or add scoped rules as more .mdc files with `globs` (for example `src/components/**/*.tsx`).
Guide

Why Convert .cursorrules to AGENTS.md?

Cursor marks .cursorrules as legacy, and no other major agent treats it as its main file. AGENTS.md is read by Cursor itself plus Codex, Windsurf, Zed, Cline, Jules and several Copilot surfaces, so moving your rules there lets every agent on the team follow the same instructions. Last verified 2026-11-13 against the vendor documentation. See the compatibility table.

What Does the Converter Map Where?

  • Markdown headings become AGENTS.md sections. Headings about commands, setup, build or testing map to Commands; style and conventions to Code style; rules, do and do not lists to Working rules; structure and architecture to Project layout.
  • Lines that look like shell commands, and shell code blocks, are collected under Commands. Other code blocks and tables are carried over unchanged.
  • Lines that start with always, never, do not or must are treated as rules.
  • Persona lines such as "You are an expert engineer" are kept under Project-specific notes and called out in the conversion notes, so you can decide whether to replace them with concrete rules. Nothing is silently dropped.
  • Frontmatter (Cursor description, globs and alwaysApply, Copilot applyTo, Windsurf trigger) is removed, and the conversion notes say what was removed.
  • A heading the converter cannot classify keeps its original name as its own section. Unheaded lines it cannot classify go under Project-specific notes, in the original order.

The result is AGENTS.md in the same shape the generator produces, plus thin CLAUDE.md, GEMINI.md, copilot-instructions.md and project.mdc files built from it.

What Can the Converter Not Do?

  • It does not invent commands. If your .cursorrules never said how to run the tests, the Commands section says so and asks you to add them.
  • It does not judge whether a rule is right for your project; it only moves and groups.
  • It does not resolve contradictions for you. It keeps both lines and the linter flags them.
  • It does not split rules into glob-scoped .mdc files; do that by hand where it helps.

How Do You Check the Output?

  1. Read the AGENTS.md tab top to bottom.
  2. Add missing commands and delete rules nobody can explain.
  3. Open the linter and paste the result: it flags vague rules, contradictions, missing commands and pasted secrets.
  4. Download the zip and commit the files at the paths shown.
  5. Delete the old .cursorrules once the new files are in place.

What Should Happen to the Persona Line?

Lines like "You are a senior full-stack engineer" are kept under Project-specific notes and flagged in the conversion notes and by the linter. They cost tokens on every request and rarely change what the agent does. Replace them with the concrete behavior you wanted, for example a rule about testing or dependencies.

Read more: .cursorrules vs .cursor/rules and the AGENTS.md format.

Frequently Asked Questions

Is my .cursorrules file uploaded?

No. The converter runs entirely in your browser. The text you paste is never sent to a server, and you can confirm this in your browser developer tools by watching the Network tab while you convert.

Will Cursor still work after I delete .cursorrules?

Yes. Cursor reads AGENTS.md, and the converter also produces a .cursor/rules/project.mdc file that always applies and points to AGENTS.md.

Why is my Commands section empty?

Your file did not contain anything that looked like a command. The converter never guesses commands, because a wrong test command is worse than none. Add the real install, build, test and lint commands yourself.

Does it handle .mdc files too?

Yes. Paste a .cursor/rules .mdc file and the frontmatter is stripped before the body is converted. A glob-scoped rule may be better kept as its own .mdc file, though.

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word for it. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing you type is sent. The check takes under a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your input.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Paste a real instruction file into the editor and read the report and the conversion.
  5. Look at the Network tab again. It is still empty. Downloads are built in the page as Blob URLs, so even the zip never touches a server. For extra proof, turn on offline mode after the page loads: everything keeps working.

Only the feedback form can add a line to that log, and it sends only the vote and comment you type into it. 2prompt has no server code at all: no API, no model and no database of your files. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the fonts and the anonymous analytics endpoint.

Was this helpful?