learn

# /learn — Behavioral Correction When the user corrects a mistake, diagnose which behavioral surface caused it and apply one minimal, targeted fix. Interactive — runs in the foreground with the user. ## When to Use - User corrects behavior ("no, don't do that", "you should always...") or a mistake must never recur - A pattern of repeated errors suggests a missing rule ## Flow 1. **Diagnose before changing anything.** Read the conversation, recent changes, and relevant config to establish what went wrong and why — missing rule, stale convention, or wrong default. Name the responsible surface. If the diagnosis is ambiguous, report what you verified and ask — never guess a surface. 2. **Propose the minimal fix in plan mode:** exactly which file changes, the content, and the rationale. One learning = one surface = one change; never batch. 3. **Apply after approval**, then confirm what was learned. 4. **Persist to memory:** write a feedback memory (format below) and add it to the `.claude/memory/MEMORY.md` index so the learning survives across sessions. ## Writable Surfaces | Surface | Path | Controls | |---------|------|----------| | Project conventions | `CLAUDE.md` | Commands, gotchas, coding rules | | Agent identity | `AGENTS.md` | Role, preferences, team behavior | | Personality | `SOUL.md` / `IDENTITY.md` | Tone, communication style | | Global rules | `~/.claude/rules/*.md` | Cross-project behavior | | Native memory | `.claude/memory/` | Feedback, user prefs, project c...