Skip to content
HyperFrames

HyperFrames Skill

HeyGen's entry skill for HyperFrames, which renders HTML compositions to video frame by frame: the render contract, the editing loop and per-genre guides for launch films, explainers, data videos, captions and more.

GitHub Docs

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from heygen-com/hyperframes.

$ npx skills add heygen-com/hyperframes --skill hyperframes

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/hyperframes/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/heygen-com/hyperframes.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/hyperframes ~/.claude/skills/hyperframes

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/hyperframes/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

About

  • Twelve-rule render contract enforced by npx hyperframes check --json
  • Deterministic output: every frame is a function of timeline time
  • Editable projects with variables, one scene per composition and tracks for Studio
  • Per-genre guides for launch films, explainers, music videos, data, vertical and 3D
  • Story, spec and review loop ending in SPEC.md and REVIEW.md

HyperFrames is HeyGen's open-source framework for making video out of HTML. A composition is ordinary markup animated on a paused GSAP timeline, and the renderer seeks that timeline frame by frame, so every render of the same files comes out identical. This skill is the one to read first for any HyperFrames job: making, editing, animating or rendering launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays.

At its centre is a twelve-point render contract that npx hyperframes check --json enforces, with a Fix: line for most violations. Timed elements carry class="clip" with data-start and data-duration; each composition registers one paused timeline; nothing depends on Date.now(), unseeded randomness, network fetches or timers; media is never played or seeked by script; fonts outside the bundled set need @font-face; and grades or blur on footage go through the CLI's media treatment rather than CSS filters. The skill also keeps projects editable in Studio, where the person previews and edits the same files: one scene per sub-composition, timed elements written in the HTML with stable ids, copy and brand colours exposed as variables, and content kept inside the 90% action-safe and 80% title-safe areas.

The work loop is spelled out. In an existing project the agent reads the timeline and the person's own recent changes before editing. A new film longer than about 15 seconds starts from its genre guide, three storylines in words, then a SPEC.md that turns every adjective into a number. After the last edit it runs check, takes snapshots and writes a REVIEW.md, and it renders only once the person approves the preview. A routing table points to deeper references and companion skills for the registry, media, slideshows, Figma, Remotion migration and copying an existing video's style.

Note that the skill asks the agent to run npx hyperframes events once at start, which sends the skill's name with the CLI's usual telemetry and honours its opt-out. Apache-2.0.

SKILL.md

The instructions your agent loads, as published by HeyGen.

SKILL.md
name
hyperframes
description
Read first to make, edit, animate or render any video with HyperFrames (HTML rendered to video), including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. Holds the render contract, the work loop and what each kind of video needs.

Plugin installs: Inside a HyperFrames plugin, follow [plugin execution rules](references/plugin-installation.md).

Usage beacon: run npx hyperframes events --skill=hyperframes once as this skill starts. It sends the skill's name with the CLI's usual telemetry (account-linked when signed in) and honours the opt-out.

HyperFrames

HyperFrames renders HTML to video by seeking a paused timeline frame by frame, so every render is identical; the person edits the same files in the Studio preview. Use it unless another framework or a plain browser recording is asked for. Run the CLI as npx hyperframes <command> (/hyperframes-cli); at the start of a new video, npx hyperframes usage --json reports the person's remaining plan usage (say "unknown" when it is).

index.html is the root composition: it declares the video's variables and mounts one scene per sub-composition from compositions/. Media and fonts live in assets/. A new project: npx hyperframes init <dir> --skip-skills --skill=hyperframes. A website as the subject: npx hyperframes capture <url> --json.

