remember · yeachan-heo — Claude Code skill: organize project knowledge
A skill to decide where discovered knowledge belongs: project memory for durable facts, notepad for short-lived context, docs for instructions. Keeps findings from getting lost in chat.
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a claude-codeWhat remember does
Remember sorts information by destination. Team knowledge that outlasts a project lives in project memory; short working notes go to notepad priority; temporary session notes stay in notepad working; conventions and instructions belong in docs or AGENTS and CLAUDE files.
The workflow is straightforward: gather session findings, classify each one (durable project fact, temporary note, operator preference, or duplicate), propose a destination, and write only there. The skill spots duplicates and conflicts that need cleanup.
Use it when your project accumulates unwritten conventions or when you need to separate working context (active sprint notes) from permanent knowledge (architecture decisions, known bugs).
What it helps with
- preserve a finding before it disappears into chat history
- decide whether information belongs in memory, notepad, or docs
- classify whether something is durable project fact or temporary working note
- find and clean up duplicates and conflicts across memory surfaces
- organize knowledge so the team can find it in the next session
Example prompts for the agent
- Remember that we discussed the database migration — it should go into project memory
- Which of our findings today are temporary, which should we lock in?
- Check if we already have this in project memory or notepad
How to install remember
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a claude-code2Manually: put the files in place
~/.claude/skills/remember/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/remember/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a codex2Manually: put the files in place
.agents/skills/remember/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a cursor2Manually: put the files in place
.cursor/skills/remember/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Yeachan-Heo/oh-my-claudecode remember2Manually: put the files in place
.github/skills/remember/SKILL.md1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a gemini-cli2Platform CLI
gemini skills install https://github.com/Yeachan-Heo/oh-my-claudecode --path skills/rememberManually: put the files in place
.devin/skills/remember/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set26
The whole set →Other versions of remember
Similar
Questions about remember
How do I install remember in Claude Code?
Run npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a claude-code. The skill lands in ~/.claude/skills/remember/SKILL.md.
What does remember do?
Remember helps you sort information found during work: project memory for durable team knowledge, notepad priority for short-lived context for the next turns, notepad working for temporary session notes, and docs/AGENTS/CLAUDE for instructions and conventions. It keeps findings from getting lost in chat history.
How do I decide whether to store something in memory, notepad, or docs?
Remember classifies each item: project memory holds durable facts that matter beyond one session (architecture, known bugs), notepad priority holds short context for immediate next turns, notepad working holds temporary notes from the current session, docs/AGENTS/CLAUDE hold instructions and agreements. The skill helps you choose and flags duplicates or conflicts.
Source text
SKILL.md · MIT
--- name: remember description: Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs --- # Remember Use this skill when the user wants to preserve or organize useful knowledge discovered during a session. ## Goal Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history. ## Memory surfaces - **Project memory** — durable team/project knowledge - **Notepad priority** — short high-signal context for the next turns - **Notepad working** — temporary active-session notes - **Docs / AGENTS / CLAUDE files** — durable instructions and conventions when they truly belong there ## Workflow 1. Gather the relevant session findings. 2. Classify each item: - durable project fact - temporary working note - operator preference or instruction - duplicate / stale / conflicting information 3. Propose the best destination for each item. 4. Write or update only the appropriate memory surface. 5. Call out duplicates or conflicts that should be cleaned up. ## Rules - Do not dump everything into one store. - Prefer project memory for durable team knowledge. - Prefer notepad for short-lived working context. - Keep entries concise and actionable. - If something is uncertain, mark it as uncertain rather than storing it as fact. ## Output - What was stored - Where it was stored - Any duplicates/conflicts found
© Yeachan-Heo · MIT · Yeachan-Heo/oh-my-claudecode