A repeatable way to turn a pile of screenshots and quick notes into a clean, shareable report — without writing or designing it yourself. You organize the evidence; an AI agent does the writing and layout. This is the pattern behind the Design Gap Reports SOP, generalized — that one's a recipe for a specific job, this is the technique underneath it.
Screenshot or photograph whatever you're documenting. No editing, no writing yet — just capture it.
Lay the images out on a visual board — grouped, ordered, marked up — so the story is obvious just from the layout.
Hand the board to an AI agent and ask for the report. It reads the organization you already did and writes and designs around it.
You don't need to be a designer or a writer to produce a document that looks like one. Your job is staying the expert on what's actually in the screenshots — what's wrong, what changed, what matters. The agent's job is turning your organization into a well-made document. The clearer you organize in step 2, the less the agent has to guess, and the better it gets on the first try.
The kiosk audit happened to be a UI-vs-design report, but the pattern isn't about UI bugs — it's about any job where you're holding a pile of visual evidence and need a document out of it:
Step 2 is the one worth practicing. An agent can only work with what your layout already tells it — so the organizing you do before you ever open Claude is most of the job.
If two things are being compared, put them in the same row or column, in a consistent order, every time. The comparison should read from the layout alone.
Circle it, arrow it, box it — directly on the screenshot. A note that travels with the image survives being handed off; a separate list of comments gets lost or misread.
If the grouping already says "these two are being compared," you don't need a caption that says it again. Save words for what the picture can't show.
Rough circles and crooked boxes are fine — even better, they read as genuine. Presentation is the agent's job, not yours.
Hand over the board — the FigCraft/Figma file, plus any raw material it was built from (video, photos, links).
Say what it's for and who it's going to — a report nobody will read is a different document from one a specific person has to act on.
Say to use your material, not invent its own — the agent should build the report from what's actually on the board, not design graphics to explain it.
Review the first draft like any draft — correct wording, swap an image, reorder a section. Ask for the update on the same document rather than starting over.
This pattern turned into a step-by-step recipe for one repeat job: reporting a UI/design mismatch to a developer. Use it as a template for writing up your own repeat task the same way.