cursor-supermemory 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,18 @@
1
+ {
2
+ "hooks": {
3
+ "sessionStart": [
4
+ {
5
+ "type": "command",
6
+ "command": "bun run \"${CURSOR_PLUGIN_ROOT}/dist/session-start.js\"",
7
+ "timeout": 20
8
+ }
9
+ ],
10
+ "sessionEnd": [
11
+ {
12
+ "type": "command",
13
+ "command": "bun run \"${CURSOR_PLUGIN_ROOT}/dist/session-end.js\"",
14
+ "timeout": 30
15
+ }
16
+ ]
17
+ }
18
+ }
package/package.json ADDED
@@ -0,0 +1,28 @@
1
+ {
2
+ "name": "cursor-supermemory",
3
+ "version": "1.0.0",
4
+ "description": "Persistent AI memory for Cursor — powered by Supermemory",
5
+ "type": "module",
6
+ "bin": {
7
+ "cursor-supermemory": "./dist/cli.js"
8
+ },
9
+ "scripts": {
10
+ "build": "bun build ./src/cli.ts --outfile ./dist/cli.js --target node && bun build ./src/mcp-server.ts --outfile ./dist/mcp-server.js --target node && bun build ./src/hooks/session-start.ts --outfile ./dist/session-start.js --target node && bun build ./src/hooks/session-end.ts --outfile ./dist/session-end.js --target node",
11
+ "typecheck": "tsc --noEmit",
12
+ "dev": "bun run src/cli.ts"
13
+ },
14
+ "dependencies": {
15
+ "supermemory": "^4.11.1"
16
+ },
17
+ "devDependencies": {
18
+ "@types/bun": "latest",
19
+ "typescript": "^5"
20
+ },
21
+ "files": ["dist", "rules", "skills", "commands", "hooks", ".cursor-plugin", ".mcp.json"],
22
+ "keywords": ["cursor", "supermemory", "mcp", "memory", "ai", "plugin"],
23
+ "license": "MIT",
24
+ "repository": {
25
+ "type": "git",
26
+ "url": "https://github.com/supermemoryai/cursor-supermemory"
27
+ }
28
+ }
@@ -0,0 +1,21 @@
1
+ ---
2
+ description: Supermemory persistent memory tools — use them proactively
3
+ alwaysApply: true
4
+ ---
5
+
6
+ You have access to Supermemory MCP tools for persistent memory across coding sessions:
7
+
8
+ - `supermemory_search`: Search before answering questions about previous work, bugs, or patterns
9
+ - `supermemory_add`: Save decisions, fixes, preferences when user asks or when clearly valuable
10
+ - `supermemory_profile`: Get aggregated user profile and preferences
11
+ - `supermemory_list`: List recent memories for this project
12
+ - `supermemory_forget`: Delete a specific memory by ID
13
+
14
+ When to use:
15
+ - User mentions past sessions, previous work, or "last time" → search first
16
+ - User says "remember", "save this", "don't forget" → add immediately
17
+ - After solving a hard bug → save the solution and root cause
18
+ - Discovering architectural patterns or conventions → save them
19
+ - User asks why something was done a certain way → search for context
20
+
21
+ Scope: use `project` for codebase-specific knowledge, `user` for cross-project preferences.
@@ -0,0 +1,13 @@
1
+ ---
2
+ name: memory-init
3
+ description: Deep codebase exploration to initialize project memory. Use when starting work on a new project or when user asks to "index" or "learn" the codebase.
4
+ ---
5
+
6
+ 1. Explore the project structure: read package.json, README, main entry points
7
+ 2. Identify: tech stack, framework, architecture patterns, key directories
8
+ 3. Find conventions: naming, testing approach, build system, deployment
9
+ 4. Read core files to understand data models and business logic
10
+ 5. Save architecture summary: call `supermemory_add` with type=architecture
11
+ 6. Save tech stack: call `supermemory_add` with type=project-config
12
+ 7. Save key conventions: call `supermemory_add` with type=learned-pattern
13
+ 8. Confirm: "Codebase indexed — [N] memories saved about [project name]"
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: memory-save
3
+ description: Save important information to persistent memory. Use when user explicitly asks to remember something, or when you've solved a significant problem worth preserving.
4
+ ---
5
+
6
+ 1. Extract the key insight, decision, or solution to save
7
+ 2. Choose scope: `project` for codebase-specific, `user` for personal preferences
8
+ 3. Choose type: preference, architecture, error-solution, project-config, learned-pattern, or conversation
9
+ 4. Call `supermemory_add` with concise, searchable content
10
+ 5. Confirm to user that the information has been saved
@@ -0,0 +1,9 @@
1
+ ---
2
+ name: memory-search
3
+ description: Search persistent memory for relevant information from past coding sessions. Use when user asks about previous work, past bugs, architectural decisions, or anything that may have been worked on before.
4
+ ---
5
+
6
+ 1. Call `supermemory_search` with a focused query based on what the user is asking about
7
+ 2. If results found, surface relevant memories in your response with context
8
+ 3. If no results found, note that no prior memory exists for this topic
9
+ 4. For broad questions, try both project scope and user scope