All packs

Kit · 36 pages · 12 prompts + house style

Stop re-shooting screenshots by hand

A rig that finds your stale screenshots and re-shoots them. You don't write the code.

After using this: You'll have something that finds your out-of-date screenshots, takes them again, crops and labels them the same way every time, and hands you the result to check.

Who this is for

Your help centre has more screenshots than you can possibly keep current. You don't need to be able to code, but you do need to be willing to run a command and look at what comes out.

Not for you if

You want to decide which images should exist in the first place, or what they should show. That's Screenshots that earn their place.

$99

One-time purchase · HTML and PDF

Licence

Instant delivery after payment.

How it works

Screenshot maintenance loses to everything else on your list, and not because anybody is lazy. It's invisible until it's embarrassing, it never looks finished, and the tedious half is most of it. This kit builds the rig that takes the tedious half: one prompt walks an AI coding tool through seven stages, stopping after each so you check before it carries on, and eleven more let you build or fix one piece at a time. What you keep is the judgment. What you hand over is the clicking.

What's inside

  1. 01How to use this kit
  2. 02Why doing it by hand always loses
  3. 03What to automate and what to keep
  4. 04Ranking what's stale without opening anything
  5. 05Capturing the same way every time
  6. 06The seven things that break it
  7. 07Annotating without it looking automated
  8. 08Wiring it into your docs
  9. 09The prompts
  10. 10Telling whether it worked
  11. 11Give your AI your house rules
  12. 12What to do next

Preview a prompt from the pack

The full prompt, exactly as it appears in the pack. Nothing removed.

A screenshot came out wrong and I want to know why before I change anything. What I expected: [describe it] What I got: [describe it, and paste any error] Work through the common causes in this order and tell me which it is, with your reasoning: 1. Wrong account. Does this screen look different for staff, admins, or a different plan? This is the most expensive one because the picture looks completely fine. 2. Scale. If an annotation is near the target but never on it, and the error grows the further across the screen you go, the zoom or the device pixel ratio is not what the script thinks. 3. Timing. Skeletons, spinners, half-drawn charts, empty states about to fill in, or an animation mid-flight all mean the shot fired before the page was finished, not before it had loaded. 4. Hover. If something is missing entirely, it may not exist in the page until the mouse is over its parent. 5. State. Different data, different counts, a different plan, a flag on or off. 6. Size. If it looks fine locally but wrong once published, check the height against the platform's limit. Tell me the single most likely cause, how to confirm it in one step, and then the fix. Add a check so it fails clearly next time rather than producing a plausible wrong picture.

Questions

Stop re-shooting screenshots by hand, $99

Instant delivery after payment.