← ClaudeAtlas

compare-screenshotslisted

Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.
transitive-bullshit/skills · ★ 4 · AI & Automation · score 75
Install: claude install-skill transitive-bullshit/skills
# Compare Screenshots Judge images against the intended result. A user-approved design is the target; a historical baseline is only an earlier attempt and may be wrong. Metrics locate differences, never decide correctness. Use [design-with-images](../design-with-images/SKILL.md) for the full exploration-to-implementation loop. ## Workflow 1. **Establish the target.** Use the user-approved reference and stated design requirements when available; do not replace them with your own taste. Otherwise derive the target from the visual requirement, what the thing depicts in reality and the domain skill that owns the look. Write it down in one or two concrete sentences ("low sun should cast long shadows east; trees fill the canopy; labels stay legible at this zoom"). - If the right answer isn't clear — competing valid readings, a taste or product-intent call, a tradeoff only the owner can settle — **stop and ask the user** what the correct answer should be. Show them the comparison. Do not quietly default to the baseline to avoid asking; that bakes in whatever the baseline got wrong. 2. **Confirm comparability** so the differences you see are real, not capture artifacts: same viewport, DPR, route/page, frozen time/tick, camera intent, UI state, data, fonts/assets where they matter. If not comparable, fix capture setup or compare only a crop/feature where the mismatch is harmless. 3. **Measure the approved design.** For reference matchi