All packs

Kit · 31 pages · 11 prompts + house style

Screenshots that earn their place

Every screenshot you add is a maintenance bill. Decide which ones are worth paying.

After using this: You'll know which screenshots are worth keeping, your alt text will finally say something useful, and every release will hand you a short list of the images it made wrong.

Who this is for

You look after a help center with more screenshots than you can keep current, and every product release leaves some of them wrong.

Not for you if

You want help making screenshots look nicer. This is about which ones are worth having and keeping them true, not about design.

$89

One-time purchase · HTML and PDF

License

Instant delivery after payment.

Also in a bundleSave $87Clean up an old help center

How it works

It starts with one rule: nothing may exist only inside an image. Prompt 2 audits one category and finds the images carrying facts that exist nowhere else. Then you decide which visuals earn their upkeep, move the facts into the words, write alt text that works for screen readers, search and AI, and build each release's reshoot list from the release notes rather than from memory.

What's inside

  1. 01Why screenshots go stale so fast, and what a stale one costs
  2. 02The one rule: nothing may exist only inside an image
  3. 03The 4 jobs a visual does well, and the 4 it does badly
  4. 04Screenshot, diagram, video or words: what each one costs
  5. 05Taking a screenshot that lasts, with before and after examples
  6. 06Alt text that works for screen readers, search and AI
  7. 07Keeping them current: a reshoot list built from each release
  8. 0811 prompts, including the audit that finds your load-bearing images, with a finished example of its output
  9. 09A house style setup prompt your team and your AI assistant can follow
  10. 10The short version: every rule and prompt on one page

See the pages

3 pages from the PDF you download, as they are. Select one for a closer look.

Preview a prompt from the pack

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

You are a careful documentation reviewer looking for information that exists only inside images, where no search, screen reader or AI can reliably reach it. Our articles: [paste in full, including the alt text and captions of every image. Attach the images if you can. If you can't, describe what each one shows] Our product: [one line] If I attached images, list what you can read in each one first, so I can check it. For every image, tell me: 1. What job it is doing: locating something, reassuring the reader, showing a relationship, showing a result, or decoration. 2. Whether anything in it exists ONLY in the image and nowhere in the text. Be specific: values, limits, plan names, button labels, error message text, steps, states. Call these load-bearing images. 3. What the text would need to say for the image to become optional. Give me the sentence. 4. Whether the alt text is doing any work, or is just a label. 5. Whether the image is likely to be stale, based on anything in the surrounding text that suggests the interface has changed. Then give me: - The load-bearing images, ranked by how much damage the hidden information does if a reader or a bot cannot see it. Money, limits and error messages first. - The images that are pure decoration and could be deleted with no loss. - A count: how many images, how many load-bearing, how many with useful alt text. Do not guess at what an image contains beyond what I described or attached. Don't invent any fact I didn't give you. Where you'd need one, write [TODO: confirm]. At the end, list only the facts you needed and didn't have, not style choices, things to double-check, or anything I already gave you.

The thinking behind it

Want the thinking behind this kit? The course Writing the article covers it in short parts, with an exercise in each.

Questions

Screenshots that earn their place, $89

Instant delivery after payment.