ukimsanov bf8aef029c fix(skill): "alive, not active" rule — kill the opacity-breath failure
Real-AI-test artifact (huly opener): agent entered the app-name labels
("Linear, Jira, Slack, Notion, Docs") staggered, then held them for
~2 seconds while the beam built. To "keep them alive" during the hold,
the agent scheduled `tl.to(labels, { opacity: 1 }, "+=2")` — an
opacity-only breath. At 1920×1080 a 15% opacity oscillation is
invisible; the labels read as frozen for the first ~2s of the video.

Agent's own retro on the failure: "That opacity breath is invisible at
video scale — it's exactly the 'hold with breathing' micro-animation
the playbook tells you not to rely on. So functionally the labels are
frozen for ~2 seconds. It fights the hook."

User's instruction on encoding this as a rule (verbatim): "yes maybe
something like that, just so that AI wouldn't take it as oh damn it
gotta move and do something MOVEE, but just meaning it shouldn't
stay still..."

Encoded the rule in two places with calibrated language — explicitly
NOT "everything must bounce" but "presence requires life":

1. skills/website-to-hyperframes/references/step-3-storyboard.md —
   new "Alive, not active" section in the opener-design block (right
   after the hook patterns, before the CTA section). Names the
   failure mode literally (opacity-only breath → reads as paused
   slide), then lists the four valid continuous-motion patterns
   (drift, camera dolly, wobble, parallax) with magnitudes calibrated
   to be felt-not-watched. Reinforces "one pattern per element, don't
   stack" so the orchestrator doesn't over-spec. Also notes the
   carve-out: deliberate stillness as the CONCEPT (the Negative space
   hook) stays valid — the difference is whether the stillness is
   doing work.

   Also touched the CTA paragraph to extend the rule there — the
   "logo held still after entry" failure is the same failure mode in
   the closing beat.

2. skills/website-to-hyperframes/references/beat-builder-guide.md —
   - Extended landmine #6 (Hold with breathing) to explicitly call
     out the opacity-breath variant as the most common version of
     the failure, with the literal `opacity: 0.85 → 1.0` tween shape
     so workers grep-match it in their own code.
   - New landmine #8 "Alive, not active — no frozen readable text."
     Names the rule, lists the four patterns, says "one per element,
     don't stack" three different ways because the over-correction
     ("MOVEE!") is the second-order failure to head off. Closes with
     a self-check: for every on-screen-for-more-than-1s element, can
     you point at the GSAP tween carrying it through its lifetime?
     If no, add one of the four.

Tone calibration:
- Explicit "fix is NOT make it move more"
- "Goal: the frame feels alive; the viewer can't point at 'the
  motion' if asked" — defines the upper bound (subtlety)
- Magnitudes are floors (4-8px, 1.0→1.04+, ±1.5-3°), not pushes
- Negative space stillness as concept is preserved — the rule names
  unintentional frozen-during-hold as the failure, not all stillness

No code change. The rule is doc-only because the perception gate
(check-rendered-perception.mjs) can't detect "this is visibly frozen
at video scale" — that's a quality judgment, not a binary failure.
Encoded as a sub-agent rule so workers honor it at write time, and
as a storyboard rule so orchestrators name the motion pattern per
element when they spec the beat.

Followups (separate):
- huly creative critique (opener stillness) — addressed by this rule.
- heygen creative critique (CSS cube instead of the real Orb mp4) —
  addressed by commits 570dedbd (capture-video CLI) + e6aa7fed
  (captured videos doc landmine).
2026-06-12 01:28:00 -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%