Visual reference generation

Arguing about an image costs an hour. Arguing about a build costs a sprint. Generate the picture first.

Before generating

Settle these, or the output is decoration:

• Surface and platform — web page, native mobile screen, dashboard. These are not the same problem at different aspect ratios: touch targets, native chrome, and scroll behavior change what a good layout is.
• What it optimizes for — one conversion, one task completion, one first impression. Stated, so the image can be judged against something.
• Content reality — real headline lengths, real data volumes, real edge cases. A concept built on three-word labels collapses on contact with actual copy.

Generating

• One concept per image. Tiling several ideas onto one canvas makes them impossible to compare or iterate separately.
• Generate genuinely different directions, not variations of one. Three near-identical options is one option presented three times.
• Include the states that will exist: a populated view and an empty one, at minimum.

Web versus mobile

Web — the fold is a real constraint but not a hard one; horizontal space allows genuine layout choices; hover exists. Design for a range of widths, and decide what the narrow case does.

Mobile — thumb reach dictates where primary actions sit; native navigation patterns are expectations, not suggestions; there is no hover, so affordance must be visible. Design the scroll, not the screenshot.

After generating

Say explicitly what in the reference is direction and what is placeholder. A developer handed a concept will otherwise implement the lorem ipsum faithfully.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

• Generate before the content, states, and constraints are settled. A reference built on placeholder copy hides every real problem.
• Present a generated image as a working design. Say what it is.
• Generate with filler text where real string lengths decide the layout.
• Hand off an image as the spec. Hand off the tokens, spacing, and states behind it.