When something looks wrong in the browser, don't try to describe it — just show Claude Code.
Claude Code is multimodal, so you can drag and drop a screenshot directly into the conversation:
"Here's a screenshot of the broken sidebar. Can you fix the overlap?"
Claude will inspect the image, identify the visual issue, and look at the relevant template or CSS to propose a fix. This works for layout problems, styling bugs, broken dark mode, or components that don't render correctly.
You can also reference an image file on disk:
# Take a screenshot, then point Claude to it
"Look at /tmp/screenshot.png — the card grid isn't responsive on mobile"
For best results, crop the screenshot to the relevant area and combine it with a file reference:
"Here's a screenshot. The template is in resources/views/dashboard.blade.php"
You can even paste two screenshots for before/after comparisons — Claude will spot the difference and trace it back to the code.
The key principle: show Claude the bug, don't describe it. A screenshot removes all ambiguity about what you're seeing.
Log in to leave a comment.
Hand Claude your heap snapshots or server code and ask it to trace memory leaks — it spots missing event listener cleanup, unbounded caches, and stream lifecycle bugs that are easy to miss in code review.
Ask Claude to audit your UI components for WCAG accessibility issues — it catches semantic problems, missing ARIA attributes, and keyboard navigation gaps that automated tools miss.
The --debug flag enables verbose logging for Claude Code, and an optional category filter like "api,mcp" lets you narrow output to exactly the subsystem you need to investigate.