remember

# /si:remember — Save Knowledge Explicitly Writes an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically. ## Usage ``` /si:remember <what to remember> /si:remember "This project's CI requires Node 20 LTS — v22 breaks the build" /si:remember "The /api/auth endpoint uses a custom JWT library, not passport" /si:remember "Reza prefers explicit error handling over try-catch-all patterns" ``` ## When to Use | Situation | Example | |-----------|---------| | Hard-won debugging insight | "CORS errors on /api/upload are caused by the CDN, not the backend" | | Project convention not in CLAUDE.md | "We use barrel exports in src/components/" | | Tool-specific gotcha | "Jest needs `--forceExit` flag or it hangs on DB tests" | | Architecture decision | "We chose Drizzle over Prisma for type-safe SQL" | | Preference you want Claude to learn | "Don't add comments explaining obvious code" | ## Workflow ### Step 1: Parse the knowledge Extract from the user's input: - **What**: The concrete fact or pattern - **Why it matters**: Context (if provided) - **Scope**: Project-specific or global? ### Step 2: Check for duplicates ```bash MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory" grep -ni "<keywords>" "$MEMORY_DIR/MEMORY.md" 2>/dev/null ``` If a similar entry exists: - Show it to the user - Ask: "Update the existing entry or add a new one?" ### Step 3: Write to MEMORY.md A...