Before you start
- A PNG, JPG or WebP screenshot with enough context to understand the issue.
- Source access for the AI if you expect a code change, or the original design file for a manual edit.
The workflow
- 01
Capture the reproducible state
Use your normal screenshot tool to capture the page after the issue appears. Record the viewport size and steps that caused it. For a menu overlap, include both the menu and the obscured control. Do not crop away the very context the model needs to understand the bug.
- 02
Mark a small number of changes
Upload the screenshot to Stash’s annotation tool. Use a box for the affected area, an arrow for the target and numbered text for each request. Keep labels outside the important content when possible. Prefer three precise notes to a screen filled with arrows pointing in several directions.
- 03
Describe expected and actual behavior
Write “At 390px wide, the booking button overlaps the date; keep both on separate rows” rather than “fix mobile”. Include the source artifact link or relevant code with the screenshot. If you are only sharing a flattened design export, explain that the edit must be made in the original tool.
- 04
Export or create a review
Download the annotated PNG to attach to the AI conversation, or create a review link for human comments. An AI may not be able to open an invitation-only image through ordinary web browsing. Attach the image or use an authorized connection and confirm what it can read before relying on it.
- 05
Check the fix in context
Ask for a new version with only the requested changes. Reproduce the original steps at the original width and also check a wider view. Confirm that the fix did not hide content or break the primary action. Keep the original screenshot as evidence of what you were trying to change.
WORKED EXAMPLE
Explain an overlapping button
A fictional narrow layout has a booking button covering the final line of the date.

Starting point
“The mobile layout looks broken.”
A clearer result
“1: At 390px wide, put the date and booking button in separate rows. 2: Keep the button full width. Preserve the desktop layout and all copy.”
Check the result
- The date remains fully visible.
- The button can be reached by keyboard.
- The desktop layout still matches the baseline.
Original practice files
Fictional examples made for these guides. Download them to try the workflow with your own tools.
A prompt you can use
Replace the bracketed fields with your project details. Check what the AI can access before requesting changes.
Use the attached annotated screenshot and [source/work link]. Reproduce the issue at [viewport] after [steps]. Actual behavior: [problem]. Expected behavior: [result]. Implement notes [numbers] only. Preserve [constraints]. Return a new version and explain how to verify the fix. Do not claim a screenshot alone gives you the editable source.Download the brief, prompt and checklist ↓
Questions & answers
How do I show an AI exactly what to change in a screenshot?
Use arrows, boxes and numbered notes, then pair the image with the editable source and a bounded instruction. Ask the AI to confirm the intended changes before creating a revision.
How do I explain a visual bug to an AI coding assistant?
Include reproduction steps, viewport, actual behavior, expected behavior and the source link. A marked screenshot helps locate the issue; the code or artifact source lets the assistant fix it.
Can I hide private details before sharing?
Remove them in the source or cover them with a solid opaque block before exporting. Pixel blur is visual obfuscation and may not sufficiently conceal sensitive content.
Does the annotation tool capture my screen?
No. Bring a screenshot or exported image from another tool. Importing and editing stay in your browser; creating a review link uploads a flattened copy.
Keep in mind
- Annotations do not guarantee pixel-perfect AI edits or restore source layers.
- Download your result before leaving the editor; local edits are temporary.
Put it into practice.
Start with the example or bring a small project of your own.
Annotate a screenshot ↗