Know Me

2. Save (To Memory Topic Files)

~/.claude/projects/<project-path>/memory/
├── MEMORY.md              ← Summary + links (auto-loaded, 200-line limit)
├── user-preferences.md    ← How the user likes to work
├── project-context.md     ← What they're building and why
├── tech-stack.md          ← Tools, frameworks, versions they use
├── communication-style.md ← How they want Claude to communicate
└── corrections.md         ← Things Claude got wrong — never repeat

Where to save:

• MEMORY.md: One-line summaries with pointers to topic files
• Topic files: Detailed entries with date and context

3. Recall (Before Responding)

Before making suggestions or writing code:

1. Check if MEMORY.md has relevant user preferences
2. Read the relevant topic file if the task touches a known preference area
3. Apply stored knowledge — don't ask questions you already know the answer to

4. Apply (Personalize Everything)

• Use their preferred tools/frameworks without asking
• Match their communication style (concise vs detailed, casual vs formal)
• Reference their project context when making architectural suggestions
• Avoid patterns they've previously rejected

Auto-Activation Triggers

This skill activates when you detect:

• User shares personal information, preferences, or opinions
• User corrects Claude on a choice or assumption
• User describes their project, team, or goals
• User expresses frustration about Claude's behavior
• A preference conflict with stored memory (update needed)

What NOT to Save

• Temporary task context (what file they're editing right now)
• Information that belongs in code/docs, not memory
• Sensitive data (passwords, API keys, financial details)
• Speculative conclusions from a single interaction
• Anything the user asks you to forget

Handling Corrections

When the user corrects you on something from memory:

1. Immediately acknowledge the correction
2. Update or remove the incorrect memory entry right now
3. Save the correction to corrections.md so the mistake never repeats
4. Continue with the corrected information

Privacy Rules

1. Never save secrets, credentials, or sensitive personal data
2. If the user says "forget X" or "don't remember that" — delete it immediately
3. Only save information relevant to working together effectively
4. Don't reference stored personal info unnecessarily — use it naturally
5. If unsure whether something is worth saving, err toward saving it (except sensitive data)

Quick Save Template

When saving a new memory entry to a topic file:

### [Category]: [What you learned]
- **Observed:** [date or "this session"]
- **Context:** [How you learned this]
- **Detail:** [The actual preference/info]