home / skills / yeachan-heo / oh-my-claudecode / note

note skill

safe

This skill saves important context to a persistent notepad, ensuring notes survive conversation compaction and are easily retrievable.

npx playbooks add skill yeachan-heo/oh-my-claudecode --skill note

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.9 KB

---
name: note
description: Save notes to notepad.md for compaction resilience
---

# Note Skill

Save important context to `.omc/notepad.md` that survives conversation compaction.

## Usage

| 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) |

## Sections

### Priority Context (500 char limit)
- **Always** injected on session start
- Use for critical facts: "Project uses pnpm", "API in src/api/client.ts"
- Keep it SHORT - this eats into your context budget

### Working Memory
- Timestamped session notes
- Auto-pruned after 7 days
- Good for: debugging breadcrumbs, temporary findings

### MANUAL
- Never auto-pruned
- User-controlled permanent notes
- Good for: team contacts, deployment info

## Examples

```
/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
```

## Behavior

1. Creates `.omc/notepad.md` if it doesn't exist
2. Parses the argument to determine section
3. Appends content with timestamp (for Working Memory)
4. Warns if Priority Context exceeds 500 chars
5. Confirms what was saved

## Integration

Notepad content is automatically loaded on session start:
- Priority Context: ALWAYS loaded
- Working Memory: Loaded if recent entries exist

This helps survive conversation compaction without losing critical context.

Overview

This skill saves important context to a persistent in-repo notepad file so key facts survive conversation compaction. It provides simple commands to append, view, prune, and clear notes across three durable sections: Priority, Working Memory, and MANUAL. Use it to keep critical project facts, debugging breadcrumbs, and permanent team info accessible across agent sessions.

How this skill works

The skill creates and updates a .omc/notepad.md file and parses command flags to determine where to store content. It timestamps Working Memory entries, enforces a 500-character limit for Priority Context, and loads Priority and recent Working Memory entries automatically at session start. Commands allow showing contents, pruning older working entries, and clearing temporary notes while preserving priority and MANUAL entries.

When to use it

Save short, critical facts that must always load at session start (Priority).
Record session-specific findings, errors, or debugging steps (Working Memory).
Store permanent references like team contacts, secrets locations, or deployment notes (MANUAL).
Quickly capture context before a session compaction or agent handoff.
Inspect or prune accumulated ephemeral notes to avoid bloat.

Best practices

Keep Priority Context concise (under 500 characters) to avoid eating context budget.
Use timestamps and short sentences in Working Memory for readable debugging trails.
Reserve MANUAL for long-lived entries that should never be auto-pruned.
Prune Working Memory regularly (older than 7 days) to reduce noise.
Confirm saved content with the --show command after critical updates.

Example use cases

Add a quick note about a reproducible bug encountered during testing.
Mark the project package manager or important config paths in Priority so agents always know them.
Store an internal contact email or deployment URL in MANUAL for future lookups.
Log step-by-step troubleshooting notes across a debugging session.
Clear ephemeral notes after a release while keeping permanent documentation intact.

FAQ

How do I add a permanent note?

Use the --manual flag to append content to the MANUAL section, which is never auto-pruned.

What happens if Priority exceeds 500 characters?

The skill warns you that the Priority Context is too long so you can shorten it and avoid context budget issues.

Can I view the current notepad?

Yes. Use the --show flag to display the full notepad contents.