AI Agent Rules Generator

Generate CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, and .github/copilot-instructions.md from one form. Multi-agent. Strictness swaps.

Platform

Choose your project's runtime target. Switching platforms resets the dependent fields below.

Target agents

Choose every agent your team uses. CLAUDE.md becomes a thin @AGENTS.md import when both Claude Code and Codex are selected.

Claude Code OpenAI Codex Cursor GitHub Copilot

Skills

Choose reusable agent skills to include as separate output tabs and reference from the generated rules.

Andrej Karpathy Coding Superpower Core GSD Core Matt Pocock Core

Project type

Language

Styling

Unit test runner

End-to-end runner

Deploy target

Strictness

Replaces the coding-standards / forbidden / response-format / scope sections wholesale. Higher levels do not stack on top of lower levels.

Conservative Balanced Aggressive

          # CLAUDE.md

Project guidance for Claude Code. Read this first; it overrides any general defaults.

## Project Overview

This is a Vite + React project written in TypeScript, styled with Tailwind CSS utilities.

## Tech Stack

- Framework: Vite + React
- Language: TypeScript
- Styling: Tailwind CSS utilities

## Commands

- Start dev server: `pnpm dev`
- Production build: `pnpm build`

## Project Structure

- `src/` — application source (one default export per module).
- Tests live next to the code in `*.test.ts` files (or `__tests__/` if the project already uses that pattern).
- Build output lands in `dist/` (or framework default).

## Coding Standards

- Use TypeScript strict mode (`strict: true` in tsconfig.json) when editing TS files.
- Cap function length at 40 lines; extract named helpers above that.
- One default export per module; named exports for utilities.
- Prefer `const` over `let`; reject `var`.
- Run the test command before declaring a task complete.

## Workflow Rules

- Use plan mode for changes spanning more than 5 files or touching architectural boundaries.
- List the files you intend to touch before editing.
- Run the unit-test command after every code edit and paste the exit status.

## Forbidden

- Do not add new dependencies without approval.
- Do not refactor unrelated files alongside the requested change.
- Do not change public component or function signatures without listing them in your summary.

## Skills

- Andrej Karpathy Coding: read `.claude/skills/andrej-karpathy-coding.md` before each task.


## Response Format

- List the files you plan to touch before editing.
- Show changes file-by-file with a 1-sentence rationale per file.
- Run the verification command and paste its exit status in the final reply.

Related prompts

Related skills