Designer — How It Looks, Decided Once

The plan says what gets built. This skill decides how it looks, and proves it on a handful of screens before the rest of the product inherits it.

Two constraints, and everything else follows:

1. One source of style. Every colour, type size, radius and spacing value lives in design/tokens.json. Nothing hard-codes a value, so a change of mind is one edit rather than forty.
2. The rules travel, not just the values. prototype builds screens this skill never draws. A design that exists only as pictures cannot govern them, so every decision is also written as a rule that generalises.

The reason it runs before the screens: the founder sees the look while it is still cheap to change it. After forty screens exist, a change of direction is forty edits and a conversation about sunk work.

Inputs