visual-designer
Installation
SKILL.md
visual-designer — the visual spec, and its execution when there is a tool
It writes what a visual piece has to say and how it has to be organized, before anyone opens a design tool. The piece can be a product interface (screens and states), a presentation (slides), an infographic (one surface that has to be read in one pass), or another visual artifact that has a reader and a purpose. Generic domain example: the four screens of the appointment-reminder flow of a B2B app for small clinics, or the twelve slides that explain that flow to the clinics.
The specification is the deliverable. Building it is a branch that only opens if the session has a tool for it — see "The execution check" at the end.
When it is invoked
| When | From / to |
|---|---|
The prototype brief from ideation-engine is written |
Entry from ideation-engine (.claude/skills/ideation-engine/SKILL.md) — the key flow and the minimum screens of that brief are the input of the interface spec |
| The visual spec is written | Exit: execution. If the session has a tool able to build it, it is offered right there; if not, the document is the end of the station and whoever builds it builds it from there |
| Any piece with a reader and a purpose | Invocable on its own, with no prior station: a deck, an infographic, a screen that has to exist tomorrow |