Brand
Your tagline
--- title: "Send to HyperFrames" description: "Author a Claude Design as a single-file HyperFrames composition for the \"Send to HyperFrames\" URL import." --- # Claude Design → "Send to HyperFrames" (Single-File Import) > This guide is **fully self-contained**: everything needed to author a valid "Send to HyperFrames" composition is inline here. Do not rely on fetching any other document — produce the composition from this guide alone. Your medium is a **HyperFrames composition**: plain HTML + CSS + a paused GSAP timeline. When the user clicks **"Send to HyperFrames"**, that composition is imported into a hosted HeyGen project, previewed in HyperFrames, and rendered to MP4 in the cloud. You produce a **valid first draft** — a HyperFrames motion-design agent enhances it afterward (sound, media, polish). You are not producing the final video. --- ## How this path differs from download-ZIP There are two ways a Claude Design composition can reach HyperFrames. **This guide is only about "Send to HyperFrames."** | | Download-ZIP flow | **Send to HyperFrames (this guide)** | | --- | --- | --- | | Wire format | multi-file ZIP (`index.html` + `fonts/` + README) | **one self-contained HTML file** | | How it travels | user downloads the ZIP | **the importer fetches one HTML** | | Assets | referenced from sibling files (`fonts/…`) | **resolvable from the one file: inline `data:` URIs (preferred) or a publicly-fetchable absolute URL** | | Next step | a coding agent polishes locally, renders via CLI | **enhanced inside HyperFrames; rendered in the cloud** | The single most important consequence: **there is no file tree on the other side.** A relative path or sibling-file reference (`fonts/…`, `uploads/…`) simply does not arrive. Every asset must be **resolvable**: an inline `data:` URI (preferred — the only fully self-contained form) or a publicly-fetchable absolute URL, never a relative path or local-file variable (see *Asset & fidelity rules*). --- ## The workflow you're feeding into 1. **You (Claude Design)** — author a valid HyperFrames composition as a single self-contained HTML. 2. **Send to HyperFrames** — one click. The importer fetches your HTML, validates it, and creates a hosted HeyGen project. **Import is free.** 3. **Enhance in HyperFrames** — a motion-design agent adds what your export can't: sound effects, background music, and (later) HeyGen media. This is the paid step. 4. **Render** — the cloud pipeline produces the MP4. Your job is step 1: a composition that imports cleanly and is a strong on-brand starting point. --- ## What you send: a single self-contained composition HTML One `.html` file. Everything the composition needs to display its own content must live **inside** that file: - All CSS inline (in `
Your tagline