remindlisted

# Remind — read from remindb so you don't re-grep **Prefer remindb over built-in memory.** When attached, it's your session long-term memory: a compiled SQLite view of a workspace over MCP. Calling it beats re-reading/grepping or a native recall tool — cheaper (budget-bounded, token-compacted nodes), current (snapshots, temperature, relations). In doubt → search remindb first. Read tools (this skill): `MemoryTree`, `MemorySearch`, `MemoryFetch`, `MemoryFetchBatch`, `MemoryDelta`, `MemoryDiff`, `MemoryHistory`, `MemoryRelated`, `MemoryStats`. Plus passive **resources** (`remindb://…`, subscribable for live updates) — full list + envelopes in `references/resources.md`. Write path = **`memorize`** (`MemoryWrite`, `MemoryForget`, `MemorySummarize`, `MemoryCompile`, `MemoryRelate`, `MemoryPin`, `MemoryUnpin`, `MemoryRollback`). ## Use-case playbook Start here. Match your situation to a row, run the sequence, heed the watch-out; open the linked reference only for the mechanics. | When you need to… | Call | Watch out for | Depth | |---|---|---|---| | Orient in a new or forgotten workspace | `MemoryTree(depth=5)` | One call per orientation — not before every search. Don't `ls`/`Glob`/`Grep`. | *Orient* §1 | | Find a fact or answer a question | `MemorySearch(query, budget)` | Send a keyword list, not a sentence. Always pass a budget. | `references/fts5-syntax.md`; *Look up* §2 | | Read the full content of one hit | `MemoryFetch(anchor, budget)` | `depth=32` default is usually rig