Cursor rules vs Cline rules
Every comparison page on the web is a capability table someone wrote from the vendor docs in an afternoon. None of them can tell you how many real repositories ship each file, how long the median one runs, or how often two of them turn up in the same project. Those answers need a corpus, and RuleStack counts one every night.
| Format | Cursor rules 2026-08-02 | Cline rules 2026-08-01 |
|---|---|---|
| Asserted — what the docs say it can express | ||
| File | .cursor/rules/*.mdc | .clinerules |
| Status | vendor | vendor |
| Cross-tool | No | No |
| Tools that read it |
|
|
| Frontmatter | Yes | No |
| Glob targeting | Yes | No |
| Imports other files | Yes | No |
| Nested / per-directory | Yes | No |
| Multiple files | Yes | Yes |
| User-level scope | No | Yes |
| When it applies | Four modes set in frontmatter: Always Apply (every chat session), Apply Intelligently (the agent picks it by description), Apply to Specific Files (globs match the edited file), and Apply Manually (@-mentioned). Rules must carry the .mdc extension — a plain .md file in .cursor/rules is ignored. | Always in scope. Either a single .clinerules file or a .clinerules/ directory whose markdown files are all loaded. |
| Size limits | None | None |
| Measured — counted from real repositories on 2026-08-03 | ||
| Repositories carrying it | 179 | 79 |
| Share of indexed repos | 25.8% | 11.4% |
| Files indexed | 1,279 | 305 |
| Median length (words) | 272 | 262 |
| 90th percentile length | 1,171 | 1,412 |
| Files naming commands | 29.3% | 34.1% |
| Files containing code | 58.0% | 33.1% |
| Median quality score | 52 | 54 |
| Median repository stars | 24 | 1 |
How often they turn up together
A capability table cannot answer this at all. Of the repositories carrying the first format, this is the share that also carry the second — counted, both directions, on 2026-08-03.
Cursor rules + Cline rules
2026-08-0314
repositories carry both. That is 7.8% of everything with Cursor rules, and 17.7% of everything with Cline rules.
What each one is for
Cursor rules
2026-08-02The most expressive format here. Many small .mdc files, each with frontmatter declaring when it should load, so a rule about migrations only enters context when a migration is open. Costs the most to maintain and only one editor reads it.
Strengths
- Glob-scoped activation — the only widely-used format that keeps unrelated rules out of context
- Description-based activation lets the agent pull a rule in on demand
- Many small files are easier to review in a PR than one growing document
Weaknesses
- Cursor-only
- Frontmatter is a schema, and a malformed .mdc silently stops applying
- Fragmentation: rules spread over many files are easy to duplicate and contradict
Cline rules
2026-08-01A single file or a folder of files, all always-on. The folder form is the simplest way any format here lets you split rules into topics without also learning an activation model.
Strengths
- Directory form splits rules by topic with zero configuration
- Toggleable rule sets for switching context between tasks
Weaknesses
- Cline-only
- Everything is always-on — no targeting, so the folder form costs context
