Clogmeter
Weigh your AGENTS.md / CLAUDE.md / Cursor rules in the browser → Clogmeter counts tokens, flags duplicates and always/never conflicts, and suggests trims. Nothing leaves your machine.

Home · Guides · Monday 2 Nov 2026

Why Cursor is ignoring your rules (.mdc + frontmatter)

On X and Reddit, “Cursor is ignoring my rules” is often not an adherence problem — the rule never entered context. Cursor project rules live in .cursor/rules/ as .mdc files with YAML frontmatter. A plain .md in that folder is ignored. Cursor also reads root AGENTS.md / CLAUDE.md as simpler always-on markdown.

Checklist below matches Cursor’s public Rules docs (keep rules under 500 lines; split large ones).

Five checks before you rewrite the rule

  1. Extension: file must end in .mdc inside .cursor/rules/.
  2. Frontmatter fields: only description, globs, and alwaysApply control load mode.
  3. Always Apply: alwaysApply: true puts the rule in every chat (use sparingly — it costs tokens every turn).
  4. File-scoped: set globs and alwaysApply: false so it attaches when matching files are in context.
  5. Apply Intelligently / manual: a description without globs lets the agent decide; with neither description nor globs nor alwaysApply, you typically need to @-mention the rule.

Minimal working example

---
description: TypeScript conventions for this repo
globs:
  - "**/*.ts"
  - "**/*.tsx"
alwaysApply: false
---

- Prefer explicit return types on exported functions
- Follow the patterns in @src/lib/result.ts instead of inventing new Result helpers

If it loads but still feels ignored

Prefer a short AGENTS.md example for cross-tool basics, and reserve .mdc for activation control. Compare formats in CLAUDE.md vs AGENTS.md vs Cursor rules.

Open Clogmeter and weigh your instruction files → Free, browser-only. Export a trimmed copy when you are done.

No spam. Unsubscribe anytime. We never share your email.