mockups

# mockups — Push Screen Mockups to Claude Design Turn the blueprint's **Screens contracts** into reviewable visuals: one self-contained HTML page per screen (plus each pinned state variant), styled from `design-system.md` tokens, pushed to a **claude.ai/design design-system project** (per `${CLAUDE_PLUGIN_ROOT}/assets/canvas-push.md`) so the user reviews them on the canvas. Since blueprint flow passes render and review each flow's screens **in-pass** (blueprint §6a), this command is the **batch / regeneration tool**: re-render everything after a design-system change, refresh a legacy repo, or redo one flow post-hoc. It requires reviewed Screens contracts and a design system, and is **never a gate for `/vwf:plan`**. **Mockups are realizations, not contract.** They are *views* of the blueprint, regenerated at will: generation happens in an **ephemeral build directory** (the session scratch dir — never inside the repo, never committed), and the Claude Design project is the store of record. A canvas refinement that changes what a screen should *be* routes through `/vwf:blueprint <flow>` or `/vwf:design-system` — then re-run this command (regenerate-over-edit). Nothing here ever writes into `docs/blueprint/`. ## Doc Paths | Doc | Path | | ------------- | -------------------------------------------------------...