yeachan-heo/oh-my-claudecode

remember

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

First seen Apr 3, 2026

Installation

$ npx skills add yeachan-heo/oh-my-claudecode --skill remember

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from yeachan-heo/oh-my-claudecode · top by installs.

npx skills add yeachan-heo/oh-my-claudecode

Browse all from yeachan-heo/oh-my-claudecode

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 39.1K
License LICENSE
Default branch main
Open issues 2
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,432 B
  • docs SUMMARY.md 117 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 440 installs

SKILL.md

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

  1. Propose the best destination for each item.
  2. Write or update only the appropriate memory surface.
  3. 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