Name: memory-manage
Author: ZenRay

Prompt file imported from ZenRay/CursorTemplate (.cursor/commands/memory-manage.md). Copyright stays with the author.

/memory-manage — Native Memories Management

Manage Cursor's built-in memory feature for persistent context.

What are Native Memories?

Cursor Memories (v1.0+) automatically remember facts from conversations:

Persist across sessions
Stored per project, per user
AI suggests, user approves
Managed in Settings → Rules → Memories

vs KnowledgeExtractor Skill

Feature	Native Memories	KnowledgeExtractor Skill
Location	Cursor Settings	`~/Documents/PersonalKnowledge/`
Creation	AI suggests, user approves	`/archive-session` command
Scope	Per project	Cross-project
Format	Key-value pairs	Markdown documents
Management	Settings UI	File system

Commands

View Memories

/memory-manage list

Shows:

## Native Memories

| Key | Value | Created |
|-----|-------|---------|
| user-auth | Uses JWT with 15min expiry | 2024-01-15 |
| db-schema | Users table has email_verified | 2024-01-20 |
| api-limit | Rate limit 100req/min | 2024-02-01 |

Add Memory

/memory-manage add

Key: auth-method
Value: JWT with refresh tokens in httpOnly cookies
Tags: authentication, security

Edit Memory

/memory-manage edit auth-method

New value: OAuth2 + JWT hybrid with PKCE

Delete Memory

/memory-manage delete auth-method

Search Memories

/memory-manage search "authentication"

Returns matching keys and values.

Integration with Workflow

Session Start

Before starting work:

/memory-manage list
→ Review what Cursor already knows

During Session

When AI learns important fact:

AI: "I'll remember we use Redis for caching"

/memory-manage add
Key: caching-strategy
Value: Redis with 1hr TTL for user sessions

Session End

After important decisions:

/memory-manage add
Key: architecture-decision
Value: Migrated from REST to GraphQL for mobile optimization
Tags: architecture, 2024-03-01

Best Practices

What to Remember

✅ Good Memories:

Architecture decisions with rationale
Tech stack versions and constraints
API contracts and formats
Business logic rules
Debugging solutions to recurring issues

❌ Avoid:

Temporary workarounds
Code snippets (keep in codebase)
Complete documentation (keep in docs/)
Personal preferences

Memory Structure

Clear, searchable format:

Key: auth-flow-v2
Value: 
  - OAuth2 with Google/Apple providers
  - Access token: 15min, JWT
  - Refresh token: 7days, httpOnly cookie
  - PKCE for mobile apps
  - Fallback to email/password
Tags: authentication, oauth, v2, 2024-03

Regular Cleanup

Monthly review:

/memory-manage list --outdated

Delete:
- Obsolete versions
- Superseded decisions
- Temporary fixes that are now permanent

Settings Integration

Enable in Cursor:

Settings → Rules → Memories → "Generate Memories"

Options:

Auto-suggest: AI proposes memories
Manual only: You create all memories
Import/Export: Backup to JSON

Export/Backup

/memory-manage export

Saves to:
- `.cursor/memories-backup.json`
- Can commit to git (safe, no secrets)

Migration from Skills

If using KnowledgeExtractor Skill:

1. Keep Skill for cross-project knowledge
2. Add Native Memories for project-specific facts
3. Use both together:
   - `/memory-manage list` (native)
   - `@knowledge-extractor` (cross-project)

Example Memories

# Project: E-commerce API

auth-strategy:
  value: "JWT access + refresh tokens"
  created: 2024-01-15

rate-limits:
  value: "100 req/min auth, 10 req/min unauth"
  created: 2024-01-20

payment-flow:
  value: "Stripe → Webhook → Order confirmed → Email"
  created: 2024-02-01

database-constraints:
  value: "Users.email unique, Orders.user_id FK"
  created: 2024-02-15

Tips

Consistent naming: Use kebab-case keys
Date important ones: For tracking decisions
Tags: Group related memories
Regular review: Delete stale memories
Sync with team: Share critical memories

Install memory-manage and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /memory-manage — Native Memories Management Manage Cursor's built-in memory feature for persistent context. ## What are Native Memories? Cursor Memories (v1.0+) automatically remember facts from conversations: - Persist across sessions - Stored per project, per user - AI suggests, user approves - Managed in Settings → Rules → Memories ## vs KnowledgeExtractor Skill | Feature | Native Memories | KnowledgeExtractor Skill | |---------|-----------------|-------------------------| | Location | Cursor Settings | `~/Documents/PersonalKnowledge/` | | Creation | AI suggests, user approves | `/archive-session` command | | Scope | Per project | Cross-project | | Format | Key-value pairs | Markdown documents | | Management | Settings UI | File system | ## Commands ### View Memories ``` /memory-manage list ``` Shows: ``` ## Native Memories | Key | Value | Created | |-----|-------|---------| | user-auth | Uses JWT with 15min expiry | 2024-01-15 | | db-schema | Users table has email_verified | 2024-01-20 | | api-limit | Rate limit 100req/min | 2024-02-01 | ``` ### Add Memory ``` /memory-manage add Key: auth-method Value: JWT with refresh tokens in httpOnly cookies Tags: authentication, security ``` ### Edit Memory ``` /memory-manage edit auth-method New value: OAuth2 + JWT hybrid with PKCE ``` ### Delete Memory ``` /memory-manage delete auth-method ``` ### Search Memories ``` /memory-manage search "authentication" Returns matching keys and values. ``` ## Integration with Workflow ### Session Start Before starting work: ``` /memory-manage list → Review what Cursor already knows ``` ### During Session When AI learns important fact: ``` AI: "I'll remember we use Redis for caching" /memory-manage add Key: caching-strategy Value: Redis with 1hr TTL for user sessions ``` ### Session End After important decisions: ``` /memory-manage add Key: architecture-decision Value: Migrated from REST to GraphQL for mobile optimization Tags: architecture, 2024-03-01 ``` ## Best Practices ### What to Remember ✅ **Good Memories**: - Architecture decisions with rationale - Tech stack versions and constraints - API contracts and formats - Business logic rules - Debugging solutions to recurring issues ❌ **Avoid**: - Temporary workarounds - Code snippets (keep in codebase) - Complete documentation (keep in docs/) - Personal preferences ### Memory Structure Clear, searchable format: ``` Key: auth-flow-v2 Value: - OAuth2 with Google/Apple providers - Access token: 15min, JWT - Refresh token: 7days, httpOnly cookie - PKCE for mobile apps - Fallback to email/password Tags: authentication, oauth, v2, 2024-03 ``` ### Regular Cleanup Monthly review: ``` /memory-manage list --outdated Delete: - Obsolete versions - Superseded decisions - Temporary fixes that are now permanent ``` ## Settings Integration Enable in Cursor: ``` Settings → Rules → Memories → "Generate Memories" ``` Options: - Auto-suggest: AI proposes memories - Manual only: You create all memories - Import/Export: Backup to JSON ## Export/Backup ``` /memory-manage export Saves to: - `.cursor/memories-backup.json` - Can commit to git (safe, no secrets) ``` ## Migration from Skills If using KnowledgeExtractor Skill: ``` 1. Keep Skill for cross-project knowledge 2. Add Native Memories for project-specific facts 3. Use both together: - `/memory-manage list` (native) - `@knowledge-extractor` (cross-project) ``` ## Example Memories ```yaml # Project: E-commerce API auth-strategy: value: "JWT access + refresh tokens" created: 2024-01-15 rate-limits: value: "100 req/min auth, 10 req/min unauth" created: 2024-01-20 payment-flow: value: "Stripe → Webhook → Order confirmed → Email" created: 2024-02-01 database-constraints: value: "Users.email unique, Orders.user_id FK" created: 2024-02-15 ``` ## Tips 1. **Consistent naming**: Use kebab-case keys 2. **Date important ones**: For tracking decisions 3. **Tags**: Group related memories 4. **Regular review**: Delete stale memories 5. **Sync with team**: Share critical memories

{ "prompt": "# /memory-manage — Native Memories Management\n\nManage Cursor's built-in memory feature for persistent context.\n\n## What are Native Memories?\n\nCursor Memories (v1.0+) automatically remember facts from conversations:\n- Persist across sessions\n- Stored per project, per user\n- AI suggests, user approves\n- Managed in Settings → Rules → Memories\n\n## vs KnowledgeExtractor Skill\n\n| Feature | Native Memories | KnowledgeExtractor Skill |\n|---------|-----------------|-------------------------|\n| Location | Cursor Settings | `~/Documents/PersonalKnowledge/` |\n| Creation | AI suggests, user approves | `/archive-session` command |\n| Scope | Per project | Cross-project |\n| Format | Key-value pairs | Markdown documents |\n| Management | Settings UI | File system |\n\n## Commands\n\n### View Memories\n\n```\n/memory-manage list\n```\n\nShows:\n```\n## Native Memories\n\n| Key | Value | Created |\n|-----|-------|---------|\n| user-auth | Uses JWT with 15min expiry | 2024-01-15 |\n| db-schema | Users table has email_verified | 2024-01-20 |\n| api-limit | Rate limit 100req/min | 2024-02-01 |\n```\n\n### Add Memory\n\n```\n/memory-manage add\n\nKey: auth-method\nValue: JWT with refresh tokens in httpOnly cookies\nTags: authentication, security\n```\n\n### Edit Memory\n\n```\n/memory-manage edit auth-method\n\nNew value: OAuth2 + JWT hybrid with PKCE\n```\n\n### Delete Memory\n\n```\n/memory-manage delete auth-method\n```\n\n### Search Memories\n\n```\n/memory-manage search \"authentication\"\n\nReturns matching keys and values.\n```\n\n## Integration with Workflow\n\n### Session Start\n\nBefore starting work:\n```\n/memory-manage list\n→ Review what Cursor already knows\n```\n\n### During Session\n\nWhen AI learns important fact:\n```\nAI: \"I'll remember we use Redis for caching\"\n\n/memory-manage add\nKey: caching-strategy\nValue: Redis with 1hr TTL for user sessions\n```\n\n### Session End\n\nAfter important decisions:\n```\n/memory-manage add\nKey: architecture-decision\nValue: Migrated from REST to GraphQL for mobile optimization\nTags: architecture, 2024-03-01\n```\n\n## Best Practices\n\n### What to Remember\n\n✅ **Good Memories**:\n- Architecture decisions with rationale\n- Tech stack versions and constraints\n- API contracts and formats\n- Business logic rules\n- Debugging solutions to recurring issues\n\n❌ **Avoid**:\n- Temporary workarounds\n- Code snippets (keep in codebase)\n- Complete documentation (keep in docs/)\n- Personal preferences\n\n### Memory Structure\n\nClear, searchable format:\n\n```\nKey: auth-flow-v2\nValue: \n - OAuth2 with Google/Apple providers\n - Access token: 15min, JWT\n - Refresh token: 7days, httpOnly cookie\n - PKCE for mobile apps\n - Fallback to email/password\nTags: authentication, oauth, v2, 2024-03\n```\n\n### Regular Cleanup\n\nMonthly review:\n```\n/memory-manage list --outdated\n\nDelete:\n- Obsolete versions\n- Superseded decisions\n- Temporary fixes that are now permanent\n```\n\n## Settings Integration\n\nEnable in Cursor:\n\n```\nSettings → Rules → Memories → \"Generate Memories\"\n```\n\nOptions:\n- Auto-suggest: AI proposes memories\n- Manual only: You create all memories\n- Import/Export: Backup to JSON\n\n## Export/Backup\n\n```\n/memory-manage export\n\nSaves to:\n- `.cursor/memories-backup.json`\n- Can commit to git (safe, no secrets)\n```\n\n## Migration from Skills\n\nIf using KnowledgeExtractor Skill:\n\n```\n1. Keep Skill for cross-project knowledge\n2. Add Native Memories for project-specific facts\n3. Use both together:\n - `/memory-manage list` (native)\n - `@knowledge-extractor` (cross-project)\n```\n\n## Example Memories\n\n```yaml\n# Project: E-commerce API\n\nauth-strategy:\n value: \"JWT access + refresh tokens\"\n created: 2024-01-15\n\nrate-limits:\n value: \"100 req/min auth, 10 req/min unauth\"\n created: 2024-01-20\n\npayment-flow:\n value: \"Stripe → Webhook → Order confirmed → Email\"\n created: 2024-02-01\n\ndatabase-constraints:\n value: \"Users.email unique, Orders.user_id FK\"\n created: 2024-02-15\n```\n\n## Tips\n\n1. **Consistent naming**: Use kebab-case keys\n2. **Date important ones**: For tracking decisions\n3. **Tags**: Group related memories\n4. **Regular review**: Delete stale memories\n5. **Sync with team**: Share critical memories", "variables": [], "notes": "Manage Cursor Native Memories - view, edit, and organize AI memory", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/ZenRay/CursorTemplate", "path": ".cursor/commands/memory-manage.md", "ref": "0643e2b5863ee982562d545a9276c08523c183b8", "url": "https://github.com/ZenRay/CursorTemplate/blob/0643e2b5863ee982562d545a9276c08523c183b8/.cursor/commands/memory-manage.md", "key": "ZenRay/CursorTemplate/.cursor/commands/memory-manage.md" } } }

memory-manage

About