Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".
Collaborator memory recall โ restores past collaboration history at session start. Pulls relevant context from all 5 folders of 30_Claude (01_Sessions, 02_Learnings, 04_Plans, 05_Research, 06_Designs), with 20_Wiki as secondary. USE PROACTIVELY at session start when user requests non-trivial work, reopens past project, mentions external tech by name, or says Korean "์ด์ ์ / ์์ ์ / ์ฐ๋ฆฌ ~ํ์์" (English: "previously" / "earlier" / "we did this before"). Primary mechanism for continuity โ ensures Claude remembers past decisions, learnings, plans, research, and designs instead of starting from zero. Max 1500 tokens injected per briefing.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)
Generate a structured handoff document AND save it to Obsidian vault. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".