Is 2prompt free?
Yes. The generator, the stack library, the converter and the linter are free to use with no account, no limits and nothing to install. The files you generate are yours to commit to any project, commercial or not.
2prompt turns your stack and house rules into ready-to-commit AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules and Copilot instructions, with a free library of tested files for popular stacks and a converter for the ones you already have.
# AGENTS.md
Project: my-app. A web app.
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.
## Stack
- Language: TypeScript
- Framework: React + Vite
- Tests: Vitest
- Package manager: npm
## Commands
Run these from the repository root.
- Install dependencies: `npm install`
- Run locally: `npm run dev`
- Build: `npm run build`
- Run all tests: `npm test`
- Lint: `npm run lint`
- Type-check: `npx tsc --noEmit`
## Code style
- Indentation and line wrapping are whatever the formatter produces; do not hand-format against it.
- TypeScript runs in strict mode. Do not use `any`; use `unknown` and narrow it, or write the real type.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Never swallow an error. Handle it where you can act on it, or rethrow it with context about what failed.
- Commit messages follow Conventional Commits: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, with an imperative summary under 72 characters.
## 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.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Never run destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, `DROP TABLE`, deleting cloud resources) without explicit approval.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
- If the request is ambiguous or conflicts with these rules, ask one specific question instead of guessing.
## Project phase
This project is in active development. Follow the patterns that already exist; consistency beats novelty.
# 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.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.
# Copilot instructions
Project: my-app. A web app.
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: React + Vite
- Tests: Vitest
- Package manager: npm
## Commands
- Install dependencies: `npm install`
- Run locally: `npm run dev`
- Build: `npm run build`
- Run all tests: `npm test`
- Lint: `npm run lint`
- Type-check: `npx 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.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Never run destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, `DROP TABLE`, deleting cloud resources) without explicit approval.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
- If the request is ambiguous or conflicts with these rules, ask one specific question instead of guessing.
---
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`).
The .zip is laid out exactly as the files go into your repository: AGENTS.md and CLAUDE.md at the root, the Copilot file in .github/, the Cursor rule in .cursor/rules/.
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.
F12, or Cmd+Option+I on a Mac, and select the Network tab.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.
The AGENTS.md generator writes the instruction files that coding agents read before they touch your code. You describe your project once: the languages and framework, the database and hosting, the exact commands that install, build, test and lint it, and the rules your team cares about. 2prompt writes AGENTS.md as the single source of truth, plus thin files for the tools that look elsewhere: CLAUDE.md for Claude Code, GEMINI.md for Gemini CLI, .github/copilot-instructions.md for GitHub Copilot and .cursor/rules/project.mdc for Cursor.
All five files appear side by side in tabs and update as you type. You can copy any one of them, or download a zip that is laid out exactly as the files go into your repository. Nothing about this needs a server, an account or a model: the files come from deterministic templates that run in this page, so the same answers always produce the same files.
Coding agents are only as good as what they know about your project. Without instructions, an agent guesses your package manager, invents a test command, reformats files your formatter owns, and declares a task done without running anything. The fix is cheap: a short file at the root of the repository that tells the agent how the project is built, how to check its own work, and which lines it must not cross.
The catch is that every tool grew its own file. Claude Code reads CLAUDE.md, Gemini CLI reads GEMINI.md, Copilot reads a file in .github, Cursor reads .mdc rules, and Windsurf has its own rules folder. AGENTS.md is the shared answer: an open format, now stewarded by the Agentic AI Foundation under the Linux Foundation, that Codex, Cursor, Windsurf, Cline, Zed, Jules and parts of Copilot read directly. Teams that run two or three agents in one repository need one file that all of them follow, and small pointers for the tools that do not read it yet. That is exactly the set 2prompt writes.
AGENTS.md: the canonical file, with Stack, Commands, Project layout, Code style, Working rules, Product constraints, Project-specific notes and Project phase sections. See the AGENTS.md format guide.CLAUDE.md: imports AGENTS.md with Claude Code's @AGENTS.md syntax, so Claude sees the same instructions on every version. See CLAUDE.md.GEMINI.md: imports AGENTS.md with Gemini CLI's @./AGENTS.md syntax, and explains the settings alternative. See GEMINI.md..github/copilot-instructions.md: points to AGENTS.md and repeats the stack, commands and working rules inline, because Copilot Chat on github.com and in several IDEs reads only this file. See Copilot instructions..cursor/rules/project.mdc: a short always-on rule that points to AGENTS.md, which Cursor already loads, without repeating it. See Cursor rules.Windsurf reads AGENTS.md directly, so it needs no extra file. The Windsurf rules guide explains when a separate rule still helps.
The address bar keeps the whole form in the part after the #, so you can bookmark it or send the link to a teammate. Browsers never send that part of a URL to any server.
The best instruction files are short, specific and checkable. Every line is loaded into the agent's context on every task, so a line has to earn its place.
pnpm test and pnpm lint can check its own work; one that does not will guess or skip it.The generator writes every sentence to those standards, and the files it produces pass the linter with no errors or warnings.
The library has 28 hand-reviewed presets, each with real commands, a conventional directory layout and the rules agents most often get wrong on that stack: Server Components and the service-role key on Next.js with Supabase, migrations shipped with every Django model change, strong parameters in Rails, npx expo install for native modules in Expo. Every preset has its own page with the full files in plain text, and a button that loads it into the generator so you can change anything.
Popular presets: Next.js + Supabase, Next.js + Prisma, React Router v7 (Remix), React + Vite SPA, Vue 3 + Vite, Nuxt, SvelteKit, Astro, and the rest on the stacks page.
Most teams already have an instruction file, often a .cursorrules from a year ago or a CLAUDE.md that grew by accretion. Paste it into Convert & Lint and you get two things at once.
Converter pages: .cursorrules to AGENTS.md, CLAUDE.md to AGENTS.md and copilot-instructions.md to AGENTS.md.
The short version, checked against each vendor's documentation on 2026-11-13:
The full table, with each vendor's source link and the details that trip people up, is on the compatibility page. We re-check it against the vendor docs and date every check.
Yes, and you can check it. The generator, the converter, the linter and the zip builder are JavaScript that runs in this page. There is no server-side code at all: no API, no model call, no database of your files. What you type is never uploaded, never stored, and never put anywhere except the address bar of your own browser when you change the generator form.
Two things do make network requests, and neither carries anything you typed: the page loads its fonts from Google Fonts, and it sends one anonymous page-view count when it loads, before you can type anything. If you use the feedback form, it sends the vote and comment you write in it. That is the whole list. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections anywhere else.
2prompt used to be a seven-step wizard that sent your answers to a language model and returned a long "master prompt" to paste into a chat. That job is now done better, for free, by the chat tools themselves, and it needed a server and a paid model to work. We retired it. The new 2prompt keeps the useful part of the old wizard, the questions about your stack, your constraints and your project's phase, and turns those answers into files your agents actually read, without any model in the loop.
Part of the 2suite.io privacy-first ecosystem of free browser tools.
Yes. The generator, the stack library, the converter and the linter are free to use with no account, no limits and nothing to install. The files you generate are yours to commit to any project, commercial or not.
No. Everything runs in your browser. The form, the files and anything you paste into the linter are never uploaded or stored. The generator form is kept only in the address bar after the #, which browsers do not send to servers.
Yes, one anonymous page-view count when a page loads, before you can type anything. If you submit the feedback form, your vote and comment are sent too. No analytics event is attached to the form, the generated files or anything you paste.
No. The files come from deterministic templates, so the same answers always produce the same files and nothing is sent to a model. That is also why the tool is free to run and works offline once the page has loaded.
Commit AGENTS.md as the source of truth, plus the wrapper for each tool your team uses. If nobody uses Gemini CLI, skip GEMINI.md. Keep the wrappers thin so you only ever edit AGENTS.md.
Recent versions can, but by default only when there is no CLAUDE.md or CLAUDE.local.md. The generated CLAUDE.md imports AGENTS.md with the @AGENTS.md line, which works on every version and keeps both files in sync.
As short as it can be while still giving exact commands and checkable rules. Claude Code documentation suggests under 200 lines for CLAUDE.md, and Codex reads at most 32 KiB of project instructions by default.
Yes. They are plain Markdown. Edit AGENTS.md for shared changes and leave the wrappers as pointers, then paste the result into the linter to catch contradictions or vague rules you added.