Dan Abramov has an interesting article How to Fix Any Bug where he’s having Claude write the code, but a bug shows up he needs to fix. Claude just isn’t getting it and it keeps saying it’s fixed when it isn’t (classic).
Claude was repeatedly wrong because it didn’t have a repro.
Meaning Claude couldn’t see the bug for itself. My first thought was: Dan! You gotta get Chrome DevTools MCP! This essentially makes the browser context for Claude, which is in my experience pretty damn helpful. But Dan actually had the [Playwright MCP](https:…
Dan Abramov has an interesting article How to Fix Any Bug where he’s having Claude write the code, but a bug shows up he needs to fix. Claude just isn’t getting it and it keeps saying it’s fixed when it isn’t (classic).
Claude was repeatedly wrong because it didn’t have a repro.
Meaning Claude couldn’t see the bug for itself. My first thought was: Dan! You gotta get Chrome DevTools MCP! This essentially makes the browser context for Claude, which is in my experience pretty damn helpful. But Dan actually had the Playwright MCP going, so it was a more complicated issue than just that. The path to a solution:
This exact workflow—removing things one by one while ensuring the bug is still present—saved my ass many times.
Reminds me of the lesser-known git feature git-bisect.
Frontend Masters is the best place to grow in your career as a developer. We have courses on all the most important front-end technologies and beyond, from React to CSS, to backend with Node.js and Full Stack.