When Claude Gets Stuck
Claude loops: tries, fails, tries again, fails again. The instinct is to explain more, add more context, push harder. This is wrong.
"If you've explained the same thing three times and Claude still isn't getting it,
more explaining won't help. Change something."
Signs You're Stuck
Recognize these patterns:
- Same error repeated after "fixing" it
- Twenty minutes explaining why something is wrong
- Confident but completely wrong implementation
- Claude apologizing and making the same mistake
What Actually Works
Clear the Conversation
Use /clear for a fresh start. Often the accumulated context is the problem.
Start over with just the essential information.
Simplify the Task
Break into smaller pieces. If "build the auth system" isn't working, try "just validate the email format" first.
Show Instead of Tell
Write a minimal example yourself. "Make it work like this" with actual code beats any amount of description.
Reframe the Problem
Different words trigger different approaches. "State machine" vs "handle transitions" might get completely different results.
The Meta-Skill
The real skill is recognizing loops early. Three explanations = time to change. Don't wait until you're frustrated. The moment you feel like you're repeating yourself, stop and try a different approach.
More explaining won't help. Change the approach entirely: different framing, smaller scope, fresh context, or just write the code yourself and ask Claude to extend it.
Key Takeaways
- Three explanations = time to change approach
/clearoften fixes accumulated confusion- Break big tasks into smaller pieces
- Show examples instead of describing them
- Reframe problems with different terminology