COPILOT TO AGENTS.MD

Paste your .github/copilot-instructions.md and get an AGENTS.md for every agent, plus a short Copilot file that still works on Copilot surfaces that cannot read AGENTS.md. Nothing leaves your browser.

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

16 lines, 0.5 KiB, about 132 tokens (estimate)

Lint report
WARN Usable, but it could be sharper 0 errors, 1 warnings, 0 notes
  1. WARNVague rule an agent cannot check

    "Follow best practices"

    Name the practice: "parameterized queries only", "no default exports".

Converted to every formatRead as: .github/copilot-instructions.md
  • Kept 1 persona line ("You are a helpful assistant for the Acme dashboard. Act as a...") 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.

- npm ci
- npm run build
- npm run test:unit

## Code style

- Use <script setup> in single file components.
- Use 2-space indentation.
- Follow best practices for performance.
- Always use the composition API.

## Working rules

- Do not use the Options API.
- Do not add new UI libraries.
- Never put API keys in the frontend.

## Project-specific notes

- You are a helpful assistant for the Acme dashboard. Act as a world-class Vue developer.
- We use Vue 3 with the Composition API, Vite and Pinia. Tests use Vitest.
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

- npm ci
- npm run build
- npm run test:unit

## Working rules

- Do not use the Options API.
- Do not add new UI libraries.
- Never put API keys in the frontend.
.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 copilot-instructions.md to AGENTS.md?

copilot-instructions.md is read by Copilot only. AGENTS.md is read by Copilot's cloud agent, code review, CLI and VS Code chat, and also by Codex, Cursor, Windsurf, Zed, Cline and Jules. Last verified 2026-11-13 against the vendor documentation. Moving the content lets every agent share it.

Why Keep a Short Copilot File Afterwards?

Copilot Chat on GitHub.com, in Visual Studio and in JetBrains reads copilot-instructions.md but not AGENTS.md. A pointer-only file would leave those surfaces with nothing, so the converter writes a short version that keeps the stack, the commands and the working rules inline.

# Copilot instructions

Project: shop-api. Order and checkout API for the storefront.

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.

## Stack

- Language: TypeScript
- Framework: Fastify
- Database: PostgreSQL
- Tests: Vitest
- Package manager: pnpm

## Commands

- Install dependencies: `pnpm install`
- Run locally: `pnpm dev`
- Run all tests: `pnpm test`
- Lint: `pnpm lint`
- Type-check: `pnpm tsc --noEmit`

## Working rules

- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.

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-specific applyTo frontmatter, if present, is stripped; keep those rules in .github/instructions files.

What Can the Converter Not Do?

  • It does not invent commands that the original file did not list.
  • It does not split rules into path-specific .instructions.md files.
  • It does not resolve contradictions; the linter reports them so you can choose.

How Do You Check the Output?

  1. Read the AGENTS.md tab and add anything missing.
  2. Replace .github/copilot-instructions.md with the short version from the Copilot tab.
  3. Run the AGENTS.md through the linter.
  4. Download the zip and commit the files at the paths shown.

Background: AGENTS.md vs copilot-instructions.md and the copilot-instructions.md format. Starting fresh instead? Use the generator.

Frequently Asked Questions

Should I delete copilot-instructions.md?

No. Several Copilot chat surfaces read only that file. Replace it with the short version the converter produces, which keeps the essentials inline and points to AGENTS.md for the rest.

What about .github/instructions files?

Leave them in place. Path-specific instructions with an applyTo glob are a Copilot feature with no AGENTS.md equivalent, though nested AGENTS.md files can cover folder-specific rules for other agents.

Does the converter keep my headings?

It maps them to standard AGENTS.md sections where it can tell what they are about, such as commands, style or rules. A heading it cannot classify keeps its original name as its own section, and unheaded lines it cannot classify go under Project-specific notes in the original order.

Is my file sent anywhere?

No. The converter is client-side JavaScript. Nothing you paste is uploaded, stored or logged, and the page works offline once loaded.

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?