2 min read
Bug Report
When something breaks, your instinct is to say “it’s not working.” That’s natural, but it makes Claude guess. A structured bug report gets you a fix in one prompt instead of five. Copy this template, fill it in, and paste it into Claude Code.
The Template
## Bug Report
**What I did:**
[What were you doing when the bug appeared?]
**What I expected:**
[What should have happened?]
**What happened instead:**
[What actually happened? Be specific.]
**Error message (if any):**
```
[Paste the full error message here]
```
**When it started:**
[Did this just start? After which change? Was it working before?]
**Platform/Browser:**
[e.g., Safari on Mac, Chrome on mobile, iPhone 15 simulator]Example — Filled In
## Bug Report
**What I did:**
I clicked the "Save" button on the notes screen after typing a new note.
**What I expected:**
The note should save and appear in the notes list.
**What happened instead:**
The page refreshed and the note was gone. Nothing saved. The notes list still shows the same entries as before.
**Error message (if any):**
```
No error in the terminal.
```
**When it started:**
It was working fine yesterday. This started after I added the dark mode toggle in the last session.
**Platform/Browser:**
Safari on Mac (macOS Sequoia), testing locally at localhost:4321Tips
- The more specific your report, the faster Claude fixes it.
- Always paste the full error message — don’t summarize it.
- “It was working before I added [feature]” is extremely helpful context.
- If you can, mention which file or screen the bug is on.
- Screenshots help too — paste them directly into Claude Code.