dream
Skill2 starsChanged 5 months agoMITView on GitHub
Memory consolidation. Dedupe and compress .claude/memory/ topic files, absolutize relative dates, archive stale instincts and processed checkpoints, and hard-enforce the 200-line MEMORY.md cap. Produces a reviewable proposal, never a silent overwrite.
43 other projects use a version of this.
Adopted by
Most recently taken up by
- Jewgah/claude-code-skillstheir own version, first seen Nov 16, 2026
- borkweb/skillstheir own version, first seen Nov 15, 2026
- srinator22/agent-kerneltheir own version, first seen Nov 15, 2026
- fjwood69/moritheir own version, first seen Nov 10, 2026
- srinator22/New-Projecttheir own version, first seen Nov 8, 2026
- Melvynx/ai-maxxing-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ingest, resume and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 4 projects that use this
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 3 projects that use this
MicrosoftSkillinit
Also in 4 projects that use this
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 3 projects that use this
SentrySkilldeslop
Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.
Also in 3 projects that use this
AnthropicSkillstart
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
Also in 3 projects that use this
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- Noizefield/audio-plugin-coder★ 334same name
- grandamenium/dream-skill★ 136same name
- sneg55/agent-starter★ 76same name
- oprogramadorreal/optimus-claude★ 75same name
- tranhieutt/software_development_department★ 71same name
- Melvynx/ai-maxxing-skills★ 46same name
- maxvaega/awesome-skills★ 40same name
- seldonframe/seldonframe★ 40same name
- hyperb1iss/hyperskills★ 36same name
- fjwood69/mori★ 32same name
33 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- animation-disciplineSkill
- api-versioningSkill
- autopilotSkill
- browser-e2eSkill
- characterizeSkill
- clarifySkill
- codemodSkill
- constitution-compactSkill
- constitutionSkill
- context-budgetSkill
- creative-webSkill
- db-migrationSkill
- debugSkill
- detect-stackSkill
- dispatch-criteriaSkill
- experimentSkill
- fastapiSkill
- flag-cleanupSkill
- flag-rolloutSkill
- flask-realtimeSkill
- framework-detectorSkill
- front-end-designSkill
- grill-meSkill
- handoffSkill
- image-generationSkill
- implementSkill
- initiativeSkill
- instinctSkill
- loopSkill
- nextjsSkill
- observabilitySkill
- okr-alignSkill
- parallel-swarmSkill
- pivotSkill
- planSkill
- pr-bodySkill
- prime-disciplineSkill
- prod-observabilitySkill
- react-nodeSkill
- react-viteSkill
- release-trainSkill
- researchSkill
- reviewSkill
- security-guardSkill
- self-healSkill
- shipSkill
- skill-creatorSkill
- specifySkill
- tailwind-disciplineSkill
- tasksSkill
- tdd-loopSkill
- token-budgetSkill
- typographySkill
- verify-loopSkill
- verifySkill
- wip-checkpointSkill
- <kebab-case-skill-name>Skill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 42 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 75
Write the consolidated result as a proposal under .claude/memory.proposed/, not directly over .claude/memory/.
“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dream — memory consolidation
Long autonomous runs accrete memory: duplicate observations, relative dates that
rot ("yesterday"), instinct files that no longer fire, checkpoints already
folded in. Left alone, MEMORY.md bloats past the context budget and the signal
drowns. Dreaming is the periodic GC that keeps memory dense and current.
Trigger contract (with auto-dream-check.sh)
The Stop hook .claude/hooks/auto-dream-check.sh decides when; this skill is
what runs. The hook fires a dream only when both:
- more than 24h have passed since the last dream, AND
- at least 5 sessions have accumulated since then.
State lives in .claude/memory/.cache/.dream-state.json; a lock at
.claude/memory/.cache/.dream.lock prevents concurrent dreams. If an
un-reviewed proposal already exists in .claude/memory.proposed/, do nothing —
the operator must clear it via /dream-review first, or a second dream would
silently overwrite the first's proposal and drop the human-review gate.
What a dream does
- Gather — read
.claude/memory/topic files, every checkpoint under.claude/memory/.cache/checkpoints/written since the last dream, subagent handoff archives under.claude/memory/handoffs/(decisions_made, rejected_hypotheses, incidents — gap-audit G33), and the digest log.claude/hooks/.log/subagent.jsonlfor agents that skipped the handoff. - Dedupe + compress — merge repeated observations into a single entry; drop anything already captured in a topic file. Prefer the denser phrasing.
- Absolutize dates — rewrite relative dates ("yesterday", "last week") to absolute ISO dates, so the memory stays interpretable after time passes.
- Archive stale instincts — move instinct files that haven't fired recently
from the active set into
.claude/memory/.cache/archive/YYYY-MM/. 4a. Extract fresh instincts — runbash .claude/scripts/instinct-extract.sh --force(gap-audit G25: this is the pipeline's middle stage; without it observations accumulate unconsumed). 4b. Promote — runbash .claude/scripts/instinct-promote.sh auto(project → global at the 2-project threshold, gap-audit G26). - Detect contradictions — group ADR files under
.claude/memory/decisions/by theirsubsystem:frontmatter field. For each subsystem group with ≥2 ADRs, compare theirdecision:fields; flag any pair whose decisions conflict (e.g., "use postgres" vs "use sqlite"). Write flagged pairs to.claude/memory.proposed/conflicts.md(one table row per conflict: subsystem, ADR-A path, ADR-B path, conflict summary). If no conflicts found, omit the file. Do not auto-resolve — surface for human review. - Enforce the cap — run
bash .claude/scripts/memory-gc.sh enforceto holdMEMORY.mdat ≤200 lines. This is the hard backstop: the cap is enforced by the script, not by this prompt, so a crashed/hallucinating dream cannot leaveMEMORY.mdbloated (Round 4 caught exactly that silent failure). - Archive checkpoints — move processed checkpoints to
.claude/memory/.cache/archive/YYYY-MM/. - Promote + decay (mechanical) — run
bash .claude/scripts/memory-promote.shandbash .claude/scripts/learn-from-success.sh(gap-audit G29: these previously ran only via the optionally-installed desktop cron, so a fresh harness copy silently never promoted/decayed memory or learned routing). - Roll up horizons — run
bash .claude/scripts/memory-rollup.sh auto. This consolidates the week's events into.claude/memory/rollups/YYYY-Www.mdand, at period boundaries, weeklies → monthly → quarterly (each ≤100 lines). Multi-year recall depends on this: day-scale memory (in-flight briefs, observations) ages out within days, but the rollup chain preserves it at log-scale cost. The factual skeleton is deterministic (git + task ledger); you may enrich the narrative sections of the current week's file, but never alter past-period rollups.
Output
Write the consolidated result as a proposal under .claude/memory.proposed/,
not directly over .claude/memory/. The operator reviews and applies it via
/dream-review. Never overwrite live memory in place — the review gate is the
whole point.
Done means
- A proposal exists under
.claude/memory.proposed/(or the dream no-op'd because one was already pending). memory-gc.sh enforcehas run andMEMORY.mdis ≤200 lines.- Relative dates in the proposal are absolutized; processed checkpoints archived.
.claude/memory.proposed/conflicts.mdwritten if any contradicting ADRs found (subsystem-grouped comparison); absent means no conflicts detected.memory-rollup.sh autohas run — the current week's rollup exists under.claude/memory/rollups/.
References
- Trigger:
.claude/hooks/auto-dream-check.sh - Cap enforcement:
.claude/scripts/memory-gc.sh - Backstop schedule:
.claude/routines/dream-cron.yml - Review gate:
/dream-review
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

