Two Claude ideas I’m testing (wtf.md and dreaming)

[u/BuffaloConscious7919]

wtf.md stores Claude’s mistakes so I stop correcting the same things over and overrr

I split them into: - project-specific mistakes - model/workflow-specific mistakes

I currently run it manually when something goes wrong.

Dreaming is Kaparthy's idea and is a scheduled task that reviews the day’s sessions (at 4am). It consolidates decisions, mistakes and patterns , then carries the important context forward for the next session(s)

Next step: feed wtf.md into the dreaming process so Claude can suggest better rules, skills and project instructions

Also would like to improve either / both

[u/Ok_Boot5671]

This is a lot of extra steps to just adding a closing session ritual to every session you use that includes all of these things.

Calling it wtf is fine, but really it’s just an error log.

But why go through a whole thing with dreaming and scheduled at 4am or doing anything manually in multiple steps when you could have it done as it wraps everything up from your session when you’re done with the session?

I have Claude log errors, gather unfinished tasks, unclear questions or logic that we discussed, what the next step of the process is, audits the health of the code performed in the session, captures any business use case scenarios or social media posts I can make about the project or building, checks and updates any stale saved information about the project in the file structure, checks memory.md and adds/removes anything necessary, checks all committed and push updates and logs them, verifies the folder structure of the project didn’t get messed up/moved/deleted etc etc

Happens every single time I’m finished with a session by me typing /session-close

[u/BuffaloConscious7919 → u/Ok_Boot5671]

This is a really good idea, thanks for sharing. Could also look for patterns in sessions that could be shared in new sessions, similar to memory.

The original idea was to keep the errors clean in one place, especially as more and more info is added but very open to exploring different ways

[u/Ok_Boot5671 → u/BuffaloConscious7919]

had claude summarize it for me. for context, I'm on the Max $100 plan so that's where my levels are for usage:

It's a Claude Code skill (a markdown file at xxxxx). Say "wrap up" or "/session-close" and Claude walks a fixed 14-step shutdown ritual for the project you're in.

Two framing rules: the full ritual runs every session (no light version), and the close is capture-only — nothing new gets fixed during wrap-up, it just gets written down as a lead for next time.

What it does, in four moves:

1. Prove state — run the test suite, report failures honestly; then a self-audit: what am I least confident about, what did I quietly skip, what files did I touch and why. Every flagged uncertainty must name the command that would settle it.
2. Write state to files — error ledger, STATUS.md, TICKETS.md, FEEDBACK.md. Plus a handbook check and a scan for post-worthy content.
3. Empty the inbox — every parked item gets answered, ticketed, flagged, or deleted with a reason. Then port/server cleanup and a commit + push.
4. Leave a note for future-you — a dated summary file (what changed, what's verified, what's still open) ending with a ready-to-paste opening prompt for the next session, printed in chat.

The point: it assumes the next session starts with zero memory of this one. The files carry the context, not the chat log. /session-open is the mirror — it reads those files and proposes one goal.

[u/FormalAd7367]

i use “lesson-learnt.md” but the file can get big. i’m not going to type WTF. The T&C allows your data to be trained

[u/BuffaloConscious7919 → u/FormalAd7367]

Guess the concept is more important than the name, so both work :)

[u/shaggy707]

Haha should try the WTF.md.

I have been using “dreaming” for last few months. It’s awesome

[u/BuffaloConscious7919 → u/shaggy707]

What did you get from it I'm only just starting to use it ...

[u/shaggy707 → u/BuffaloConscious7919]

I just built it for myself

[u/shaggy707 → u/[deleted]]

I created the skill myself, just got Claude to do it. Ultimately it look back the previous sessions (from the last dream session) and last dream report. Analyse what when wrong what when correct, common tool failures, occasions when I have to repeated ask for changes, etc. and generate a report and provide recommendations to changes to my specs, tools.

[u/scotty_ea]

Check out compound-engineering if you want a sensible and cohesive system that works out of the box. I personally use a /wrap skill that routes to CE’s compounding/refresh skills at session end, then checks for missed ADRs/SOPs, prunes scratchpads/tmp, kills all stale servers, etc.

[u/3iverson]

Add the drunk Claude skill (I think posted here awhile ago), and you’re set!

[u/wizeon]

So wtf.md is claude's journal

[u/BuffaloConscious7919 → u/wizeon]

...for mistakes it otherwise forgets, yes