@pcircle/memesh 3.0.0 → 3.0.1

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pcircle/memesh",
3
- "version": "3.0.0",
3
+ "version": "3.0.1",
4
4
  "description": "MeMesh — The lightest universal AI memory layer. One SQLite file, any LLM, zero cloud.",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",
@@ -12,9 +12,11 @@
12
12
  },
13
13
  "files": [
14
14
  "dist/",
15
+ "dashboard/dist/",
15
16
  ".mcp.json",
16
17
  "hooks/hooks.json",
17
18
  "scripts/hooks/",
19
+ "skills/",
18
20
  "plugin.json",
19
21
  "README.md",
20
22
  "LICENSE"
package/plugin.json CHANGED
@@ -1,12 +1,20 @@
1
1
  {
2
2
  "name": "memesh",
3
3
  "description": "MeMesh — The lightest universal AI memory layer. One SQLite file, any LLM, zero cloud.",
4
- "author": { "name": "PCIRCLE AI" },
5
- "version": "3.0.0",
4
+ "author": {
5
+ "name": "PCIRCLE AI"
6
+ },
7
+ "version": "3.0.1",
6
8
  "homepage": "https://github.com/PCIRCLE-AI/memesh-llm-memory",
7
9
  "repository": "https://github.com/PCIRCLE-AI/memesh-llm-memory",
8
10
  "license": "MIT",
9
- "keywords": ["claude-code", "mcp", "knowledge-graph", "ai-memory"],
11
+ "keywords": [
12
+ "claude-code",
13
+ "mcp",
14
+ "knowledge-graph",
15
+ "ai-memory"
16
+ ],
10
17
  "mcpServers": "./.mcp.json",
11
- "hooks": "./hooks/hooks.json"
18
+ "hooks": "./hooks/hooks.json",
19
+ "skills": "./skills"
12
20
  }
@@ -0,0 +1,73 @@
1
+ ---
2
+ name: memesh
3
+ description: Use MeMesh to remember, recall, and manage AI knowledge across sessions. Triggers when the user asks to remember something, recall past decisions, forget outdated info, or manage their memory. Also triggers proactively when you make important decisions, fix bugs, or learn lessons worth preserving.
4
+ user-invocable: true
5
+ ---
6
+
7
+ # MeMesh — AI Memory Management
8
+
9
+ You have access to MeMesh, a persistent memory layer with 6 tools. Use them to remember important knowledge across sessions.
10
+
11
+ ## When to Use (Proactive)
12
+
13
+ **Remember automatically when:**
14
+ - A design decision is made ("let's use OAuth" → remember it)
15
+ - A bug is fixed (root cause + fix → remember as lesson)
16
+ - A pattern is established ("we always use Zod for validation" → remember as pattern)
17
+ - Architecture changes ("moved from monolith to microservices" → remember)
18
+ - The user explicitly says "remember this" or "don't forget"
19
+
20
+ **Recall automatically when:**
21
+ - Starting work on a feature that might have prior decisions
22
+ - The user asks "what did we decide about X?"
23
+ - You need context about a project's conventions
24
+
25
+ **Forget when:**
26
+ - A decision is superseded by a new one (use `supersedes` relation)
27
+ - The user says "forget about X" or "that's outdated"
28
+
29
+ ## Tools Reference
30
+
31
+ ### remember
32
+ ```json
33
+ {
34
+ "name": "auth-decision",
35
+ "type": "decision",
36
+ "observations": ["Use OAuth 2.0 with PKCE for authentication"],
37
+ "tags": ["project:myapp", "topic:auth"],
38
+ "relations": [{"to": "old-auth", "type": "supersedes"}]
39
+ }
40
+ ```
41
+ Types: `decision`, `pattern`, `lesson`, `bug_fix`, `architecture`, `convention`
42
+
43
+ ### recall
44
+ ```json
45
+ {"query": "authentication", "tag": "project:myapp", "limit": 10}
46
+ ```
47
+ Omit query to list recent memories. Results are ranked by relevance, recency, and access frequency.
48
+
49
+ ### forget
50
+ ```json
51
+ {"name": "outdated-design"}
52
+ ```
53
+ Archives the entity (soft-delete). Add `"observation": "specific text"` to remove just one fact.
54
+
55
+ ### consolidate
56
+ ```json
57
+ {"name": "auth-history", "min_observations": 5}
58
+ ```
59
+ Compresses verbose memories using LLM. Requires Smart Mode configured.
60
+
61
+ ### export / import
62
+ ```json
63
+ {"tag": "project:myapp"}
64
+ ```
65
+ Export memories as JSON for sharing. Import with merge strategies: `skip`, `overwrite`, `append`.
66
+
67
+ ## Best Practices
68
+
69
+ 1. **Be specific** — "Use OAuth 2.0 with PKCE" not "auth stuff decided"
70
+ 2. **Tag by project** — Always include `project:<name>` tag
71
+ 3. **Use relations** — Link related decisions with `related-to`, replace old ones with `supersedes`
72
+ 4. **Type correctly** — Use the right type (decision/pattern/lesson) for better search
73
+ 5. **Don't over-remember** — Skip trivial things. Remember decisions that took > 5 minutes to make.
@@ -0,0 +1,54 @@
1
+ ---
2
+ name: memesh-review
3
+ description: Review and clean up the MeMesh memory database. Find stale, contradicting, or redundant memories and suggest cleanup actions. Use when asked to "review memories", "clean up knowledge", or "what's in my memory".
4
+ user-invocable: true
5
+ ---
6
+
7
+ # MeMesh Memory Review
8
+
9
+ Review the memory database and provide actionable cleanup recommendations.
10
+
11
+ ## Process
12
+
13
+ 1. **Recall recent memories** — use `recall` with no query to see what's stored
14
+ 2. **Check for staleness** — identify memories not accessed in 30+ days
15
+ 3. **Check for conflicts** — look for `contradicts` relations or opposing observations
16
+ 4. **Check for verbosity** — entities with 5+ observations that could be consolidated
17
+ 5. **Report findings** with specific actions
18
+
19
+ ## Steps
20
+
21
+ ### Step 1: Load overview
22
+ ```json
23
+ recall: {"limit": 50}
24
+ ```
25
+
26
+ ### Step 2: Analyze and report
27
+
28
+ Present findings in this format:
29
+
30
+ ```
31
+ ## Memory Review
32
+
33
+ ### Summary
34
+ - Total memories recalled: N
35
+ - Active: N | Archived: N
36
+
37
+ ### Stale (not accessed in 30+ days)
38
+ - "entity-name" — last observation: "..." — Suggest: archive or keep?
39
+
40
+ ### Could be consolidated (5+ observations)
41
+ - "entity-name" (8 observations) — Suggest: run consolidate
42
+
43
+ ### Potential conflicts
44
+ - "use-jwt" vs "no-jwt" — contradicting auth decisions
45
+
46
+ ### Recommended actions
47
+ 1. Archive "old-design" (superseded by "new-design")
48
+ 2. Consolidate "auth-history" (12 observations → ~3)
49
+ 3. Review conflict between "X" and "Y"
50
+ ```
51
+
52
+ ### Step 3: Execute approved actions
53
+
54
+ After presenting the report, ask the user which actions to execute. Then use `forget`, `consolidate`, or `remember` with `supersedes` accordingly.