Wtf.md and Dreaming: Two Claude Workflow Concepts Worth Exploring

A r/ClaudeAI user describes two workflow concepts they've built to reduce mistakes and consolidate session knowledge: Wtf.md and Dreaming. Both are implemented as simple files and scheduled tasks, offering a practical pattern for anyone running long-term Claude sessions.
Wtf.md: Logging Claude's Mistakes
Wtf.md is a dedicated file for storing everything Claude gets wrong. The idea is to separate these errors into two categories:
- Project-specific: Mistakes tied to your particular codebase, config, or domain.
- Model-specific: Errors that stem from Claude itself — recurring patterns of misunderstanding or hallucination.
The user currently implements this as a skill that they manually trigger whenever they spot an error. This creates a growing reference that can be used to preempt issues in future sessions.
Dreaming: Nightly Consolidation
Dreaming is based on Andrej Karpathy's concept of consolidating information from all sessions at the end of each day. The goal is to merge insights, decisions, and lessons learned into a single reference that Claude can leverage next day.
In this setup, Dreaming runs as a scheduled task at 4 AM daily. Because it runs while the machine is idle, it doesn't interrupt work and has the full context of the previous day's sessions.
Why This Matters
These patterns address two common pain points with AI coding agents:
- Memory limits: Sessions are isolated, so context from yesterday is lost unless explicitly carried over.
- Repetition: Without a feedback loop, Claude will repeat the same mistakes across sessions.
By logging errors and consolidating knowledge, you create a continuous improvement loop.
Who It's For
Developers who use Claude (or similar agents) for substantial projects and want to minimize repeated mistakes and maintain context across sessions.
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude User Shares 'Don't Manage My Feelings' Prompt for Direct Technical Feedback
A Claude user recommends setting a specific prompt in user preferences to reduce validation preamble and get more direct technical feedback. The prompt tells Claude to skip diplomatic phrasing and provide straightforward criticism on technical and creative work.

Most People Use Claude at 5% of Its Capacity – Here's How to Fix It
After 60+ hours testing prompts on Claude Opus 4.7, a user shares a 5-step recipe: assign role, load specific context, set constraints, define output format, add forcing function.

Short system prompts improve Claude's adherence and reduce token waste
A developer discovered that replacing a 3,847-word system prompt with several tiny focused prompts (total ~200 words) eliminated Claude's drift and forgotten instructions.

Running MiniMax M2.7 Q8_0 128K on 2x3090 with CPU Offloading – Real-World Benchmarks and Config
A user successfully runs MiniMax M2.7 at Q8_0 with 128K context on two RTX 3090s plus DDR4 RAM, achieving ~50 tps prompt processing and ~10 tps token generation, and shares their llama-server flags.