Numbered Pins That Make a Developer Read Steps in Order
How to place numbered pins on a single screenshot so a developer reads your bug report as an ordered checklist, not a scavenger hunt.
How to place numbered pins on a single screenshot so a developer reads your bug report as an ordered checklist, not a scavenger hunt.
A step-by-step workflow: capture a screen, say what's wrong, publish, and hand Cursor a markdown URL it can read. All in one browser tab, in under a minute.
Three defensible rules for framing a cropped still so an agent identifies the right component, plus what goes wrong when you ignore each one.
The crop rectangle decides which element an agent touches. Four defensible rules for what to keep, what to cut, and the failure mode when you get it wrong.
A pinned screenshot and one dictated sentence beat a paragraph of description when you prompt Windsurf. Here is the step-by-step flow.
An agent can only act on what your screenshot points at. Here is how to crop, pin, and word a comment so the change lands on the intended element.
A comment like "the button is confusing" makes the receiver guess which button. Numbered pins point at the exact control, so feedback lands where you meant it.
A precise glossary of markdown screenshots: what the term means, what a review item and a numbered pin are, and why agents read the format cleanly.
A code diff tells you what changed, not how it looks. Here are five specific practices for adding screenshots to a pull request review so the author can act on every comment.
Walk through a design review from opening a browser tab to sending a public link. Each step has a clear outcome the team can act on.
You built a screen, it is almost right, and you want an agent to finish it. Here is the handoff that gets the agent looking at the same pixels you are.
You need to hand off a process to one teammate by Friday. You don't need an SOP platform for that. Here's a 20-minute method using a browser tab.
Capture the exact screens a user sees, narrate each step, and ship a complete FAQ entry to your help center without opening a docs tool.
A procedural walkthrough: capture the screen, write the comment, pin the spot, export markdown, and hand your agent a prompt it can actually execute.
A practical walkthrough for reviewing the built product against the design: cropped stills, spoken comments, numbered pins, and a shareable link the team can act on.
CleanShot X is a beautiful Mac annotation app. A browser-based review link skips the install and gets feedback to the receiver faster. Which one fits the job?
Snagit is a powerful desktop capture app. For one-off reviews you need to share with someone, a browser tab often gets the job done faster.