Skip to main content
Use an existing design as source material: preserve its visual language, then rebuild what must move as editable HyperFrames scenes.

Choose what should remain editable

Do not animate a stack of complete screenshots merely because they came from a design tool. Use screenshots for proof; use HTML for the parts that need to change.

Start from Figma

Send the agent the Figma link and the outcome:
The agent can use the /figma skill to import assets, read brand values, reconstruct editable components, and translate supported motion. Everything required by the final render should end up as local project source. For tokens, API credentials, exact CLI commands, and import troubleshooting, use the Figma integration reference.

Start from Claude Design or Open Design

These tools can establish layout, palette, type, and scene direction before a deeper production pass.
  1. Give the design tool the current HyperFrames instruction file and your real brand material.
  2. Ask for a valid project rather than isolated mockups.
  3. Download or save the project to disk.
  4. Open that folder with a coding agent.
  5. Let the agent validate timing, motion, media, captions, and rendering.
Claude Design instruction · Open Design handoff

Judge the handoff

A useful handoff has:
  • a clear visual direction;
  • real assets or honestly labeled placeholders;
  • editable source for anything likely to change;
  • stable local media and fonts;
  • a project that opens and can be checked.
Run:
Then review the actual movement in Studio, not only the design stills.