Draft UI

Deciding a surface's look is a workflow, not a one-shot render: divergent directions built as real HTML, reviewed by the user in the browser, amended, and only then locked into a brief the build chain lifts instead of re-deciding.

1. Ground, then plan N directions

Gather the grounding: the user's own words; an Approved docs/standards/design-tokens.md or the repo's token/theme files; the component kit screens already build from — the render helpers and classes in a components/ folder, a UI package, a design system; the feature's requirements when they exist. Default 3 variants, never more than 5.