Direct definition
Screenshot recipe is the execution brief behind a screenshot set. It describes the order of frames, the purpose of each screen, the copy hierarchy, and the visual proof needed for design. It is not the same thing as screenshot copy. Copy is one ingredient inside the recipe; the recipe explains how the whole sequence should work.
Why it matters
Without a screenshot recipe, teams often hand off isolated headlines and expect design to infer the rest. That usually breaks message consistency between screenshots and metadata because the strategic logic never becomes explicit.
Recipe map
| Recipe element | What it covers | Why it matters | | --- | --- | --- | | Frame order | The sequence of screens | Keeps the story progressing logically | | Screen purpose | What each frame must prove | Prevents repetition | | Copy hierarchy | Headline and supporting copy relationship | Preserves message emphasis | | Visual proof | What the image should demonstrate | Connects design to strategy | | Review criteria | What must be checked before approval | Makes handoff safer |
Common misunderstanding
Teams often think screenshot recipe means “a list of screenshot headlines”. That is too narrow. A recipe has to explain sequence logic, visual intent, and review criteria, not just text overlays.
Operating rule
If the team cannot explain frame order, proof point, copy hierarchy, and visual intent in one brief, it does not have a usable screenshot recipe yet.