Cursor AI Guides

Practical guides for getting the most out of your Cursor AI setup.

Research

I scanned 50 real projects. Most Cursor rules are broken.

We ran cursor-doctor on 50 real GitHub repos. 60% scored a C. The #1 problem: rules that waste your context window. Here are the 5 most common issues and how to fix them.

Debug

5 Cursor rule mistakes that make the AI ignore you

Your .mdc files might look fine. These 5 common mistakes cause Cursor to silently ignore your instructions, contradict itself, or waste your context window.

Lint

How to lint your Cursor rules

Your rules might have bugs you can't see. Broken frontmatter, conflicting instructions, vague prompts. Here's how to find them with one command.

Fix

How to fix Cursor rule conflicts

When two rules say different things, Cursor picks one silently. Here's how to find and resolve conflicts before they waste your time.

Optimize

Cursor token budget: how many rules is too many?

Every rule eats into your context window. Here's how to measure your token budget, find waste, and get more out of fewer tokens.

Write

How to write Cursor rules that actually work

The difference between rules that get followed and rules that get ignored. Frontmatter, structure, examples, and prompt engineering.

Migrate

Migrating from .cursorrules to .mdc files

Switch to the modern format with frontmatter, per-file rules, and globs. What changes, what to check, and how to run the migration command.

Automate

Run cursor-doctor in CI with GitHub Actions

Lint your Cursor rules automatically to catch broken frontmatter and invalid globs before they reach production.

Generate

Generate Cursor rules from your codebase with AI

Scan your code with Gemini to generate .mdc rules automatically. How rulegen-ai works, what it produces, and when to use it.

Convert

Convert rules between Cursor, Windsurf, and Claude Code

Bidirectional conversion between .mdc, .cursorrules, CLAUDE.md, and Windsurf formats. Switch editors without rewriting your rules.

Teams

Sharing Cursor rules across a team

Commit .cursor/rules/ to git, use globs for different roles, and avoid merge conflicts. How to keep your team in sync.