0
Start a new session with /clear when the task truly changes
Use /clear between unrelated tasks so leftover debugging does not bias the next feature.
The problem
Carrying a bloated session into a new feature imports stale assumptions and accelerates context rot.
The hack
When starting genuinely new work, `/clear` and paste a short brief of constraints and key files.
Why it works
Official guidance: new task → new session. /clear gives zero rot and lets you control what carries forward.
Setup
1. Distill what must survive (goal, constraints, file paths, ruled-out approaches). 2. Run `/clear`. 3. Paste the brief as your first message. 4. Put lasting lessons into CLAUDE.md so you do not re-teach them next time.
Prompt
/clearAdditional details
Prefer /compact when you are mid-feature and only need to shed noise.
Discussion
No comments yet. Be the first to say whether this worked for you.