Analyze our conversation and extract non-obvious learnings, then save them to the appropriate auto memory files.
The motto is: "How can we do this better next time?"
What counts as a learning (non-obvious discoveries only):
- •Hidden relationships between files or modules
- •Execution paths that differ from how code appears
- •Commands we tried and eventually got working
- •Non-obvious configuration, env vars, or flags
- •Debugging breakthroughs when error messages were misleading
- •API/tool quirks and workarounds
- •Build/test commands not in README
- •Architectural decisions and constraints
- •Files that must change together
What NOT to include:
- •Obvious facts from documentation
- •Standard language/framework behavior
- •Things already in CLAUDE.md or MEMORY.md
Process:
- •Review the full conversation for non-obvious discoveries
- •Read the current MEMORY.md to avoid duplicating existing knowledge
- •Categorize learnings by topic
- •For each topic, either update an existing memory file or create a new one in the auto memory directory
- •Update MEMORY.md with a brief summary and links to topic files
- •Present the learnings to the user for review before saving
Keep MEMORY.md concise (under 200 lines). Use separate topic files for detailed notes.