Cursor Rules Generator
Generate .cursorrules files for the Cursor AI IDE. Pick your stack, set coding conventions.
One rule per line. These will appear as bullet points in the generated file.
.cursorrules Preview
# Project: Untitled # Generated by DevTk.AI ## Language & Framework - Language: (not specified) - Framework: (not specified) ## Code Style - Indentation: 2 Spaces - Naming convention: camelCase
How to Use This Tool
- Select your programming language from the dropdown — this determines the language-specific conventions in the generated rules.
- Choose your framework (React, Next.js, FastAPI, Express, etc.) to get framework-aware rules and patterns.
- Use a Quick Preset to instantly populate settings for common stacks like React + TypeScript or Python + FastAPI.
- Customize coding style (indentation, naming convention) to match your team's standards.
- Add any additional custom rules in the text area — one rule per line.
- Copy the generated .cursorrules content and save it as `.cursorrules` in your project root directory.
What is .cursorrules and Why It Matters
A .cursorrules file is a configuration file that tells the Cursor AI IDE how to write code in your project. It defines coding conventions, preferred libraries, patterns to follow or avoid, and other rules that guide AI-generated code to match your team's standards. Think of it as a style guide that the AI reads before writing any code.
Without a .cursorrules file, Cursor's AI makes its own assumptions about code style, naming conventions, and patterns. This can lead to inconsistent code that doesn't match your existing codebase. With a well-crafted .cursorrules file, every AI-generated code snippet follows your team's conventions from the start.
The .cursorrules format is specific to Cursor, but the concept extends to other AI coding assistants. GitHub Copilot uses `copilot-instructions.md`, Claude Code uses `CLAUDE.md`, and Windsurf uses `.windsurfrules`. If you use multiple AI coding tools, check out our Universal AI Coding Rules Generator that creates all formats from a single form.
Best practices for .cursorrules: Be specific about your stack and versions. Include naming conventions, file structure preferences, and testing requirements. List libraries you prefer and ones to avoid. Keep the file under 500 lines — too many rules can confuse the AI. Update it as your project evolves.
Last updated: February 2026
FAQ
What is a .cursorrules file?
A .cursorrules file tells Cursor AI IDE how to write code in your project. It defines coding conventions, preferred libraries, patterns to follow or avoid, and other rules that guide AI-generated code to match your team's standards.
Where should I place the file?
Place the .cursorrules file in the root directory of your project. Cursor automatically detects and applies it to all AI interactions within that project.
Does this work with other AI IDEs?
The .cursorrules format is specific to Cursor, but the generated rules can be adapted for other AI coding tools. Many developers also use similar rules as system prompts for ChatGPT or Claude when asking for code help.
How is .cursorrules different from CLAUDE.md?
.cursorrules is read by Cursor IDE's AI features, while CLAUDE.md is read by Claude Code (Anthropic's CLI tool). They serve the same purpose — guiding AI code generation — but use different formats. .cursorrules is plain text with direct instructions, while CLAUDE.md typically uses Markdown with structured sections.
What about the new .mdc format?
Cursor introduced the .mdc (Markdown Configuration) format as an evolution of .cursorrules. The .mdc format supports structured metadata, conditional rules, and more advanced configuration. However, .cursorrules remains widely supported and is the simpler option for most projects. Both formats are recognized by Cursor.