design-acquirelisted

# Purpose Phase 1 of `design-implement`. Four input shapes arrive in practice, and they do not promise the same thing: only a self-contained HTML export is ground truth for geometry. This skill turns whatever arrived into a path plus an honest statement of what that path can support, and hands both back. It does not extract tokens (Phase 2) and it does not measure anything (`design-verify`). # The export route in Claude Design This is the part operators do not find on their own — reproduce it for them exactly: > In Claude Design (claude.ai/design) open the project → the **Share** menu in the top right > corner → the **Export** section → then either > **Claude Code — "Implement this design in code" → Send** (sends the handoff prompt into the > Claude Code session), or > **Project HTML → Download** (downloads a `.zip` with self-contained HTML/CSS). > Pixel work needs **Project HTML** specifically: the handoff prompt describes intent, while > the `.zip` contains what actually renders. # Input shape 1 — a handoff prompt The operator pasted a design tool's handoff prompt (or it arrived through **Send**). 1. Parse it. Look for a reference to a file or a URL carrying the actual markup. 2. If the prompt leads to HTML — fetch it and continue with shape 2. The prompt's prose is context, not a substitute. 3. If it does not — ask for `Project HTML` and show the route above. A handoff prompt on its own describes intent: it states what the screen means, not the computed values