ukimsanov efd3d52dc1 fix(skill): unify SVG-naming docs with the actual capture emission
Audit found four docs still claimed the capture pipeline emits filenames
in the shape <role>-<word>-<hash>.svg (e.g. partner-logo-amazon-2TeU5qiM.svg,
header-logo-airbnb-EfGh5678.svg, stripe-logo.svg). That naming was an
EARLIER design that was abandoned in commit 5f290345 in favor of pure
content-hash names — aria/heading-derived label inference was misaligning
across partner-logo carousels, so the pipeline now emits:

  - logo-<hash>.svg   for DOM-marked logos (per tokenExtractor.ts's
                      isLogo signals: inside <header>/<nav>/[role=banner],
                      inside <a href="/"> brand-home link, aria-label
                      matches document.title, or class-substring match;
                      see commit 02f95f95 for the broadened detection)
  - svg-<hash>.svg    for everything else
  - <human-slug>.png  for downloaded raster images (catalog-derived
                      slugs were not affected by the alignment bug)

Four docs were carrying the old claim and would mislead an agent into
grepping for the wrong filename shape:

1. step-0-capture.md "Captured asset filenames" section — described
   the three-trust-level pattern based on <role>-<slug>-<hash> shape.
   Rewrote to describe the actual logo-<hash>/svg-<hash> emission +
   the three real ways to find a logo: grep asset-descriptions.md,
   ls | grep logo-, or open + verify. Kept the operational rules
   (non-critical = pick by thumbnail; brand-critical = open + verify;
   verify path exists before writing; legacy historical pitfall +
   gnarly-path-replacement rule).

2. beat-builder-guide.md Pre-Write Cheat Sheet pitfall #4 — same
   outdated claim, rewrote to point at the real naming convention +
   the discovery procedure (grep asset-descriptions.md for the brand,
   ls | grep logo- for DOM-marked candidates, open + verify for
   brand-critical). Cross-references the doc landmine from commit
   e6aa7fed.

