Remember

Yeachan-Heo/oh-my-claudecode/skills/remember

by Yeachan-Heo454bae017356ed1d056182cd929b6eb6cf6143adNo licenseListed Oct 9, 2026Updated Oct 9, 2026

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

Instructions onlyProductivity & Workflow
AI-generated overview

Reviews reusable session knowledge and routes it to project memory, notepad, or durable docs.

What it does
This skill takes findings gathered during a session and classifies each item as a durable project fact, a temporary working note, an operator preference or instruction, or duplicate, stale, or conflicting information. It then proposes the best destination for each item and writes or updates only the appropriate memory surface, such as project memory, notepad priority, notepad working, or docs and AGENTS/CLAUDE files. It reports what was stored, where it was stored, and any duplicates or conflicts found.
When to use it
Use it when the user wants to preserve or organize useful knowledge discovered during a session. It fits situations where durable, reusable knowledge should be promoted out of chat history into the right memory surface, or where duplicates and conflicts across memory stores need to be identified. It is not meant for dumping everything into a single store.
Requirements
No scripts or tools are required; it is instructions only. It needs access to the memory surfaces it writes to (project memory, notepad, and docs or AGENTS/CLAUDE files).

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

Source and attribution

Source:Yeachan-Heo/oh-my-claudecodeinskills/rememberat commit454bae0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal