← tasteMarkdown

Imagery, icons and texture

Condensed from: Taste Skill (https://github.com/Leonxlnx/taste-skill), Hallmark (https://github.com/Nutlope/hallmark), UI UX Pro Max (https://github.com/nextlevelbuilder/ui-ux-pro-max-skill)

Decide what imagery exists (first that fits wins)

  1. The user's own photos, footage, screenshots.
  2. Screenshots captured from the running product (1440×900 and 390×844 at 2x).
  3. The product built in HTML at true size.
  4. Openly licensed real photos of the subject's world (Wikimedia Commons, museums), credited; never URLs from memory.
  5. The subject drawn in code (last resort).
  6. Type and colour alone, on purpose.

Generated images only on request. Top-scored pages carry a median 37 images, weak ones 5.

Product What leads
Place, food, object, craft, event Photographs. Hero photo is the largest thing on screen 1: full-bleed, or 60-75% of screen height
Software, SaaS, dev tool The product's interface. Max 1-2 context photos, each passing the deletion test (remove it, a fact is lost)
Docs, API, CLI, manifesto Type and code; at most one full-bleed photo band

Showing software

Photographs: size, count, crop

Treatment (one for the whole page)

Text over photos

Delivery

Drawing (only when no honest picture exists)

Icons

Logos

Texture and grain

Default: none, especially on modern-minimal pages and app UI. Use only when the brand's lineage is print (risograph, letterpress, film, ticket stock).

Backgrounds

Placeholders that aren't lorem or grey boxes

Read by your agent through get_guide("imagery-texture") in the taste MCP.