rememberlisted

# /remember - Save Session to Memory Summarize the current work session and save it to persistent memory for future context. ## Instructions When the user invokes `/remember`, you should: ### 1. Check for Activity Log First, check if there's an activity log from this session: ```bash REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "$PWD") ACTIVITY_FILE="$REPO_ROOT/.claude-memory/activity.log" if [ -f "$ACTIVITY_FILE" ]; then cat "$ACTIVITY_FILE" fi ``` ### 2. Analyze the Session Review what was accomplished in this conversation: - What files were read, created, or modified? - What was the main goal or task? - What key decisions were made? - Were there any important patterns or learnings? ### 2.5. Compression Guidelines When writing summaries, facts, or knowledge entries, follow these rules to maximize information density: - **Resolve pronouns to concrete entities**: Write "JWT middleware validates tokens" not "it validates them" - **Use absolute file paths**: Write "src/auth/middleware.ts" not "this file" or "the auth file" - **Write dense, self-contained summaries**: Each memory entry should be understandable without the original conversation context - **Avoid filler phrases**: Do not use "I think", "basically", "sort of", "actually" — state facts directly - **Use ISO dates**: Write "2026-02-11" not "today" or "yesterday" — temporal references decay quickly The system automatically compresses text at write time (normalizing dates, stripping fill