Skip to content

docs(guides): add Claude Design → Send to HyperFrames single-file import guide#2131

Open
somanshreddy wants to merge 1 commit into
mainfrom
07-10-send-to-hyperframes-guide
Open

docs(guides): add Claude Design → Send to HyperFrames single-file import guide#2131
somanshreddy wants to merge 1 commit into
mainfrom
07-10-send-to-hyperframes-guide

Conversation

@somanshreddy

Copy link
Copy Markdown

Summary

Adds a self-contained authoring guide for the "Send to HyperFrames" import path — where a Claude Design composition is sent to HeyGen as a single HTML file, imported into a hosted project, and rendered in the cloud. This is a different workflow from the existing claude-design-hyperframes.md (download-ZIP + local-CLI-render), so it's a separate guide rather than edits to that one.

Why a new guide

The Send-to path differs from download-ZIP on every axis: one self-contained HTML (not a ZIP), assets inlined as data: URIs (no sibling fonts/ tree), enhanced in HyperFrames + cloud-rendered (not local Claude Code + CLI). One doc can't teach both without contradiction — most starkly, Send-to inverts the "base64 media → use a file reference" rule into "inline everything as data: URIs."

What it covers

  • The single-self-contained-HTML wire format + the composition contract the importer validates (→ 422 on failure)
  • Inline-brand-assets fidelity rules; no bundled/splash-loader artifacts; keep-the-original-as-reference
  • A complete, importable worked skeleton (1920×1080, 8s, 5 scenes, one shader, count-ups, correct HyperShader.init + autoAlpha toggles + window.__timelines registration)
  • The animation-pattern catalog and determinism rules

It is intentionally fully self-contained (no external doc references), because the authoring agent may not reliably fetch a second URL.

Validation

Reviewed for technical accuracy and internal consistency against a known-good composition that was actually imported and rendered to a correct MP4 — verified the contract, the scene tiling (0-8s), the shader-window math, the anchor/non-anchor visibility rules, and that every catalog tween fits its scene window.

🤖 Generated with Claude Code

…ort guide

Self-contained authoring guide for the 'Send to HyperFrames' MCP import path
(distinct from the download-ZIP flow): single self-contained HTML wire format,
the composition contract the importer validates, inline-brand-assets fidelity
rules (base64 data: URIs), no bundled/splash artifacts, keep-the-original-as-
reference, a complete worked skeleton, the animation-pattern catalog, and
determinism rules. Reviewed for technical accuracy against a known-good
imported+rendered composition.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jul 10, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
hyperframes 🟢 Ready View Preview Jul 10, 2026, 9:25 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant