stark-ai-de/agent-skills / skills/cursor-operations/cursor-memory-curator
cursor-memory-curator
VerifiedAudit and safely curate Cursor rules and provided memory-bank context. Use when reviewing stale, conflicting, sensitive, or misplaced Cursor instructions, not generic repository docs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.3 KB |
| assets/cleanup-plan-template.md | markdown | 2.0 KB |
| assets/review-report-template.md | markdown | 2.2 KB |
| references/classification-rubric.md | markdown | 4.6 KB |
| references/conflict-resolution.md | markdown | 1.7 KB |
| references/context-surface-anatomy.md | markdown | 2.6 KB |
| references/example-review-report.md | markdown | 2.3 KB |
| references/plan-lifecycle.md | markdown | 1.8 KB |
| references/safe-editing-procedure.md | markdown | 5.3 KB |
| scripts/backup-cursor-context.mjs | script | 40.0 KB |
| scripts/inventory-cursor-context.mjs | script | 6.9 KB |
| scripts/scan-cursor-context-risks.mjs | script | 10.1 KB |
references/context-surface-anatomy.md
View on GitHub# Cursor Context Surface Anatomy
Use this reference when deciding which Cursor surface owns a durable instruction.
## Project Rules
Cursor Project Rules live in `.cursor/rules/` and use `.mdc` files. Treat the YAML frontmatter as behavior metadata:
- `description` describes when an intelligent rule should be considered.
- `globs` scopes rules to file patterns.
- `alwaysApply` marks a rule as broadly applied.
Prefer Project Rules for project-specific guidance that benefits from Cursor rule metadata, file scoping, or manual rule attachment.
Flag plain `.md` files under `.cursor/rules` as rule candidates that lack Cursor Project Rule metadata. Recommend converting them to `.mdc` or moving simple instructions to `AGENTS.md`.
## Legacy `.cursorrules`
Treat `.cursorrules` as legacy project context. If modern `.cursor/rules/*.mdc` files cover the same guidance, classify the older claim as `DELETE`, `KEEP BUT REWRITE`, or migration to a Project Rule.
## `AGENTS.md`
Cursor supports `AGENTS.md` in the project root and subdirectories. Prefer `AGENTS.md` for straightforward agent instructions that should be readable across agent runtimes and do not need Cursor rule metadata.
Nested `AGENTS.md` files are more specific than parent files for work in that subtree.
## User Rules
User Rules are global preferences configured in Cursor settings. Treat them as user-level preferences such as communication style or broad coding conventions.
Do not claim a local editable User Rules file unless current Cursor evidence proves one. If the user provides exported text, review it and return manual settings changes unless they approve editing the exported artifact.
## Team Rules
Team Rules are shared organization or team instructions managed through Cursor. Treat them as high-impact shared policy. Do not edit them directly from repo files unless the user provides an explicit exported artifact and approval.
Classify team-wide standards as `MOVE TO CURSOR TEAM RULES` only when they are durable, non-secret, and broader than one repo.
## Memory-Bank Artifacts
Some users keep Cursor memory-bank files in locations such as `memory-bank/`, `docs/memory/`, or `.cursor/memory-bank/`. There is no assumed official `~/.cursor/memories` store for this skill.
Treat memory-bank files as user-maintained artifacts:
- Review them when the user provides a path.
- Preserve their schema if it is clear.
- Defer the proposal in chat or the single curation record instead of editing or creating a sibling context file when the schema is unclear.
## Source Basis
- Cursor Rules docs: https://cursor.com/docs/rules
- Cursor Agent Skills docs: https://cursor.com/docs/skills
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |