2 min read476 wordseng
Claude Code’s quality improved when it was forced to self-verify UI changes in Chrome DevTools MCP at mobile, tablet, and desktop widths, inspect screenshots for issues, fix them, and recheck—cutting human QA and boosting first-pass quality about 3x, though at the cost of more to
- • The author says Claude Code quality improved by having Claude verify its own work before marking tasks done.
- • The workflow uses Chrome DevTools MCP to open the changed page, inspect screenshots at mobile, tablet, and desktop sizes, and click through the UI flow.
- • Claude is instructed to look at the screenshots itself and identify what is wrong, then fix issues and re-screenshot to confirm the fix.
- • The author argues that passing tests do not guarantee the feature works correctly in the browser, especially for visual and layout problems.
- • The approach increased first-pass quality by about 3x and reduced the need for the author to act as QA.
- • The main tradeoffs are higher token usage, longer runtime, and limited coverage of device-specific or non-visual bugs.
- • The author suggests using the self-verification loop mainly for changes that actually affect the UI rather than for every task.