recalllisted

# recall — project memory Topical project reference lives in `.claude/reference/<topic>.md`. CLAUDE.md carries only cross-cutting safety and process rules; everything else (env vars, architecture quirks, area pitfalls) is in the reference. This skill is the read/write interface to that store. ## When to invoke **Lookup (most common):** - User says `/recall <topic>` or `/recall <question>`. - User asks "what do we know about X", "any pitfalls with Y", "remind me how Z works". - BEFORE editing in an area you don't already have loaded — any subsystem with its own reference file, plus secrets/env wiring. **Capture:** - User says `/recall save <text>`, "remember this", "save this learning", "add to reference". - A quirk just bit you (or just bit the user) and the lesson belongs in the next session's context. ## Step 1: Look up 1. List the available topics: ``` ls .claude/reference/ ``` 2. Match the user's query to a topic. Starter topics (the project may have grown more — trust the `ls`): | File | Covers | |---|---| | `secrets.md` | Env var names + what they key | | `architecture.md` | System flow, auth, state strategy | | `pitfalls.md` | Accumulated cross-cutting gotchas | | `commands.md` | Build / dev / test scripts | | `tech-stack.md` | Non-default library choices and why | | `deployment.md` | Deploy target, build output, asset paths | 3. Read the matched file(s). If the query spans multiple topics, read each. 4. If nothing in the table