← ClaudeAtlas

dreamlisted

Consolidate the project's auto memory in place (merge, correct, prune, re-index), then offer to clean up .turbo/. Use when the user asks to "dream", "tidy memory", or "clean up stale notes".
tobihagemann/turbo · ★ 420 · Code & Development · score 89
Install: claude install-skill tobihagemann/turbo
# Dream Consolidate this project's auto memory, then clear out what `.turbo/` no longer needs. Text passed with the invocation steers the memory pass: what to look for and how to organize the notes. Every note is still read, and Step 3's conditions for deleting a note hold regardless. ## Step 1: Read the Memory Use the auto-memory directory the system prompt names. When it names none, an effective `autoMemoryDirectory` setting gives the location. Otherwise the directory is `<Claude config home>/projects/<encoded project root>/memory/`. The config home is `CLAUDE_CONFIG_DIR` when set and `~/.claude` otherwise. The key replaces every character outside `A-Za-z0-9` with `-`, and long keys may be truncated and hashed. List the directory, then read `MEMORY.md` and every note with the Read tool. When the directory does not exist or holds no notes, say so and continue with Step 4. ## Step 2: Gather Evidence Judge each statement in every note, and in every entry `MEMORY.md` holds in full rather than as a pointer to a note, by its kind: - **A claim the project can confirm or refute**, such as a path, a symbol, a flag, or a command: check it by searching the current code, reading a file only where the match does not settle the claim. A claim about how a tool behaves at runtime is unverifiable unless reading settles it. - **A decision or preference of the user**: the code never contradicts it. Only a note modified more recently, or the user reversing it in a session transcript, d