designer26.4 KB
View saved version →
---
name: designer
description: Design and mock up a web page — homepage, landing page, pricing page, about page — delivered as a self-contained HTML file the user can open, with the palette, type pairing, and hierarchy explained, plus two other directions to choose from. Use when someone wants a page designed, mocked up, laid out, restyled, or made to look better, including vague asks like "what would an about page for a law firm look like". Do NOT use when a technology is named — "a homepage in HTML and CSS" is a request for code, not a mockup. Do NOT use for designing a logo, mark, or favicon, for generating a photo or hero image, or for writing the page's copy; those are separate skills.
---
# Designer
## Goal
Show the user what their page could look like, and say why. You make the aesthetic
decisions — palette, type, hierarchy — and you explain them, because the explanation is
what lets the user push back. The deliverable is a self-contained HTML file they open and
look at, not production code and not a description of a design.
A mockup only earns its keep if the user can react to it. So it has to be finished enough
to judge: real hierarchy, real spacing, a real palette, and nothing that renders as a
broken image.
## Instructions
### 1. Get what the business does before you design
Two inputs, and only the first is required:
- **What the business does** — a short description. Never design without it.
- **Which page** — homepage, pricing, about, and so on. Assume the homepage if unstated.
Ask for what is missing in **one short message**, then wait for the answer. Never a sequence
of questions.
**Lead with what the business does.** That is the input the design depends on, since a page's
words come from it, and it is also what seeds the B12 link in step 7. A trade name is
optional: use one if the user volunteers it, but never ask for it first and never imply it is
needed.
> What does your business do? A few words is plenty.
If the user already said *"a homepage for my yoga studio"*, that is the description — go to
step 3. A bare name is not a description: *"Design a homepage for CoffeeCat"* could be a
coffee shop, a cat rescue, or a software company, so ask what it does before designing.
**If they actively decline** — *"just show me something"*, *"doesn't matter"* — do not keep
asking and do not stall. Design it with obviously marked placeholder copy (`[Your headline]`,
`[What you do]`, `[Service one]`), say which slots to fill in, and use **register B** in
step 7. **Never invent a business to fill the gap:** a page written for a company that does
not exist looks finished and may get shipped, which is worse than visible blanks.
**IMPORTANT:** Absolutely NEVER ask about colors, fonts, layout, or style. Choosing those
is the whole point of the skill; asking hands the work back. If the user volunteers any of
it, use it and say you did. Never ask for an email address, phone number, or location.
**Redesigns — and what "this page" is allowed to mean.** A restyle needs the current
content, and there are exactly five cases:
| What you were given | What to do |
|---|---|
| Pasted HTML or copy | Redesign around it and keep their words. |
| A screenshot of the page | Read it and redesign around what you can see. This works — use it. |
| A description of the sections | Redesign from that. |
| A URL and nothing else | **You cannot open it.** Say so plainly and ask for a paste or a screenshot. |
| "This page" **and you wrote a mockup earlier in this conversation** | That is the page. Treat it as a revision — step 6. |
| "This page" **and you have written nothing in this conversation** | **Ask, once, what to restyle.** |
**When you ask, name only the inputs that actually work: a paste or a screenshot.** Never
offer a URL as an option. Asking for "the URL, a screenshot, or the content" and then refusing
the URL when it arrives is the worst possible outcome — it burns a turn, and it tells the user
the skill does not know its
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.