memory
Skill8 starsChanged 5 months agoMITView on GitHub
How this workspace keeps long-term memory. Auto-loads whenever you are about to write to, organize, or recall persistent memory across sessions.
110 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- eduardoweberai-cloud/claude-skillstheir own version, first seen Nov 16, 2026
- arxdsilva/ai-loopstheir own version, first seen Nov 16, 2026
- raucheacho/lorag-claude-codetheir own version, first seen Nov 16, 2026
- matthewwong525/WongStacktheir own version, first seen Nov 15, 2026
- maxwell2732/claudecode-research-harness-workflowtheir own version, first seen Nov 15, 2026
- XORwell/archeflowtheir own version, first seen Nov 15, 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
roronoazoroshao369Skillmemory-compression
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
- +5 more from naman10parikh
- +1 more from jh941213
Other versions110 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- thesawdawg/agent-skills★ 217% same
Wrote their own version · 109
- 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★ 454same name
- makushingu/harness-maxxing★ 235same name
99 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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 93 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Don't store what the repo already records — code structure, past fixes, git history, or anything in CLAUDE.md — nor what only matters to …
“Common” is measured: kept by at least 6 in 10 of the 93 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
Claude Code ships auto memory (on by default, v2.1.59+): notes Claude writes
for itself that persist across sessions. They live in
~/.claude/projects/<project>/memory/ — machine-local, per repository, never
committed. MEMORY.md (its index) loads at the start of every session; topic
files load on demand. This file is the house style for that memory: keep it
organized and it becomes a real asset; let it sprawl and it becomes noise.
The shape
MEMORY.mdis an index, not a dump. One short line per stored fact, each pointing to a topic file:- [Title](topic-file.md) — one-line hook. Keep it lean (it loads every session). Small, high-frequency facts can live inline.One fact per topic file. A topic file holds a single durable thing, with frontmatter:
--- name: <short-kebab-slug> description: <one line — used to judge relevance on recall> type: user | feedback | project | reference --- <the fact. For feedback/project, follow with **Why:** and **How to apply:** lines.>- Link related memories with
[[other-slug]]. Link liberally; a link to a file that doesn't exist yet just marks one worth writing.
What each type is for
- user — who the user is: role, expertise, durable preferences.
- feedback — guidance on how you should work (corrections and confirmed approaches). Include the Why.
- project — ongoing work, goals, or constraints not derivable from the code or git. Convert relative dates to absolute.
- reference — pointers to external resources (URLs, dashboards, tickets, docs).
When NOT to save
Don't store what the repo already records — code structure, past fixes, git history, or anything in CLAUDE.md — nor what only matters to the current conversation. If asked to "remember" one of those, save the non-obvious part (why it mattered), not the fact itself.
Hygiene
- Before saving, check for an existing file on the topic and update it rather than duplicating. Delete memories that turn out to be wrong.
- Never put credentials in memory. Secrets go in a dedicated, gitignored
file (
.credentials/), never in a memory note. - Recall is background, not instruction. A recalled memory reflects what was true when it was written. If it names a file, flag, or command, verify that still exists before acting on it.
Browse or edit memory any time with /memory.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

