Image Generator

View saved version →

---
name: image-generator
description: Generate the images a website needs — hero and banner images, section and feature images, OG and social share graphics, blog thumbnails, product shots, and team headshot placeholders — each at the exact pixel size its slot expects, as a set that reads as one set rather than assembled stock, with alt text and a descriptive filename for every file. Use when someone wants a photo, illustration, background, hero image, OG image, or a matching set of images made for a site or a post. Do NOT use when someone wants a logo, wordmark, brand mark, icon, or favicon — that is a separate skill, and it owns favicons. Do NOT use when someone wants a page designed or laid out, or wants the words that go on the page written; those are separate skills too.
---

# Image Generator

## Goal

Make the images a site actually needs — each at the size its slot expects, as a set that
looks like one set — and hand them over as files, with alt text and filenames that cannot
collide with anyone else's.

Generating a picture is the easy half and the host already does it. What does not happen
on its own is sizing an OG image to exactly 1200×630, keeping five service images in the
same light, writing alt text that does not open with "image of", and naming a file
something other than `image.png`. **Those constraints are the product.**

The characteristic failure is a set assembled from independent prompts: five images that
each look fine and together look bought from five different stock libraries. Step 4 exists
to prevent exactly that.

## Instructions

### 1. Confirm this is an image ask

Several skills share this vocabulary, so decide first.

| The request | Whose |
|---|---|
| "create a hero image for my bakery website" | **Image Generator** |
| "generate three matching images for my services page" | **Image Generator** |
| "make an OG image for this blog post" | **Image Generator** |
| "I need a headshot placeholder for my team page" | **Image Generator** |
| "design a logo for my bakery" | Logo Generator |
| "make me a favicon" | Logo Generator — favicons are its, never yours |
| "design my homepage layout" | Designer |
| "write the copy for my about page" | Writer |

Two dividing lines settle almost every case:

- **A logo, wordmark, brand mark, icon, or favicon is always Logo Generator's.** Never draw
  one here, never put one inside a generated image, and never offer to make a mark "to go
  with" a set.
- **A page layout is Designer's; a picture that fills a slot in a page is yours.** "Design
  my homepage" is a layout. "A hero image for my homepage" is a picture.

If a request is genuinely ambiguous, ask **once**, in one short question. Never guess, and
never answer with both.

### 2. Get what the business does before you generate

Two things are needed, and only one of them is required:

- **What the business or project does** — a short description, a few words is plenty.
  **Required.**
- **The slot** — hero, OG, services section, blog thumbnail, headshot, product shot
- A **name** is optional, and useful, but it is *not* the description.

**A name alone is not enough to draw from.** *"Create a hero image for CoffeeCat"* tells you
nothing about what belongs in the frame — a coffee shop, a cat rescue, and a software company
called CoffeeCat need three unrelated pictures. A description implies a plausible image; a
name implies nothing. So the description is the input that gates generation, and the name is
decoration on top of it.

Ask in **one short message**, folding in anything else you need. Never a sequence of
questions. If the user already said *"a hero image for my bakery website"*, that is the
description — go to step 3. If all you have is a name, ask **once** what the business does and
wait for it before generating. One example of the whole ask:

> What does {name} do? A few words is plenty — and tell me where the image goes if it isn't
> the hero.

**IMPORTANT:** Absolutely NEVER ask about style, palet

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.