READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card
复制下面这句话，粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具，它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-hyperframes-f233015db934 ，按照其中的说明把「hyperframes」安装到你（当前 AI 工具）中。执行前先告诉我将运行的命令和写入的位置，等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件，由原作者维护。在 GitHub 查看
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).
Atomic capabilities you load on demand — not full video workflows. For "make me a video", use the intent router below.
| You want to… | Skill |
|---|---|
Author / edit an HTML composition — the data-* contract, clips, tracks, sub-compositions, variables | /hyperframes-core |
| Animate — atomic motion, scene blueprints, transitions, runtime adapters (GSAP / Lottie / Three.js / Anime.js / CSS / WAAPI / TypeGPU) | /hyperframes-animation |
Creative direction — frame.md / design.md, palettes, typography, narration, beat planning, audio-reactive | /hyperframes-creative |
| Media — TTS voiceover, background music, transcription, background removal, captions | /hyperframes-media |
Media resolve — find + freeze BGM, SFX, images, icons from HeyGen catalog into .media/ with manifest tracking | /media-use |
| CLI dev loop — init, lint, validate, inspect, preview, render, publish, doctor | /hyperframes-cli |
Install registry blocks / components (hyperframes add) | /hyperframes-registry |
This section knows only the top-level workflows; it does not load their internal references or the domain skills above.
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:
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 | Use it for |
|---|---|
/product-launch-video | Marketing / launching / promoting a product — from its URL, a brief, or a script (even if the site is only named) |
/website-to-video | Turning a general website into a video — site tour, portfolio / landing-page showcase, social clip from the site's visuals |
/faceless-explainer | Explaining a topic / concept from text — no product, no URL; every visual is LLM-invented |
/pr-to-video | A GitHub PR / code change → changelog / feature-reveal / fix / refactor explainer |
/embedded-captions | Adding captions / subtitles to an existing talking-head video (footage untouched) |
/talking-head-recut | Packaging an existing talking-head video with designed graphic overlays — lower-thirds, data callouts, kinetic titles, pull-quotes |
/motion-graphics | A short, unnarrated, design-led motion graphic — kinetic type, a stat / chart hit, a logo sting, a lower-third overlay |
/music-to-video | A music track → a beat-synced video — lyric video, slideshow, or kinetic promo; the music drives pacing (optional user images / videos cut onto the beat grid) |
/slideshow | A presentation / pitch deck / interactive deck — discrete slides, fragments, branching, hotspots; output is a navigable deck, not a rendered video |
/general-video | Anything else — longer or multi-scene pieces, a static loop / poster, a custom composition |
/remotion-to-hyperframes | Porting an existing Remotion (React) composition to HyperFrames (migration, not creation) |
Disambiguation (only where confusable):
/motion-graphics, regardless of input./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./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)./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.)/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./general-video only when the piece is clearly longer than ~3 min, or is a static / loop / custom format.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:
npx skills add heygen-com/hyperframes --skill <workflow-name> (e.g. --skill pr-to-video — bare name, no leading /).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.
HyperFrames skills are versioned. npx hyperframes init checks the installed skills against the latest on GitHub and installs/refreshes the full set whenever anything is out of date or missing — so a freshly init'd project always has the complete, latest set (and re-running init on an up-to-date project is a no-op). The check is a quick GitHub round-trip; offline (or rate-limited) it falls back to installing after a short timeout, so init never hard-fails on a network hiccup. The creation workflows scaffold with init, so starting a new project always runs this check and pulls our latest skills from GitHub when they're stale. The --skip-skills flag is currently neutered (a temporary measure while the skills.sh registry catches up): passing it no longer skips the check, so every init checks GitHub. CI/tests opt out via the HYPERFRAMES_SKIP_SKILLS=1 env var.
If a task is behaving unexpectedly, or before a long build, confirm the installed skills are current:
npx hyperframes skills check (add --json for a machine-readable verdict; exits non-zero when anything is outdated or missing).npx hyperframes skills update — pulls the full set to the latest, installing any not yet present (same as init's install step).The CLI also surfaces a one-line reminder when a render / lint / validate run detects stale skills.
/product-launch-video/website-to-video/faceless-explainer/product-launch-video; no headless Chrome.)pin-and-paper preset. (sweet spot 30–90s)./pr-to-videoowner/repo#N ref, or "this PR" — read via the gh CLI (not a site to scrape)./embedded-captions/talking-head-recut/motion-graphics/music-to-videoaudiomap.json) the whole video is built on./slideshowSlideshowController reads to turn the GSAP timeline into a navigable deck — discrete slides, fragment reveals, branching sequences, hotspot navigation, presenter mode, and speaker notes. The deliverable is a deck, not an MP4./general-videohyperframes-* skills) → validate./remotion-to-hyperframes