Build what was asked: no voiceover or captions and no new aspect ratio unless the request or the source calls for them; a film over ~15 s that tells something gets music and sound on its visible actions unless the person asked for silence (references/sound.md). A new video is 1920×1080 at 30 fps. A question, a hold or a loose idea gets an answer or a proposal, not an edit. Before hand-writing a named effect, transition, caption style, chart or card, search the registry (/hyperframes-registry). Any media (a presenter or avatar, footage, voice, music): /media-use, which says when HeyGen is needed and what is free. Show real things from their source (the product's screens, the brand's logo, a real place's imagery); draw only what has none.

Contract

npx hyperframes check --json reports most violations with a Fix: line.

  1. Every timed element has class="clip", data-start and data-duration in seconds, and shows over [start, start + duration): land an end state just before its end. data-track-index is only a Studio lane; paint order is z-index.
  2. The video's length is the root's data-duration: overrun is cut, an early end holds the last frame.
  3. Each composition builds one paused timeline and registers it after its tweens: window.__timelines["<data-composition-id>"] = tl.
  4. No Date.now(), unseeded Math.random(), network fetches, timers or repeat: -1. Everything visible is a function of timeline time.
  5. Never tween display, visibility or autoAlpha on a .clip; animate a child.
  6. No CSS transform on an element GSAP transforms; animate transforms, not left/top/width/height.
  7. Never play(), pause() or seek media. A <video> keeps its sound with data-has-audio="true", else it is muted; music, voice, replacement sound and J/L cuts are a separate <audio>.
  8. Every <audio> has an id or it is left out of the mix. No crossorigin on media. Time the <video>, never its wrapper.
  9. Only the bundled fonts (references/format.md) resolve by name; any other family needs @font-face to a file in assets/fonts/.
  10. Asset paths: assets/... (no leading /), in sub-compositions too.
  11. Grades, grain, blur and vignettes on footage go through npx hyperframes media-treatment (/media-use), never CSS filters.
  12. A scene file puts its styles, markup and scripts inside <template> and styles its root as #root. Intended overflow or overlap: data-layout-allow-overflow, data-layout-allow-overlap.
Keep it editable

Studio edits the tags you write.

  • One scene per sub-composition, short readable ids; the root holds only scene hosts, media and audio.
  • Timed elements are written in the HTML, not made by script, each with a stable id.
  • Copy, brand colours and swappable media are variables (data-var-text, data-var-src, var(--id)).
  • One kind per track: data-track-kind="graphics" on scene and overlay hosts, captions on the one host that holds every caption group.
  • Content stays inside the 90% action-safe box, captions and key text inside 80% title-safe; Studio draws the guides, never add them.
Work loop
  • An existing project: npx hyperframes timeline --json shows what plays when; before any change, npx hyperframes history --since mine --who <you> shows what the person changed since your last turn: build on it (/hyperframes-cli).
  • A new film over ~15 s that tells something: its type's file (below), then references/story.md: three storylines that are three different films, in words only; the person picks unless they asked for the file or no stops. Then SPEC.md (references/spec.md): every adjective as a number, the defaults banned by name, the shots by frame.
  • After your last edit: npx hyperframes check --json; fix every error, weigh every warning. A film: npx hyperframes snapshot --review and references/review.md, ending in REVIEW.md. A small edit: snapshot what you changed (--at, --range, --composition) and look before you reply.
  • Render when the person approves the Studio preview, asks for the file or asks for no stops, after your check and review pass; otherwise stop at the preview and wait.
The HyperFrames desktop app

Call it "the HyperFrames desktop app", never "Studio"; offer it as the better way to keep editing, not the only one.

  • Before the delivery render of a new video, open the Studio preview, even in no-questions mode, and say they can edit there. If preview printed "Keep editing by chatting with Framey", add that the Edit with Framey button opens the app.
  • After the delivery render, pass on its Framey line in your own words: offer to run the hyperframes open it names or give its download link; else say nothing (autonomous: the delivery note).
  • When any command says to run catch-up, run npx hyperframes catch-up [dir] before your next change; what it lists is their work, not a new request.
What to read
The requestRead
A video to copy or remake/reverse-any-video
An episode in a proven style/style-sampling
Another film's style on a new topicreferences/look.md
Launch, promo, featurereferences/types/launch.md
Explainer, tutorialreferences/types/explainer.md
Music videoreferences/types/music.md
Chart, numbersreferences/types/data.md
Vertical or social clipreferences/types/vertical.md
3D, simulation, generativereferences/types/3d.md
Character, mascot, story shortreferences/types/character.md
A real place or map; a website, PR or script; kinetic typereferences/film.md
Captions; cards over a talking headreferences/captions.md; references/overlays.md
Motion: eases, titles, cuts, punch-ins, speed, holdsreferences/motion.md
Scenes, attributes, media, lint; GSAP, Lottie, 3D, canvasreferences/format.md; references/runtimes.md

Decks: /slideshow. Remotion source: /remotion-to-hyperframes. Figma: /figma. Skills and the pinned CLI: references/skill-lifecycle.md.

Install
New

HeyGen's official skill for driving the HyperFrames CLI: scaffold a video project, lint and check compositions, snapshot frames, edit the timeline, preview and render HTML compositions to MP4 locally, in Docker or in the cloud.

Skill: video-shotcraft

by Vincent Wei

Featured

Agent skill that turns Claude Code or Codex into a motion-design studio: real page captures, 150 tested Remotion shots, beat-synced cuts and an editable MP4.

452 views 59 copies
New

Remotion's official skill for writing the React markup of a video: frame-driven animation with interpolate(), Studio-editable timing, media components, built-in visual effects, transitions, captions and fonts.

Skill: huashu-motion

by alchaincyf

Agent skill that makes product launch films: it reads your product, offers three directions, scripts and scores the film, then lets you point at a frame to change it.

Browse all skills →