← all checks

Cursor rules: .cursor/rules and .cursorrules in open source repos

Cursor rules are instruction files Cursor reads from the repo: a .cursor/rules/ folder of .mdc files, one topic each, or the older single .cursorrules file at the root.

How many repos have Cursor rules?

Of the 401 repos on the leaderboard, 15 pass in full (4%), 3 pass in part (0.7%) and 383 fail (96%).

Why does Cursor need project rules?

Cursor's Rules docs name .cursor/rules/*.mdc and AGENTS.md as its repo instructions. Devin also pulls Cursor rule files into its Knowledge, so the check counts a little for Devin and most for Cursor.

What counts as Cursor rules?

  • Full pass: at least one .mdc file in .cursor/rules/, in a subfolder of it, or in a .cursor/rules/ folder up to three directories down. A plain .md file there does not count: Cursor ignores it.
  • 50%: only the older .cursorrules file. Cursor's current docs no longer mention it.
  • Fail: neither is present.

How checks become a score: methodology.

How do I add Cursor rules to my repo?

Create .cursor/rules/ with one .mdc file per topic: code organisation, naming and style, how to run tests. Move any .cursorrules content into them.

Which AI agents read Cursor rules?

Pass rate by language

Cursor rules vs AGENTS.md: which to use, and how to keep one source.

Top-scoring repos that pass

Popular repos that fail it

Every check, grouped into what to do first: how to make your repo ready for AI coding agents.