Vision prompt guide
Claude Fable 5.2 Vision for Screenshot Audits
Two design variants may look nearly identical while one drops an important condition. Claude Fable 5.2 accepts image inputs, and Anthropic published chart-recognition results at launch. We used those documents to build two illustrative screenshot checks. Run each one on material you can manually verify.
The quick picks
Use the exact-copy prompt when a layout has approved wording. Use the comparison prompt when a second export may have lost an element. In both cases, give the screenshots short IDs and ask for an image ID and location beside every finding.
Prepare a clean source packet
Use a full-size screenshot of each version and provide a separate text copy of the approved statement. Label them A and B in your prompt. Remove unrelated browser tabs and personal material before capturing. If a relevant label is hard to see, attach a separate clear view labeled with its parent ID.
Prompt 1. Audit the exact claim
Imagine an A5 flyer that must say “Workshop materials included” exactly once. The illustrative output is one row per screenshot with the observed wording, location and pass or verify status. Check quoted text visually before accepting a reported mismatch.
Compare [image ID] with the approved phrase [exact phrase]. Return image ID, visible wording, approximate location and status. Use verify if the line is obscured or too small. Do not infer hidden text. Keep any layout suggestions separate from the wording check.Prompt 2. Find the lost element
A revised flyer may move the registration instruction under a dark photo. Give the model the expected element list. If it says B lacks the action, inspect the full frame and a zoomed view before deciding whether the action is absent or merely hard to read.
Review [A] and [B] against [required element list]. For each element, give location in A, location in B and a short evidence note. Mark uncertain findings for manual review. Return the one difference most likely to block the intended action.Convert findings into precise changes
Place the two screenshots side by side on a Ciyo canvas. Turn each confirmed discrepancy into a named change request such as “Restore the exact registration line below the date in B.” Attach the relevant reference and give the editor the copy as text.
Read the final export again
After the edit, review the actual exported file at its intended size. Compare the same list against the new version and keep a note of which findings were dismissed. A repeatable audit depends on the evidence and pass rule staying visible.
Turn an uncertain finding into a follow-up request
If the response says the registration line is absent, first inspect the supplied image yourself. If the line is present but too small to read, label a clearer view B-detail and keep the full B image attached. Ask the model to revise only that finding using both views.
The decision record should distinguish missing, obscured and confirmed present. These lead to different edits: restore a missing line, increase contrast for an obscured line, or dismiss a false alarm. Keep a human check for the exact wording before approving the export.
Frequently asked questions
Can vision read every label?
Image quality, size and legibility affect the result. For critical wording, read the original export and keep an approved text source.
Does this create the corrected image?
The Claude audit returns written findings. Apply approved changes in the design tool, then review the export.
Bring two designs into one view
Place your originals and revision notes together before choosing which visual to update.