Skip to content

CLAUDE.md / Rules File Generator

Generate CLAUDE.md, .cursorrules, copilot-instructions.md, .windsurfrules and .clinerules files from one form or a stack template.

CLAUDE.md / Rules File Generator

PreviewCLAUDE.md
# Project Rules

## Tech Stack
- Next.js
- React
- TypeScript

## Project Type
Web App

## Naming Conventions
camelCase for variables, PascalCase for components

## Import Style
Absolute paths with aliases (@/)

## Architecture & Patterns
- Functional components only
- Clean architecture

## Testing
Jest + React Testing Library

Preview updated, 23 lines

Updated . Provided as is. Check the output before you rely on it in production.

How to use CLAUDE.md / Rules File Generator

  1. 1

    Describe your project

    Start from a quick template or fill in tech stack, project type, naming convention, import style, architecture patterns and testing approach.

  2. 2

    Choose the assistant

    Select Claude Code, Cursor, GitHub Copilot, Windsurf or Cline. The output follows that assistant's file name and format.

  3. 3

    Add your own rules

    List directories to ignore, never-do rules and any custom rules. The preview updates as you type.

  4. 4

    Copy or download the file

    Copy the rules file or download it, then put it where the assistant reads it, such as CLAUDE.md at the repository root or .github/copilot-instructions.md for Copilot.

  5. 5

    Share with your team

    Commit the file so every team member, and their AI tools, follow the same standards. Update it as conventions evolve.

Questions and answers

What is CLAUDE.md?
CLAUDE.md is a Markdown file in a project that Claude Code loads as standing instructions: stack, conventions, commands and constraints. This generator writes one from a short form or a stack template such as Next.js or FastAPI, and can output the same rules for Cursor, Copilot, Windsurf or Cline.
What is .cursorrules?
A .cursorrules file in the project root gives Cursor's AI project instructions such as tech stack, coding style and things to avoid. This tool generates it from the same form it uses for CLAUDE.md and the other formats, so the rules stay consistent across assistants.
Do I need a rules file for every AI assistant?
Each assistant reads its own file format (CLAUDE.md, .cursorrules, .github/copilot-instructions.md, .windsurfrules, .clinerules). This tool generates each format from the same inputs; switch the assistant to get its file.
Can I import my existing rules file?
Not directly. Start from the quick template closest to your stack, then paste your existing rules into the Custom Rules field so they carry into every format.
What should I put in my rules file?
Start with tech stack, coding style preferences, and key constraints. The form guides you through the most impactful sections: project context, naming conventions, architecture patterns, and things to avoid.
For AI agents: how to call this tool

Machine-readable contract, endpoints and examples. Humans can ignore this section.

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/rules-file-generator/

For automation planning, fetch the canonical contract at /api/tool/rules-file-generator.json.