3. step-3-storyboard.md "Captured Asset Inventory" table — example
   rows used filenames the pipeline doesn't actually emit
   (stripe-logo.svg, partner-logos/*.svg). Updated to realistic
   examples: capture/assets/logo-5fce3a91.svg (real DOM-marked logo),
   capture/assets/svgs/svg-* (46 files) (the partner-logo grid).
   Added a one-paragraph note below the table explaining the naming
   convention + telling agents to resolve the real hash via
   asset-descriptions.md before writing it into a beat.

4. beat-builder-guide.md GSAP-only section "SVG VIA IMG" rule —
   minor: updated the example from <img src="logo.svg"> to <img
   src="capture/assets/logo-<hash>.svg"> to reflect realistic paths.
   The teaching point (img can't inherit CSS color → inline SVG or
   filter) is unchanged.

Cross-checked with the actual capture emission in tokenExtractor.ts
(broadened isLogo with structural DOM signals, commit 02f95f95) +
assetDownloader.ts (the SVG content-hash slug pathway). The docs
now match what the code actually does.

Followup commits (separate, per audit punch list):
- Sub-comp root background: rule needs to be in beat-builder-guide
  not just step-5 (a starter template still puts background: on root)
- SFX volume hierarchy in background-music.md still has the old
  0.2-0.35 SFX row + capabilities.md audio example uses 0.8.
2026-06-12 02:21:46 -07:00
2026-06-11 02:40:36 +00:00
2026-06-11 02:40:36 +00:00
2026-06-11 02:40:36 +00:00
2026-06-11 02:40:36 +00:00
2026-06-11 02:40:36 +00:00
2026-03-21 22:43:56 -07:00

HyperFrames

npm version npm downloads License Node.js Discord

Write HTML. Render video. Built for agents.

Quickstart | Showcase | Playground | Catalog | Docs | Discord

HyperFrames demo: HTML code on the left transforms into a rendered video on the right

HyperFrames is an open-source framework for turning HTML, CSS, media, and seekable animations into deterministic MP4 videos. Use it locally with the CLI, from AI coding agents with skills, or as the rendering core behind hosted authoring workflows.

Quick Start

With an AI coding agent

Install the HyperFrames skills, then describe the video you want:

npx skills add heygen-com/hyperframes

Try a prompt like:

Using /hyperframes, create a 10-second product intro with a fade-in title, a background video, and subtle background music.

The skills teach agents the HyperFrames production loop: plan the video, write valid HTML, wire seekable animations, add media, lint, preview, and render. They work with Claude Code, Cursor, Gemini CLI, Codex, and other coding agents that support skills.

For visual design handoff workflows, see the Claude Design guide and Open Design guide.

Manually with the CLI

npx hyperframes init my-video
cd my-video
npx hyperframes preview      # preview in browser with live reload
npx hyperframes render       # render to MP4

Requirements: Node.js 22+, FFmpeg

What You Can Build

Need ideas? Browse the Showcase for finished videos you can watch, read, run, and remix.

  • Product launch videos and feature announcements
  • PR walkthroughs with animated code diffs, narration, and captions
  • Data visualizations, chart races, and map animations
  • Social videos with kinetic captions, overlays, and music
  • Docs-to-video, PDF-to-video, and website-to-video explainers
  • Reusable motion graphics for automated content pipelines

Frame.md

frame.md — your design system, ready for video.

Every brand has a design.md. None of them were written for a camera. frame.md is the missing translation layer: it takes your web-context design spec and inverts it for the frame — the same tokens, the same rules, but rewritten so an AI agent can compose a promo video without guessing at scale or reaching for web chrome.

The output is a DESIGN.md superset your whole toolchain can read. Atoms stay sacred. Composition stays free. Numbers come from the script.

Biennale Yellow
Biennale Yellow
BlockFrame
BlockFrame
Blue Professional
Blue Professional
Bold Poster
Bold Poster
Broadside
Broadside
Capsule
Capsule
Cartesian
Cartesian
Cobalt Grid
Cobalt Grid
Coral
Coral
Creative Mode
Creative Mode

Browse and remix them all at hyperframes.dev/design.

How It Works

Define a video as HTML. Add data attributes for timing and tracks. Use GSAP, CSS, Lottie, Three.js, Anime.js, WAAPI, or your own frame adapter for seekable animation.

<div id="stage" data-composition-id="launch" data-start="0" data-width="1920" data-height="1080">
  <video
    class="clip"
    data-start="0"
    data-duration="6"
    data-track-index="0"
    src="intro.mp4"
    muted
    playsinline
  ></video>

  <h1 id="title" class="clip" data-start="1" data-duration="4" data-track-index="1">Launch day</h1>

  <audio
    data-start="0"
    data-duration="6"
    data-track-index="2"
    data-volume="0.5"
    src="music.wav"
  ></audio>

  <script src="https://cdn.jsdelivr.net/npm/gsap@3/dist/gsap.min.js"></script>
  <script>
    const tl = gsap.timeline({ paused: true });
    tl.from("#title", { opacity: 0, y: 40, duration: 0.8 }, 1);
    window.__timelines = window.__timelines || {};
    window.__timelines.launch = tl;
  </script>
</div>

Preview instantly in the browser. Render locally or in Docker. The renderer seeks each frame in headless Chrome and encodes the result with FFmpeg, so the same input produces the same video.

HyperFrames Stack

HyperFrames is the open-source rendering engine, plus a growing set of tools around HTML-native video creation.

Piece Status What it does
CLI Available Scaffold, preview, lint, inspect, and render local video projects
Core / Engine / Producer Available Parse compositions, drive headless Chrome, encode video, and mix audio
Catalog Available Reusable blocks and components for transitions, overlays, captions, charts, maps, and effects
Agent skills Available Teach coding agents the video-production patterns that generic web docs miss
Studio Available, evolving Browser surface for previewing and editing compositions
AWS Lambda rendering Available Deploy a distributed render stack and drive renders from your laptop or CI
hyperframes.dev Available Community playground for previewing, iterating, sharing, and rendering HTML-native video projects
frame.md Available Invert your design system for the camera — a DESIGN.md superset an agent can compose video from

Catalog

Install ready-to-use blocks and components:

npx hyperframes add flash-through-white   # shader transition
npx hyperframes add instagram-follow      # social overlay
npx hyperframes add data-chart            # animated chart

Browse the catalog at hyperframes.heygen.com/catalog.

Why HyperFrames?

  • HTML-native: compositions are HTML files with data attributes. No React requirement, no proprietary timeline format.
  • Agent-friendly: agents already write HTML, and the CLI is non-interactive by default.
  • Deterministic: same input, same frames, same output. Built for CI, regression tests, and automated rendering.
  • No build step: an index.html composition plays as-is and can be previewed directly in the browser.
  • Adapter-based animation: bring GSAP, CSS animations, Lottie, Three.js, Anime.js, WAAPI, or a custom runtime.
  • Open source: Apache 2.0 license, with no per-render fees or commercial-use thresholds.

HyperFrames vs Remotion

HyperFrames is inspired by Remotion. Both tools render video with headless Chrome and FFmpeg. The main difference is the authoring model: Remotion's bet is React components; HyperFrames' bet is plain HTML that humans and agents can both write easily.

HyperFrames Remotion
Authoring HTML + CSS + seekable animation React components
Build step None; index.html plays as-is Bundler required
Agent handoff Plain HTML files JSX / React project
Library-clock animations Seekable, frame-accurate via adapters Wall-clock animation patterns need care
Distributed rendering Local and AWS Lambda render paths Remotion Lambda, mature cloud renderer
License Apache 2.0 Source-available Remotion License

Read the full comparison in the HyperFrames vs Remotion guide.

Documentation

Full documentation: hyperframes.heygen.com/introduction

Packages

Package Description
hyperframes CLI for creating, previewing, linting, and rendering compositions
@hyperframes/core Types, parsers, generators, linter, runtime, and frame adapters
@hyperframes/engine Seekable page-to-video capture engine using Puppeteer and FFmpeg
@hyperframes/producer Full rendering pipeline for capture, encode, and audio mix
@hyperframes/studio Browser-based composition editor UI
@hyperframes/player Embeddable <hyperframes-player> web component
@hyperframes/shader-transitions WebGL shader transitions for compositions
@hyperframes/aws-lambda AWS Lambda SDK and deployment surface for distributed renders

Community

HyperFrames is used in production at HeyGen, with community examples from teams like tldraw, TanStack, and others in ADOPTERS.md. Open a PR if your team is using HyperFrames.

Development Note

The repo uses Git LFS for golden regression-test baselines under packages/producer/tests/**/output.mp4 (about 240 MB of .mp4 files). If you're cloning the full repo for development, install Git LFS first:

# macOS
brew install git-lfs

# Ubuntu / Debian
sudo apt install git-lfs

# Windows
winget install GitHub.GitLFS

# Then, once per machine
git lfs install

If you only need source files, you can skip LFS content:

GIT_LFS_SKIP_SMUDGE=1 git clone https://github.com/heygen-com/hyperframes.git

License

Apache 2.0

S
Description
Write HTML. Render video. Built for agents.
Readme
760 MiB
Languages
JavaScript 55.3%
TypeScript 44.5%