Posts tagged “screenshots”

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.