CLAUDE.MD TO AGENTS.MD

Paste your CLAUDE.md and get an AGENTS.md that every agent can read, plus a thin CLAUDE.md that imports it so Claude Code keeps working exactly as before. The conversion runs in your browser.

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

19 lines, 0.6 KiB, about 141 tokens (estimate)

Lint report
WARN Usable, but it could be sharper 0 errors, 2 warnings, 0 notes
  1. WARNwhole fileCommands, but no test command

    Commands are listed, but none of them runs the tests.

    Add the exact test command, and the command to run a single test file.

  2. WARNVague rule an agent cannot check

    "Make sure the code is good"

    Replace with a check the agent can run: a test, a lint rule, a command.

Converted to every formatRead as: CLAUDE.md
  • Removed 1 @import line (docs/billing-glossary.md). Imports are not inlined: paste the imported files too, or keep them and reference them from AGENTS.md in words.
AGENTS.mdFor Codex, Cursor, Copilot, Jules, Windsurf and more
# AGENTS.md

This is the billing service. You are an expert Python developer.

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.

- Install: uv sync
- Run: uv run uvicorn app.main:app --reload
- Test: uv run pytest
- Lint: uv run ruff check .

## Code style

- Type hints on every function.
- Use 4 spaces.
- Keep functions small and readable.

## Working rules

- Never edit an applied Alembic migration.
- Ask before adding dependencies.
- Make sure the code is good before finishing.
- IMPORTANT: run the tests before saying you are done.

## Notes

- Money is stored as integer cents.
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

This is the billing service. You are an expert Python developer.

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

- Install: uv sync
- Run: uv run uvicorn app.main:app --reload
- Test: uv run pytest
- Lint: uv run ruff check .

## Working rules

- Never edit an applied Alembic migration.
- Ask before adding dependencies.
- Make sure the code is good before finishing.
- IMPORTANT: run the tests before saying you are done.
.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 Move CLAUDE.md Content Into AGENTS.md?

CLAUDE.md is read mainly by Claude Code, while AGENTS.md is read by Codex, Cursor, Windsurf, Zed, Cline, Jules and several Copilot surfaces. If anyone on the team uses another agent, keeping rules only in CLAUDE.md leaves them without instructions. Last verified 2026-11-13 against the vendor documentation.

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.
  • @path import lines are removed from the output and listed in the conversion notes, because AGENTS.md has no import syntax; inline the imported text or link to it.

How Does Claude Code Keep Working?

The converter outputs a new CLAUDE.md containing @AGENTS.md. Claude Code resolves the import and sees the same instructions as before. This matters because, by default, Claude Code reads AGENTS.md directly only when no CLAUDE.md or CLAUDE.local.md exists.

# 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.

What Can the Converter Not Do?

  • It does not follow @imports; the imported file's text is not pulled in.
  • It does not invent missing commands.
  • It does not decide which lines are Claude-only; move those back into CLAUDE.md by hand.

How Do You Check the Output?

  1. Compare the AGENTS.md tab with your original file.
  2. Move any Claude-specific notes into the CLAUDE.md wrapper below the import.
  3. Paste AGENTS.md into the linter and fix vague rules it flags.
  4. Download the zip, commit, and start a new Claude Code session to confirm it loads.

Background: CLAUDE.md vs AGENTS.md and the CLAUDE.md format.

Frequently Asked Questions

Will Claude Code see my instructions twice?

Not with the generated files. The new CLAUDE.md imports AGENTS.md once. It only loads twice if you also switch the Claude Code Project instructions setting to load both CLAUDE.md and AGENTS.md.

What happens to CLAUDE.local.md?

Nothing. Keep it as it is for personal notes; it loads after CLAUDE.md and stays out of version control. Do not paste it into the converter unless you want its content shared.

Are @imports converted?

They are removed from the output and listed in the conversion notes, because AGENTS.md has no import syntax and other agents would not follow them. Inline the imported text into AGENTS.md or link to the file instead.

Is the conversion done on a server?

No. Parsing and generation happen in JavaScript on this page. Nothing you paste is uploaded or stored.

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?