Anysphere · .cursorrules and .mdc files
Best Cursorrules & configs — RuleSell
Cursor is a VS Code fork built around AI editing — Composer, Agent mode, tab autocomplete, and per-project rules via .cursorrules or .mdc files. Rules tell the model your project's conventions so it stops re-inventing your stack on every prompt.
Top 5 Cursor rules right now
Ranked by quality score — freshness, schema completeness, and review signals. Refreshed daily.
Why use Cursor rules from RuleSell
- Quality-scored Cursor rules — every .cursorrules and .mdc file gets an automated grade from freshness, schema, and review signals.
- Frameworks covered: Next.js, React, FastAPI, Go, Rust, Flutter, Django, Rails, and 30+ more.
- Real GitHub author attribution and SPDX license (no anonymous re-uploads).
- Copy-paste install — drop into .cursorrules or .cursor/rules/ and you're done.
How to use Cursor rules
1. Pick a Cursor rule
Browse the listings below and open one that matches your stack.
2. Copy the file contents
Click "Copy" on the listing — or download the raw file from the source URL.
3. Paste into .cursorrules at repo root, or .cursor/rules/*.mdc
Drop the rule into .cursorrules at repo root, or .cursor/rules/*.mdc. The exact command: # Copy the rule into your repo root:
4. Restart Cursor
Restart your Cursor session so the new rule is loaded. Verify it appears in the active context.
# Copy the rule into your repo root:
cp rule.cursorrules ./.cursorrules
# Or for scoped rules:
mkdir -p .cursor/rules && cp rule.mdc .cursor/rules/Cursor rules — frequently asked
Where do Cursor rules live in a project?
Cursor reads .cursorrules at the repo root for project-wide rules, and .cursor/rules/*.mdc files for scoped or auto-attached rules. Both formats are supported.
What's the difference between .cursorrules and .mdc?
.cursorrules is a single project-wide file in markdown. .mdc files in .cursor/rules/ are scoped — you can attach them to specific globs (e.g. **/*.tsx) or invoke them manually via @rule-name.
How do I share Cursor rules with my team?
Commit .cursorrules and the .cursor/rules/ directory to git. Every teammate gets the same rules automatically when they pull.
Are Cursor rules the same as Claude Code skills?
Conceptually similar — both inject project-specific guidance into the model. Format differs: Cursor uses .cursorrules/.mdc; Claude Code uses skills, agents, and hooks under ~/.claude/. Many rules on RuleSell ship in both formats.
Why use a quality-scored .cursorrules file over an awesome-list?
awesome-* GitHub lists are alphabetical link dumps with no review — you have no idea if a rule is 6 months stale or breaks your stack. RuleSell scores every listing on freshness, schema, and review signals so you pick what actually works.