Cursor Memory Curator

Goal

Audit Cursor durable context as user-owned agent state: expose stale, unsafe, duplicated, ignored, conflicting, or misplaced rules; propose better destinations; and apply cleanup only after a report, backup, and explicit approval.

Keep the subject scoped to Cursor Project Rules, legacy .cursorrules, AGENTS.md, User Rules, Team Rules, and user-maintained Cursor memory-bank artifacts. Do not treat this as a Codex memory curator.

When to use

• The user asks to review, audit, clean up, prune, rewrite, or remove Cursor rules or persistent Cursor context.
• The user mentions .cursor/rules, .cursorrules, Cursor User Rules, Cursor Team Rules, stale rules, rule conflicts, or Cursor context pollution.
• The user asks whether a durable Cursor instruction belongs in a project rule, AGENTS.md, repo docs, User Rules, Team Rules, a skill, config, or deletion.
• The user reports that Cursor keeps forgetting, keeps using stale guidance, or is applying old project instructions.

When not to use