Ethan Ha

Prompts1 min read

Product Visuals With Image Codes (Launch Sequence)

By Ethan Ha

Pretty screenshots don't ship a product. They do help people understand what you built in three seconds.

I don't collect 200 random image shortcuts. I use a small stack of image codes in a fixed order when I need visuals for a launch, landing page, or Insidr-style demo.

The sequence

1. Product truth first

Write the one sentence of what the product does. If the sentence is fuzzy, fix that before any image prompt.

2. Hero / product shot

Prompt · copy & paste

/ProductShot /SoftDaylight /Minimalist

[product] on a clean desk, no fake UI text, no logos you didn't give me

3. UI mock (only if the product is software)

Prompt · copy & paste

/AppMockup /Minimalist /SoftDaylight

Browser window showing [core screen]. Real layout, not generic dashboard soup. Headline text: "[exact headline]"

4. Ad / social crop

Prompt · copy & paste

/AdCreative /UGCAd /CloseUp

Same product, phone-first framing, space for 5 words of caption: "[caption]"

5. Explainer if the product is abstract

Prompt · copy & paste

/Annotated /Schematic /Minimalist

Simple diagram of [user → result]. Labels in plain English. No 3D chrome.

Rules that save re-rolls

  • Stack two codes, not five
  • Put real copy in the prompt — models invent brand names if you don't
  • Generate without tiny text when spelling matters; add type in Figma / code later
  • Reuse the same lighting code across a set so the page feels like one brand

Where this sits in the build

Visuals come after weekend prompts prove the core flow. Otherwise you're polishing a ghost.

This is how I make visuals for products like Insidr — see it live.

Try Insidr →

Brands: partner with me

Keep reading

← Back to Resources