Hyperframes

HyperFrames — start here

HyperFrames renders video from HTML — a composition is an HTML file whose DOM declares timing with data-* attributes, whose animation runtime is seekable, and whose media playback is owned by the framework. The full authoring contract lives in /hyperframes-core; read it before writing composition HTML.

Below: a capability map (the domain skills, loaded on demand) and the intent router (pick a workflow for any "make me a video" request).

Capability map — the domain skills

Atomic capabilities you load on demand — not full video workflows. For "make me a video", use the intent router below.

Intent routing — pick a workflow

This section knows only the top-level workflows; it does not load their internal references or the domain skills above.

Before routing — confirm the input, not the spec

Routing needs to know what the video is about — its input and subject. If that's unspecified ("make a video about our thing" with no URL, product, topic, or asset), ask before entering any workflow — committing to a workflow IS the routing decision. At most two questions:

• Input — a product (URL / brief), a general website, a GitHub PR, a topic to explain, or an existing talking-head video?

Spec defaults — state, don't ask (they never change the route): aspect 16:9 (use 9:16 only for a named vertical destination — TikTok / Reels / Shorts); narration / caption language = the user's. The chosen workflow re-confirms its own specifics at its first step.

Workflow cheat-sheet

Disambiguation (only where confusable):

• Motion-first & unnarrated (under ~10s, the motion _is_ the message) → /motion-graphics, regardless of input.
• A URL or script — markets a specific product (even just naming the site) → /product-launch-video; a general non-product site → /website-to-video; a GitHub PR link → /pr-to-video; explains a concept with no product / site → /faceless-explainer. Genuinely unclear product-vs-topic, or launch-vs-general-site → ask one question.
• Existing footage — plain spoken-word subtitles → /embedded-captions; designed overlay cards → /talking-head-recut. Neither edits the footage itself (re-timing / recolor / reframe / reorder / audio is NLE editing — out of scope).
• A music track is the input (an audio file, or a video to pull audio from) with no narration → /music-to-video — the music's beats/energy drive the pacing. (Narrated pieces stay with the input-matched workflow above; /motion-graphics is for short unnarrated motion that isn't music-driven.)
• A presentation / pitch deck / interactive deck (discrete slides, navigation, presenter mode) → /slideshow — output is a navigable deck, not a rendered video. An explicit "slideshow" request proceeds directly; an adjacent trigger ("deck / slides / presentation / convert this page") makes /slideshow confirm it's a slideshow before authoring, and switch to the appropriate non-slideshow workflow if not.
• Length is a guide, not a gate — intent picks the workflow; go to /general-video only when the piece is clearly longer than ~3 min, or is a static / loop / custom format.

If the matched workflow isn't installed

Once you've picked a workflow, check it's actually available to you. If the matched workflow skill isn't installed, don't fall back to guessing — tell the user to install it first:

• Just this workflow: npx skills add heygen-com/hyperframes --skill <workflow-name> (e.g. --skill pr-to-video — bare name, no leading /).
• All workflows at once: npx skills add heygen-com/hyperframes --all (core + every workflow, skips the picker).

After they run it, re-read the workflow's skill and continue.

Keeping skills current