Direct answer
If Claude Code breaks your app, do not keep asking it to try random fixes. Stop, save what is working, copy the exact error, and ask Claude to investigate the likely cause before it changes files. Most beginner bugs are small, reversible, and easier than they feel.
Collect the evidence first
- The exact error message
- What you were trying to do
- What you expected to happen
- What happened instead
- What changed since it last worked
The prompt that helps
Something broke. Do not edit files yet.
First, investigate and explain what is most likely happening.
Here is what I was trying to do:
[describe]
Here is what I expected:
[describe]
Here is what happened instead:
[describe]
Here is the exact error:
[paste error]
Before making changes:
1. Identify the likely cause.
2. Tell me which files you need to inspect.
3. Explain the safest fix.
4. Then ask for permission to apply the fix.
Common beginner mistakes
- Changing five things at once
- Letting Claude repeat the same failed fix
- Not knowing what worked last
- Looking at an old cached page
- Assuming a scary terminal message means the project is dead
Debugging is usually a process problem before it is a technical problem.
When Claude loops
Say it clearly: You already tried that and it did not work. Stop and explain why before trying another fix. If the session keeps looping, ask for a diagnosis first or start a fresh session when the context gets too noisy.
FAQ
Did Claude Code ruin my app?
Probably not. Most breakages are reversible.
Should I paste the whole error?
Yes. Exact wording matters.
Should I let Claude fix everything automatically?
Not at first. Ask it to investigate and explain the likely cause first.