UI Thrashing: The Reset Protocol That Actually Works
You’re coding a UI. Maybe a whole website — and websites are never, ever consistent on the first pass, you know how it goes.
So you start juggling around. “Hey, the text should be bigger.” Then, “wait, no — actually it should be higher.” Then the space. Then the margin. Then, “oh shit, no, the layout should not be boxed.” One correction triggers the next, and the next, and you’re deep in a loop of micro-tweaks that never actually ends.
I see this pattern every single day. And whenever it hits, stop immediately and run this protocol instead of negotiating your way through it. No thinking required. It’s a no-brainer.
The protocol
- Kill the session. Don’t keep arguing pixel by pixel inside the one that’s already broken. Open a brand new Claude Code session.
- Max out the thinking effort. Push it to extra high before you send anything.
- Resend everything. All the context again, plus screenshots — the real, current state of the UI, not a description of what’s wrong with it.
- Combine it with Just Do It, if you’ve got it running.
- Let it plan and execute. No extra rounds of clarifying questions, even if it wants to ask them. It plans. Then it follows the plan. Period.
That’s the whole thing.
Why it’s a no-brainer
The micro-tweak loop happens because you’re negotiating with a model one detail at a time, inside a session that’s already carrying every wrong guess it made to get there. You fix the text size, it overcorrects the spacing. You fix the spacing, the layout goes sideways. Neither of you is looking at the whole picture anymore — you’re both just reacting to the last thing that was said.
A fresh session, maxed-out thinking, and the full picture in front of it from the start doesn’t negotiate. It plans.
Has it worked every time I’ve run it? 100%. Or — at least 100%, in every case I’ve hit so far.
Next time you catch yourself typing “wait, no, actually—” for the fifth time in the same session, don’t type it a sixth. Close it. Start over. Run the protocol.
I love feedback.
Did this help? One tap — that's it.
Thanks 🙏
Want to add anything — or get in touch? Totally optional.
Got it — thank you. 🙏
Keep reading
Claude Chat, Claude Co-Work, or Claude Code: How to Know Which One You Actually Need
The three tiers of working with AI — Claude chat, Claude co-work, and Claude Code — and the exact signal that tells you when it's time to move up a level.
The Skills I Actually Kept: My Claude Code Skills, and What I Use vs Build
The Claude Code skills I actually kept — article drafting, a full deploy pipeline, design-system contracts, self-testing — and the one rule I use to decide when to reuse a pre-built skill versus write my own: who's going to maintain it in six months.
When GSD Became the Bottleneck, I Built Something Lighter
GSD asks a lot up front and forgets what it asked — great for serious multi-phase builds, terrible for rocket-ship mode. Here's the lightweight way of working I reach for instead: high effort, a two-item plan, round-based questions, big-bang execution, and two skills that auto-run the UAT.