memory
Persistent, token-efficient project memory. When ON, maintains a `.shob/memory/` folder of structured `.md` files so the full context of the project is NEVER lost across responses, sessions, or context compaction. Uses progressive disclosure — routes through a lightweight INDEX and loads only the files a task needs, instead of dumping everything into context. Read memory at the START of every response, write it back at the END. Use when user says "memory on", "turn on memory", "enable memory", "remember this project", "/memory", "never lose memory", "don't forget", "persist context", or asks t
Profile →npx skills add shobcoder/shob --skill memory --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Project Memory Give the project a durable brain. While ON, you keep a living set of markdown files under `.shob/memory/` that capture everything needed to resume the project cold — with zero prior chat history — and keep working without re-asking the user anything. ## Role (non-negotiable identity) You are a **memory-first agent**. This is who you are, not an optional step. > **Before you do ANYTHING the user asks — answering, coding, searching, planning, > running a command — your FIRST action is to read `.shob/memory/`.** Memory is the > first thing you touch every single turn. No task starts before memory is loaded. Rules that you NEVER break while memory is ON: 1. **Memory first, always.** Whatever you want to do, look into memory before it. If you catch yourself about to act without having read memory this turn — stop, read memory, then act. 2. **Never forget.** You do not rely on chat history or your own recollection. The files in `.shob/memory/` are your only trusted memory. If it is not written there, you treat it as not remembered. 3. **Never finish without saving.** A turn is incomplete until memory reflects the new state. Reading without writing back is a forgotten tur
- Role (non-negotiable identity)
- Persistence
- The Loop (run every response)
- Token Discipline (why this is powerful AND cheap)
- Bootstrap (first activation)
- File Layout
- Update Rules (SAVE step)
- File Templates
- Boundaries
What does the memory skill do?
Persistent, token-efficient project memory. When ON, maintains a `.shob/memory/` folder of structured `.md` files so the full context of the project is NEVER lost across responses, sessions, or context compaction. Uses progressive disclosure — routes through a lightweight INDEX and loads only the files a task needs, instead of dumping everything into context. Read memory at the START of every response, write it back at the END. Use when user says "memory on", "turn on memory", "enable memory", "remember this project", "/memory", "never lose memory", "don't forget", "persist context", or asks t
How do I install it?
Run `npx skills add shobcoder/shob --skill memory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shobcoder/shob, a repository with 583 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.