Point at UI bugs instead of describing them to Claude Code

I built a skill that lets you point at UI bugs instead of describing them to Claude Code The fix-check-explain loop was killing my momentum. So we built Bugshot — open source, one command to install. The problem no one talks about Everyone praises AI-assisted coding for how fast you can ship features. What they don't mention is the part where you stare at a broken layout, then walk back to your terminal and try to describe it in words. The sidebar overlaps the main content. I think it's a z-index issue. Also the button on the right side is cut off. Did Claude understand exactly what you meant? Maybe. Probably not. So you clarify. You re-explain. You add more detail. The fix-check-explain loop becomes the slowest part of your workflow — not the code, not the logic, just the communication. BEFORE "The sidebar overlaps the main content area. It looks like a z-index issue. The gap between the header and the card below is too large. Also the button on the right is cut off." AFTER [screensho