From oh-my-claudecode
Saves notes to .omc/notepad.md in priority, working memory, or manual sections via /note commands to persist context across compactions. Includes show, prune, clear options.
How this skill is triggered — by the user, by Claude, or both
Slash command
/oh-my-claudecode:noteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Save important context to `.omc/notepad.md` that survives conversation compaction.
Save important context to .omc/notepad.md that survives conversation compaction.
| Command | Action |
|---|---|
/oh-my-claudecode:note <content> | Add to Working Memory with timestamp |
/oh-my-claudecode:note --priority <content> | Add to Priority Context (always loaded) |
/oh-my-claudecode:note --manual <content> | Add to MANUAL section (never pruned) |
/oh-my-claudecode:note --show | Display current notepad contents |
/oh-my-claudecode:note --prune | Remove entries older than 7 days |
/oh-my-claudecode:note --clear | Clear Working Memory (keep Priority + MANUAL) |
/oh-my-claudecode:note Found auth bug in UserContext - missing useEffect dependency
/oh-my-claudecode:note --priority Project uses TypeScript strict mode, all files in src/
/oh-my-claudecode:note --manual Contact: [email protected] for backend questions
/oh-my-claudecode:note --show
/oh-my-claudecode:note --prune
.omc/notepad.md if it doesn't existNotepad content is automatically loaded on session start:
This helps survive conversation compaction without losing critical context.
npx claudepluginhub letrandat/oh-my-claudecode13plugins reuse this skill
First indexed Jul 8, 2026
Showing the 6 earliest of 13 plugins
Stores, recalls, queries, and audits durable project knowledge as atomic facts or compound documents, plus a working notepad that survives conversation compaction. File-backed under `.vibekit/`, cross-runtime portable.
Writes an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.