The developer keeps asking which button I meant

You wrote "the CTA on pricing looks off". The developer asks which CTA. You send a screenshot. They ask whether it's the mobile or desktop version. By the time it's sorted out, the fix took five minutes and the back and forth took most of a day.

Honestly, I'd ask too. A pricing page might have nine buttons on it, three of them orange, and guessing wrong means doing the work twice. So the questions aren't fussiness. They're a developer trying to avoid fixing the wrong thing.

Stop describing it

Point at it instead. Open the page, click the actual button with Lasso and write your note right there. Something like "this one, desktop only, the label wraps onto two lines".

The note keeps the page address, the button's selector and its text, and a screenshot of how it looked when you clicked. That's pretty much the full list of things a developer was about to ask you for.

Then drop the comment's super link into the ticket or the Slack thread. Whoever opens it lands on the live page with your note sitting on that button. No guessing, no follow-up.

When an AI is the one fixing it

This gets even better with Cursor or Claude Code, because agents are confident guessers. Export the collection for AI and paste it in. Every item already says where and what, so the agent goes to the right element rather than rewriting a random div with great enthusiasm. Our guide to sending feedback to ChatGPT, Claude or Cursor has a prompt that works well.