design

# Create a design canvas **Two quick exits.** Empty request: ask in one line what they want designed (and for what), then stop. Request EXACTLY one of `consent`, `revoke`, `sync`, `login`, `import`, `export` or `status` alone (or `import`/`export`/`sync` plus only a URL or project name): that is a Claude Design account/project command this preview doesn't handle - say so in one line and stop. For `consent`, `revoke`, `login`, `sync` point at `/design <verb>` alone (`/design-sync <project>` for a sync with a project hint); those need a first-party claude.ai login and an org policy permitting Claude Design, so without either say Design consent/sync is not available here. For `import`, `export`, `status` say those are not available while this preview is on and point at claude.ai/design, never a `/design ...` spelling. Do not design something named "status". Anything that describes something to design -- a login page, an export dialog, a status dashboard - is a brief. This is an early preview of Claude Design inside Claude Code: the skill ships a **precompiled payload** - Claude Design's "Design Components" editor on a multi-artboard canvas, packaged to run inside a published Artifact. It is not at parity with claude.ai/design and the editor baked into each canvas does not update after publish; say so plainly if asked. You do NOT build or modify the editor - you seed design content into a copy of the payload with the helper, and publish. Every `.dc.html` file renders as its own...