Templates
The shape each skill's design work starts from, and the prompt that seeds it.
What a template is
Clicking a tile on claude.ai/design does one observable thing: it preloads a prompt into the chat box. So a template is a seed prompt plus an inherited design system — picking one for a skill is picking how that skill's surface gets designed, not which files come out.
The seed is therefore derived from the skill's capabilities.json, never stored. Change
what a skill needs and its seed changes in the same commit. A stored prompt is a copy of the
declaration, and a copy drifts — the board goes on showing a connector the skill stopped
using, and nothing disagrees.
By role
| Floor | Skill | Template | Seed |
|---|---|---|---|
sales |
account-research | Research | floor-design/seeds/sales-account-research.md |
sales |
call-prep | Document | floor-design/seeds/sales-call-prep.md |
sales |
draft-outreach | HTML email | floor-design/seeds/sales-draft-outreach.md |
sales |
forecast | Document | floor-design/seeds/sales-forecast.md |
sales |
pipeline-review | UI mockups | floor-design/seeds/sales-pipeline-review.md |
By template
| Template | Produces | Bound to |
|---|---|---|
| Mobile app design | screens at phone width, with navigation between them | — |
| Slides | a deck: one idea per artboard, read in sequence by an audience | — |
| Document | one flowing artboard — a memo, a report, a page of prose | sales/call-prep, sales/forecast |
| Wireframe | structure without styling: what goes where, before what it looks like | — |
| Animation | a timed composition — state changing over a clock | — |
| UI mockups | a working-looking screen: real type, real colour, real density | sales/pipeline-review |
| Résumé | one page, dense, hierarchical, printed as often as viewed | — |
| 3D object | a thing with volume, rotated and lit | — |
| Research | an argued page: claims, evidence, figures, citations | sales/account-research |
| HTML email | a message that survives a mail client's renderer | sales/draft-outreach |
| Color + type pairing | a palette and a type scale, judged against each other | — |
| Diagram | a mechanism: parts, and the arrows that make them one thing | — |
| Flier | a single loud page — one message, read at a glance | — |
Why each binding
| Skill | Template | Why |
|---|---|---|
| account-research | Research | the output is an argued page — a claim about an account with the evidence under it, which is the one template that treats citations as structure rather than decoration |
| call-prep | Document | read once, in the ten minutes before a call, top to bottom — one flowing page and no state |
| draft-outreach | HTML email | the output literally is an email, and the constraint that shapes it — surviving a mail client's renderer — is this template's whole subject |
| forecast | Document | the deliverable is a written number with its reasoning attached; the arithmetic is not the artefact |
| pipeline-review | UI mockups | a scored table with risk flags is a live surface someone sorts and filters, not a page they read; density and colour ARE the design question here |
The existing board
2e14b7eb-87b7-4c99-a9e5-ded75ade8ba6 carries the twenty floors and is a reasonable starting point for
their layout. It does not inherit the design system — twenty floors, authored 2026-08-18, predates the design system — so it is a
reference for structure and not for palette. Recorded rather than quietly reused: a board that
looks like ours and is not is harder to spot than one that looks wrong.
Bindings live in floor-design/templates.jsonl, seeds are generated into floor-design/seeds/, and both are
re-derived by npm run gen:templates. A hand edit to either fails --check.