Best Cursor Rules

A curated collection of Cursor AI rules that actually work.

Skip the guesswork. These rules are battle-tested, framework-specific, and ready to drop into your project.

Quick Start

Option A: Use the Setup Wizard (recommended)

1. Open your project in Cursor (not this repo)
2. Switch to Plan Mode or Agent Mode
3. Paste the contents of SETUP-WIZARD.md into the chat
4. Answer a few questions about your stack
5. Done! The AI creates your .cursor/rules/ folder automatically

Note: The wizard must be run from inside your actual project directory, not from this repository.

[!TIP] Plan Mode (recommended) — More structured. The AI analyzes your project, asks focused questions, shows you exactly what will be created, then executes after you confirm.

[!TIP] Agent Mode — More conversational. The AI iterates with you and creates files on the fly. Good if you want to adjust things as you go.

Option B: Manual Setup

1. Create .cursor/rules/ in your project root
2. Copy the rules you need from the rules/ folder
3. Update the globs in each file to match your project structure

Available Rules

Frameworks

Languages

Backends

Styling

Testing

Best Practices

Stack Presets

These combine multiple rules for common technology combinations:

How the Wizard Works

The Setup Wizard is a special prompt that turns Cursor into a project analyzer:

1. Detection - It reads your package.json, tsconfig.json, config files, etc.
2. Questions - Asks 4-6 questions to understand your preferences
3. Planning - Shows you exactly which rules will be created
4. Execution - Creates .cursor/rules/ with customized rules

The wizard adapts to your project. Using Supabase? It includes those patterns. TypeScript strict mode? It adjusts accordingly. It's not a one-size-fits-all dump of rules.

Rule Format

Each rule uses the MDC (Markdown + Config) format:

---
description: Brief description for AI context
globs: ["**/*.tsx", "**/*.ts"]
alwaysApply: false
---

# Rule Title

## Section
Content, code examples, tables, etc.

• description - Helps the AI understand when to apply this rule
• globs - File patterns that trigger this rule (empty = manual only)
• alwaysApply - If true, always included regardless of file type

Rules are written to be concise and scannable. No fluff, just patterns and examples.

Contributing

Want to add a rule or fix something? Check out CONTRIBUTING.md.

The short version:

1. Fork the repo
2. Add/edit rules in rules/
3. Follow the format in .cursor/rules/01-rule-format.mdc
4. Submit a PR

Why This Exists

Cursor's AI is powerful, but it doesn't know your stack. These rules give it the context it needs:

• "Use Server Components by default" (Next.js 15)
• "Always enable RLS on tables" (Supabase)
• "Prefer unknown over any" (TypeScript)

Without rules, you end up correcting the AI constantly. With the right rules, it writes code the way you want it.

Credits

Maintained by Renvia Technologies with contributions from the community.

Licensed under CC0 - do whatever you want with these rules.

"Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program."
_{— Linus Torvalds}

_{Built with ☕ and too many terminal tabs}