memory
Skill13 starsChanged 11 days agoMITView on GitHub
Project memory — search, workstreams, notes, decisions. Auto-initializes on first use.
99 other projects use a version of this.
Adopted by
Most recently taken up by
- jaydubya818/ClaudeClaw-Mission-Controltheir own version, first seen Nov 8, 2026
- naman10parikh/pennytheir own version, first seen Nov 8, 2026
- NaturNestAI-Labs/beings-protocoltheir own version, first seen Nov 8, 2026
- maxtechera/memorytheir own version, first seen Nov 8, 2026
- wubinKKK/private-ai-workbenchtheir own version, first seen Nov 8, 2026
- shetengteng/skillix-hubtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
Maliot100XSkillsend-user-message
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.
Also in 4 projects that use this
jh941213Skilldocs-ci
문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.
Also in 3 projects that use this
jh941213Skilldocs-interfaces
API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.
Also in 3 projects that use this
- +6 more from naman10parikh
- +1 more from jh941213
Other versions99 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 99
- google-gemini/gemini-cli★ 109ksame name
- jlia0/tinyclaw★ 3.6ksame name
- TinyAGI/tinyagi★ 3.6ksame name
- TinyAGI/tinyclaw★ 3.6ksame name
- Chachamaru127/claude-code-harness★ 3.2ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- Muuuun/luxas★ 1.2ksame name
- shobcoder/shob★ 575same name
- boshu2/agentops★ 453same name
- makushingu/harness-maxxing★ 161same name
89 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- docs-reflectSkill
- memory-setupSkill
- parkSkill
- reflectSkill
- session-continueSkill
- session-endSkill
- session-insightsSkill
- session-restoreSkill
- session-startSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 82 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Create memory dir: mkdir -p "$(node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" dir)" (prints the path even when it does not exist yet)
- Very specific: line 29
Do NOT copy memory.js if the plugin is installed — use ${CLAUDE_PLUGIN_ROOT}/scripts/memory.js.
- Very specific: line 30
Ask: "What workstreams does the project have?" → create workstreams.json
- Distinctive: line 31
Ask: "Describe your role in 1-2 sentences" → Profile
- Distinctive: line 32
Ask: "Key links?" → Reference
- Very specific: line 85
All commands resolve the memory dir from cwd (or from the symlink location when called as memory/memory.js):
- Distinctive: line 230
Check for dead links, stale entries, size overflow, duplicates.
- Distinctive: line 236
Don't dump raw output — summarize and highlight relevant
- Distinctive: line 237
If not initialized → bootstrap automatically, don't error
“Common” is measured: kept by at least 6 in 10 of the 82 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/memory — Project Memory
Step 0: Resolve memory directory
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" dir # same folder as CC auto-memory (git root); prints the path, exits 1 if no memory yetmemory.js resolves the memory dir from cwd itself — no --dir needed. Each bash block runs in a fresh shell, so do not rely on variables set in another block.
If not initialized (no memory.js and no plugin found)
Bootstrap for this project:
- Create memory dir:
mkdir -p "$(node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" dir)"(prints the path even when it does not exist yet) - Do NOT copy
memory.jsif the plugin is installed — use${CLAUDE_PLUGIN_ROOT}/scripts/memory.js. Only copy if the plugin is not installed. - Ask: "What workstreams does the project have?" → create
workstreams.json - Ask: "Describe your role in 1-2 sentences" → Profile
- Ask: "Key links?" → Reference
- Create MEMORY.md:
# {Project} — Memory
## API
\```bash
node {absolute path to memory.js} <command>
\```
## Profile
{user answer}
## Rules
### Save
- Decision with reasoning → memory file with **Why:** and **How to apply:**
- User corrects you or confirms non-obvious choice → feedback memory
- Something surprising or counter-intuitive → note + memory
- Convert relative dates to absolute: "Thursday" → "2026-04-10"
### Don't save
- What git log already knows (commits, who changed what)
- What the code already shows (patterns, architecture)
- What CLAUDE.md already says
- Ephemeral task state (use TodoWrite)
### Format
- MEMORY.md = index only, max 200 lines. Details in separate .md files
- Each .md file has frontmatter: name, description, type (feedback/project/user/reference)
- workstreams.json = source of truth for aliases
- Use --brief for quick overviews, full output only when needed
### Session lifecycle
- Start of work → /session-start or /session-continue
- Ideas for later → /park (don't lose the thought)
- After big block of work → /reflect (workarounds, repetitions, insights → backlog)
- Before compact: save key decisions + update handoff
- Long session + topic changed → suggest /session-end
- End of work → /session-end (handoff for next session)
## Reference
{user links}- Verify:
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" list - "Memory ready. You can start working —
/memoryfor lookup."
Commands (when initialized)
All commands resolve the memory dir from cwd (or from the symlink location when called as memory/memory.js):
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" <command> [args]No arguments
Show workstreams + quick actions:
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" workstreamssearch <query>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" search "<query>"Summarize — don't dump raw. Highlight relevant to current task.
workstream <name>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" workstream "<name>"workstreams
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" workstreamsadd-workstream <name> <keywords...>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" add-workstream "<name>" <keywords...>recent [n]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" recent <n>decisions [topic]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" decisions "<topic>"list [type]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" list <type>note <text>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" note "<text>"handoff [<workstream>]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" handoff # global handoff
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" handoff <workstream> # per-ws (falls back to global)Prints NO_HANDOFF when neither per-workstream nor global file exists.
write-handoff --workstream=<name> --content=<file>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" write-handoff --workstream=<name> --content=<path>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" write-handoff --global --content=<path> # workstreams/handoff.mdFrontmatter auto-added; modified and branch are stamped so the SessionStart hook can flag an old or other-branch handoff.
card <workstream> [--material]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" card <workstream> # the card, or NO_CARD
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" card <workstream> --material # + decisions to draft or update it fromA workstream — a task, an experiment, an area — lives in a card, workstreams/<name>.md, kept current during work: what it is, why, what it doesn't do, where results live, what's open — sections as the workstream needs, status in free words. When a decision, an iteration result or an open question about it comes up, offer to update the card; draft from --material (decisions, corrections and reflections the watcher logged, newest first, with a marker where the card was last updated). Show the change, write only after the user agrees. Past ~150 lines move finished iterations out.
write-card --workstream=<name> --content=<file>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" write-card --workstream=<name> --content=<path>Writes workstreams/<name>.md (not the Write tool: CC's stamper would reshuffle the frontmatter); adds type: project, category: workstream if missing and stamps modified.
receipt [--json]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" receiptWhat this session left: memory files it wrote (by originSessionId), decisions / corrections / DOC / commits logged since its start, the workstreams it moved and whether their cards were updated. Writes nothing.
park / parked / unpark
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" park --title="<title>" --content=<path> [--workstream=<name>] [--kind=idea|task|question]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" parked [<workstream>] # parked items, oldest flagged, plus recent PARKED: notes
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" unpark <file> --to=<where> # the exit: picked-up | backlog | decision | ideas | dropParked is a state with an exit, not an ideas catalog: one file per item (workstreams/<name>/<slug>.md, or parked/<slug>.md), so recall can surface it. Use /park to draft and confirm.
unassigned [--days=30]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" unassignedDecisions that match no workstream's keywords, by day — material for proposing a new workstream when a theme recurs.
signals [--branch=<branch>]
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" signals # JSON: card index, card gaps, new-workstream, parked, pending DOC, recently offeredInput for the SessionStart hook. It shows the user at most two invitations (💡 lines) and logs OFFERED: <key> so the same one does not come back for two weeks; the model gets only the card index. Workstreams stay optional.
classify --items=<json>
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" classify --items=<path-to-json>Keyword-routes items by workstreams.json. Multi-label, case-insensitive. Unmatched → _unassigned.
session-activity
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" session-activityCurrent session's items (and DOC: subset) since last SESSION_START marker in today's notes. JSON output.
session-changes
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" session-changesGit commits + files union since session start. JSON output. Pipe with session-activity into classify for routing analysis (see /session-end Phase 1b).
docs
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" docsDOC: notes since the last review (DOCS_REVIEWED marker) for /docs-reflect. --all lists every one; --mark-reviewed closes a review.
recurring
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" recurringFind recurring feedback patterns.
reindex
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" reindexRebuild MEMORY.md index sorted by weight.
health
node "${CLAUDE_PLUGIN_ROOT}/scripts/memory.js" healthCheck for dead links, stale entries, size overflow, duplicates.
Rules
- Don't dump raw output — summarize and highlight relevant
- If not initialized → bootstrap automatically, don't error
- MEMORY.md = index. Detailed content in separate .md files
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

