Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Yeachan-Heo/oh-my-claudecode --skill remember -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/remember/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/remember/

From the same set26

The whole set →
ai-slop-cleaner Yeachan-Heo Cleans bloated AI-generated code by deleting dead logic and duplicate abstractions. It keeps current behavior locked under regression tests. Claude Code CX Codex Cursor +1 1,500installs ralplan Yeachan-Heo A skill that runs iterative planning with three agents (Planner, Architect, Critic) until consensus. Blocks vague requests before execution, never runs changes without your approval. Claude Code CX Codex Cursor +1 1,200installs hud Yeachan-Heo The hud skill configures a HUD display in Claude Code's statusline, showing git branch, context usage, running subagents, and other metrics. Track session state and keep tabs on complex work without losing context. Claude Code CX Codex Cursor +1 1,100installs deepinit Yeachan-Heo Walks a repository and writes an AGENTS.md per directory: what sits there, how the parts connect, what an agent should know before editing. Claude Code CX Codex Cursor +1 1,000installs autopilot Yeachan-Heo A skill that takes a task description and runs the full development cycle: requirements analysis, design, implementation, testing, and validation—all hands-off. Use it when you want to describe what you need and get working code back. Claude Code CX Codex Cursor +1 999installs deep-interview Yeachan-Heo A skill that runs a Socratic interview on your idea, scores ambiguity across weighted dimensions, and blocks coding until the score falls under the threshold. Claude Code CX Codex Cursor +1 998installs omc-setup Yeachan-Heo Canonical setup and repair wizard for oh-my-claudecode. It configures CLAUDE.md files, HUD statusline, and agent team defaults. Claude Code CX Codex Cursor +1 987installs ralph Yeachan-Heo A persistence loop that works through tasks in prd.json until all stories pass and get reviewer verification. Useful for multi-step jobs that need guaranteed completion. Claude Code CX Codex Cursor +1 971installs

Other versions of remember

Similar

redux vercel-labs A Redux adapter for json-render: it points the renderer at a store slice instead of its own state. Useful when app state already lives in Redux. Claude Code CX Codex Cursor +1 1,100installs agent-manager-skill sickn33 A procedure for driving several local CLI agents in tmux sessions: start, stop, tail logs, hand out tasks. Useful when work runs in parallel. Claude Code CX Codex Cursor +1 932installs planning-with-files sickn33 Keeps task context in markdown files inside the project folder, turning disk storage into agent working memory. Useful for multi-step builds and research tasks. Claude Code CX Codex Cursor +1 932installs mantis-meta-agent official google A campaign supervisor for Mantis security review: it keeps the loop running pass after pass and holds state and snapshots. Built for reviews that run long unattended. Claude Code CX Codex Cursor +1 1,500installs mantis-reflect official google Extracts insights, failures, and false assumptions from Mantis agent transcripts, appending them to workspace/learnings.jsonl. Claude Code CX Codex Cursor +1 1,500installs mantis-pipeline-adapter official google A consulting skill that walks you through building your own deterministic harness for running Mantis skills. Claude Code CX Codex Cursor +1 1,500installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. Claude Code 711,230installs

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

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor