“Can you make this button smaller?” is a pretty simple request when you can point at the button. In a coding chat, it turns into “the one under the heading, on mobile, next to the other button.” I built a little Chrome extension called VibeQuill around that problem. The first version just let me click things on a page, draw on it, and leave notes. Then I built a local connector so those notes could go straight to a coding agent with the selected element and the page context attached. Building it solo, I spent a surprising amount of time on what happens when the connection drops. I wanted the note you were typing to still be there when the connection came back, and I didn’t want reconnecting to send the same edit twice. That part would be invisible in a demo, but it mattered if I was going to use the thing myself. It’s on the Chrome Web Store now. The part I’m still figuring out is the first run: installing the extension is easy, but you have to connect your coding tool before you can send your first note. If you’ve built a browser extension that needs a separate setup step, how did you help people get through it? I’m torn between showing a quick example first and getting people straight to connecting their own tool. Here’s VibeQuill on the Chrome Web Store - https://chromewebstore.google.com/detail/vibequill/hgcefdgiponpnfgcaflcnkmhojjcfnkj if you’re curious.   submitted by   /u/Distinct-Occasion599 [link]   [comments]