How to review an AI-drafted screenshot guide

Start with what the reader needs

Name the task, required access, and expected result. A guide for a new teammate should show the page they begin on and the role they need. Avoid assuming they already have a menu open or a file selected.

Record one complete task using sample information. Keep the starting state and the confirmation at the end; both help explain whether the task was completed.

Compare each instruction with its frame

Check the exact label of every button, tab, and field. The instruction should say what to do and, where visible, what changes next. An open menu supports the menu choice; it does not prove that a later setting was saved.

Remove accidental clicks and repeated frames. Add missing transitions when the reader would have to guess. If a detail is too small to read, capture it again instead of inventing a label.

Review sensitive details before using AI

Check selected screenshots for customer names, email addresses, passwords, and API keys before requesting a draft. Use fictional records when possible. Delete frames that the guide does not need.

Aryanna’s source integration sends selected frames, click positions, and task context to the Claude API when you request AI drafting. The recording stays local. Read the privacy page before working with sensitive screens.

Try the exported guide

Open the exported HTML or Markdown guide. Check that images load, steps stay in order, captions make sense, and the last step shows the intended result. Ask someone unfamiliar with the task to follow it when practical.

Keep the guide editable. When the interface changes, record the affected task again and check the new draft instead of carrying outdated button names forward.

Put the steps to work.

Compare a worked screenshot example. Review how recordings and AI requests are handled before using private information.