short-term-memory

# Short-term Memory Skill **Purpose:** Maintain working context across sessions and compactions via `current-context.md` --- ## Problem & Solution **After context compaction, you lose:** - Recent momentum, nuanced decisions, next logical step, mental state, decision timestamps **Solution:** A concise living memory file = your sticky note between sessions --- ## Mandatory Workflow ### READ -> WORK -> UPDATE -> CHECK -> SEND **Before EVERY response:** Read `current-context.md` **After EVERY response:** Update `current-context.md` with timestamp ``` 1. Read current-context.md 2. Do your work 3. Update current-context.md (add timestamp YYYYMMDD-HHMMSS) 4. Check line count (>200? archive old entries) 5. Send response ``` --- ## Critical Rules ### 1. The file lives in the project The file is `PROJECT_DIRECTORY/current-context.md`. It lives in the project directory, not in `~/.claude/`. ### 2. Timestamp Format **Use:** `YYYYMMDD-HHMMSS` prefix for all entries. Always get the timestamp from the system clock — never invent one. ```markdown ✅ 20251230-143022 : shipping-mapping.md created (relay cascade) ⏸️ 20251230-150133 pending : API vs FTP decision (contact vendor Jan) ``` ### 3. Summaries not Novels **Keep entries short** ❌ BAD: Created shipping-mapping.md with complete cascade detection for relay points including WCMultiShipping priority, Boxtal fallback... ✅ GOOD: `✅ 20251230-143022 : shipping-mapping.md (relay: WCMultiShipping->Boxtal->carrier). Fixed one le...