remember

Topics in the source

• /si:remember — Save Knowledge Explicitly
• Usage
• When to Use
• Workflow
• Step 1: Parse the knowledge
• Step 2: Check for duplicates
• Step 3: Write to MEMORY.md
• Step 4: Suggest promotion

Writes an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically. | 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" | Extract from the user's input: What: The concrete fact or pattern Why it matters: Context (if provided) Scope: Project-specific or global? If a similar entry exists: Show it to the user Ask: "Update the existing entry or add a new one?" Append to the end of MEMORY.md: Keep entries concise — one line when possible. Auto-memory entries don't need timestamps, IDs, or metadata. They're notes, not database records. If MEMORY.md is over 180 lines, warn the user: If the knowledge sounds like a rule (imperative, always/never, convention): Temporary context: Use session memory or jus

This is an excerpt. Refer to the complete source and its current requirements.