learnedlisted
Install: claude install-skill zahidakhyar/skills
## Step 1 — Scan the conversation
Read back through the full current conversation. Tag each finding:
| Signal | Category | Memory type |
|--------|----------|-------------|
| "no", "wrong", "don't", "stop doing", rejection of suggestion | Correction | `feedback` |
| "yes exactly", "perfect", implicit acceptance of unusual choice | Validation | `feedback` |
| Tool/workflow/style choice revealed | Preference | `user` or `feedback` |
| Decision, constraint, deadline, architecture choice | Project fact | `project` |
| External system, URL, dashboard, doc location | Pointer | `reference` |
**Skip anything that is:**
- Derivable from reading the code or git history
- Code structure — module/entity maps, route lists, file layouts, tech-stack dumps. That belongs to each project's CLAUDE.md; saved here it only goes stale
- Already covered by MEMORY.md or global rules (CLAUDE.md and the files it imports)
- Ephemeral task state
**Asked to remember something on that list** ("remember this module structure", "remember this file layout")? Don't drop it silently. Ask what was non-obvious about it — the gotcha, the decision behind it, why it surprised — and save that instead.
---
## Step 2 — Check existing memories
Read `MEMORY.md` (already in context at session start). For each finding:
- Existing file already covers it → **update that file**
- A correction contradicts an existing memory → **fix or delete that memory** and its index line. A wrong memory is worse than a missing one —