implement-design-from-exportlisted

# Implement Design from Export ## When to use - User pastes/attaches a design export, HTML/CSS or screenshot, and asks to build matching UI. - User saved a design export to a file and asks you to build from it. - Not for writing a new design prompt before design, see the `craft-design-prompt` skill for that. The user designs in an AI design tool themselves, then hands the result to the agent one of these ways: - Pastes the exported HTML/CSS directly into the chat. - Saves the exported HTML to a file in the repo and tells the agent which path to read. - Attaches/pastes a screenshot of the design and asks the agent to build UI to match it visually. Do not ask the user to authenticate, generate an API key, or set up any credential for this, there's nothing to configure. Design exports are static layouts. Hover states, animations, validation, and state management are not part of the export and need to be implemented separately. When implementing those missing states, apply the `interface-design` skill's motion framework, frequency gate, easing, duration budgets, origin-aware popovers, rather than inventing ad hoc timings. Exports often hand-roll dropdowns, modals, toasts, or tooltips as plain styled `div`s. Before wiring these up, check whether the project already has a primitive for it, see `interface-design`'s native → primitive → hand-roll ladder, and use that instead of keeping the exported markup as the real implementation. Before calling the implementation done, ex