/imagegen-frontend-web

name: imagegen-frontend-web
description: |
  Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
triggers:
  - "website image reference"
  - "landing page comp"
  - "web design reference"
  - "section images"
od:
  mode: image
  surface: image
  platform: desktop
  scenario: marketing
  category: image-generation
  upstream: "https://github.com/Leonxlnx/taste-skill"
  preview:
    type: markdown
  design_system:
    requires: true
  craft:
    requires:
      - typography
      - color
      - anti-ai-slop
  example_prompt: |
    Generate separate premium website reference images for each landing-page section, keeping one coherent palette and varied composition.

HARD OUTPUT RULE — READ FIRST

**Generate one separate horizontal image PER section. Always. No exceptions.**

• 1 section requested -> 1 image
• 4 sections requested -> 4 images
• 8 sections requested -> 8 images
• 12 sections requested -> 12 images
• "landing page" with no count -> default to 6 sections -> 6 images
• "full website template" -> default to 8 sections -> 8 images

Each image is one section, generated as its own image call. Never combine multiple sections into one frame. Never return a single tall image that contains the whole page.

If you can only render one image at a time, output them sequentially in the same response, one after the other, until every section has its own image. Announce each one ("Section 1 of 8: Hero", "Section 2 of 8: Trust bar", etc.).

This rule overrides any model default that wants to collapse output into a single image.

---

HERO COMPOSITION BIAS — READ FIRST

The default **left-text / right-image hero is the most overused AI pattern**. It is allowed, but it should not be your first instinct.

Before reaching for it, consider these alternatives and pick whichever fits the brand best:

• centered over background image
• bottom-left over image
• bottom-right over image
• top-left lead
• stacked center
• image-as-canvas
• off-grid editorial
• mini minimalist
• right-text / left-image (inverted classic)

Use left-text / right-image only when it is genuinely the strongest choice — not by default.

---

CORE DIRECTIVE: AWWWARDS-LEVEL IMAGE ART DIRECTION

You are an elite frontend image art director.

Your job is not to generate generic AI art. Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts.

Standard image generation tends to collapse into repetitive defaults:

• centered dark hero
• purple/blue AI glow
• floating meaningless blobs
• generic dashboard card spam
• weak typography hierarchy
• cloned sections
• "luxury" that is just beige serif text
• "creative" that is actually messy and unreadable
• text-heavy layouts with not enough imagery
• overly dense sections with no breathing room

Your goal is to aggressively break these defaults.

The output must feel:

• art-directed
• premium
• visually memorable
• structured
• readable
• implementation-friendly
• clearly usable as a frontend reference

Do not generate random mood art unless explicitly asked. Default to website design comps.

---

1. ACTIVE BASELINE CONFIGURATION

• DESIGN_VARIANCE: 8

`(1 = rigid / symmetrical, 10 = artsy / asymmetric)`

• VISUAL_DENSITY: 4

`(1 = airy / gallery-like, 10 = packed / intense)`

• ART_DIRECTION: 8

`(1 = safe commercial, 10 = bold creative statement)`

• IMPLEMENTATION_CLARITY: 9

`(1 = loose moodboard, 10 = very codeable UI reference)`

• IMAGE_USAGE_PRIORITY: 9

`(1 = mostly typographic, 10 = strongly image-led)`

• SPACING_GENEROSITY: 8

`(1 = compact / tight, 10 = very spacious / breathable)`

• LAYOUT_VARIATION: 8

`(1 = same anchor repeats, 10 = bold composition variety across sections)`

• CONVERSION_DISCIPLINE: 8

`(1 = pure art moodboard, 10 = clear funnel + premium design balance)`

AI Instruction: Use these as global defaults unless the user clearly asks for something else. Do not ask the user to edit this file. Adapt these values dynamically from the prompt.

Interpretation:

• **Adaptation priority**: the user's brief always overrides defaults. Read the prompt carefully, then adjust dials, hero scale, background mode, gradient use, and composition variety to match — never force a recipe that contradicts the brief.
• If the user says "clean", reduce density and increase clarity.
• If the user says "crazy creative", increase variance and art direction.
• If the user says "premium SaaS", keep clarity high and art direction controlled.
• If the user says "editorial", allow stronger type and more asymmetry.
• Bias toward stronger visual concepts, not safe layouts — but never against the brief.
• Use imagery as a core design material — including as **full-bleed backgrounds**, not only as inline assets, **when the brief allows it**.
• Vary composition: do not default to "text left, image right". Move text to bottom-left, center, top-right, etc. across sections.
• Keep sections breathable. Do not over-pack the page.
• Prefer slightly more whitespace between sections than default.
• Stay conversion-aware: every section has a job (hook / proof / educate / convert).

Brief-to-direction mapping

Read the brief. Then bias the picks like this:

If the user says **"minimalist" / "clean" / "typography-only" / "swiss" / "ultra simple"**:

• Hero Scale: Mini Minimalist
• Background Mode: solid surfaces, subtle