GEMINI.md vs Windsurf 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 | GEMINI.md 2026-08-01 | Windsurf rules 2026-08-01 |
|---|---|---|
| Asserted — what the docs say it can express | ||
| File | GEMINI.md | .windsurf/rules/*.md |
| Status | vendor | vendor |
| Cross-tool | No | No |
| Tools that read it |
|
|
| Frontmatter | No | Yes |
| Glob targeting | No | Yes |
| Imports other files | Yes | No |
| Nested / per-directory | Yes | No |
| Multiple files | Yes | Yes |
| User-level scope | Yes | Yes |
| When it applies | Hierarchical memory: a global ~/.gemini/GEMINI.md, then the project file, then nested files, concatenated from broadest to narrowest. | Four trigger modes in frontmatter: always_on, glob, model_decision, manual. The legacy single-file .windsurfrules is still read. |
| Size limits | None | Per-rule and total character caps apply; long rules are truncated rather than rejected. |
| Measured — counted from real repositories on 2026-08-03 | ||
| Repositories carrying it | 33 | 14 |
| Share of indexed repos | 4.8% | 2.0% |
| Files indexed | 46 | 102 |
| Median length (words) | 257 | 515 |
| 90th percentile length | 1,704 | 1,518 |
| Files naming commands | 52.2% | 37.3% |
| Files containing code | 45.6% | 70.6% |
| Median quality score | 60 | 58 |
| Median repository stars | 11,297 | 114 |
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.
GEMINI.md + Windsurf rules
2026-08-037
repositories carry both. That is 21.2% of everything with GEMINI.md, and 50.0% of everything with Windsurf rules.
What each one is for
GEMINI.md
2026-08-01Gemini CLI's memory file, structurally close to CLAUDE.md — @imports and a user-scope layer — which is why repos that carry both usually carry near-identical text in each.
Strengths
- @path imports and a global user file, same composition model as CLAUDE.md
- Explicit hierarchy from global to local
Weaknesses
- Google-only
- No glob targeting
Windsurf rules
2026-08-01Cursor's activation model with a different vocabulary — trigger modes instead of rule types — plus hard character caps, which is the one place a format here will silently drop instructions rather than fail loudly.
Strengths
- Trigger modes give the same glob and on-demand targeting as Cursor rules
- Workspace and global rule scopes
Weaknesses
- Windsurf-only
- Character caps truncate silently — a long rule can be half-applied with no error
- No imports
