Skip to main content
skill CX Codex

hyperframes · coco-research — Claude Code skill: video from HTML compositions

Entry point for building video, animation and motion graphics in Claude, taking a brief or a URL through to a finished HyperFrames composition.

MIT ★ 328 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add coco-research/coco --skill hyperframes -a claude-code
Open on GitHub

What hyperframes does

The skill acts as a dispatcher. Project state comes first: BRIEF.md supplies the workflow and flow to execute, while hyperframes.json or STORYBOARD.md lets it resume from recorded preferences. A fresh request goes through a short interview about the subject, then lands on one workflow such as /slideshow, /embedded-captions or /remotion-to-hyperframes.

HyperFrames turns HTML into video. Timing lives in data-* attributes on the DOM, the animation runtime can be seeked, and the framework owns media playback. The authoring contract sits in /hyperframes-core and is read before any composition markup gets written. Inputs vary widely: a website URL, a GitHub PR, a Figma design, plain text, existing footage, a music track.

Scaffolded projects pin hyperframes@<version> in package.json, and that pin never moves by itself. Before any render-affecting command the skill probes with npx hyperframes@latest upgrade --project . --check and bumps only when npx hyperframes check passes. A failed check puts the project back on the pinned release.

What it helps with

  • turn a written brief into a promo clip
  • caption existing talking-head footage without recutting it
  • port a Remotion project over to HyperFrames
  • validate and batch-render an existing project
  • build a navigable interactive deck

Example prompts for the agent

  • Make a short promo from the brief in BRIEF.md
  • Add subtitles to interview.mp4 and leave the footage alone
  • Validate the compositions and render the whole project into out/

How to install hyperframes

1Skills CLI (Vercel)

npx skills add coco-research/coco --skill hyperframes -a claude-code

2Manually: put the files in place

~/.claude/skills/hyperframes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hyperframes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hyperframes

How do I install hyperframes in Claude Code?

Run npx skills add coco-research/coco --skill hyperframes -a claude-code. The skill lands at ~/.claude/skills/hyperframes/SKILL.md.

What does hyperframes do?

It is the mandatory entry point for video and animation requests. It reads project state, runs an intent interview when needed and routes the job to the owning workflow, with HyperFrames as the default output framework unless another one is chosen.

What happens to an older project with a pinned CLI version?

The pin in package.json does not advance on its own. Before rendering, the skill checks it with npx hyperframes@latest upgrade --project . --check and bumps only after npx hyperframes check succeeds.

Source text

SKILL.md · MIT
---
name: hyperframes
description: >
  Mandatory entry point: read this first for any request to make, create, edit, animate, or render a
  video, animation, or motion graphic, including a promo, explainer, captioned clip, title card,
  overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also
  use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames
  project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing
  footage, or music. It resumes project state, captures intent when applicable, selects and installs
  the owning workflow, and routes domain capabilities. HyperFrames is the default output framework
  unless the user explicitly chooses another framework for the deliverable or asks only to record a
  browser session.
---

# HyperFrames entry point

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.

## 1. Start from project state

Apply the first matching row; do not evaluate lower state rows:

| State                                                                                                                         | Action                                                                                                                                                                                                      |
| ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Explicit port of existing Remotion source to HyperFrames                                                                      | Read `references/routes/remotion-to-hyperframes.md`, then route directly to that workflow. Skip the intent layer.                                                                                           |
| Specific operation on an existing HyperFrames project: inspect, diagnose, validate, preview, render, publish, or batch-render | Perform only that operation. Skip intent and workflow routing; load `/hyperframes-cli` and any required domain skills.                                                                                      |
| Specific edit to an existing project                                                                                          | Make the edit. Do not run the intent layer.                                                                                                                                                                 |
| `BRIEF.md` exists                                                                                                             | Read `workflow` and `flow`. Execute that workflow; `flow: companion` always executes in `/general-video`. Ask no brief questions.                                                                           |
| No brief, but `hyperframes.json` or `STORYBOARD.md` exists                                                                    | Resume from project files and recorded preferences. Infer the owning workflow from existing artifacts. If it cannot be determined uniquely, ask one routing-only question; do not run the intent interview. |
| Fresh creation                                                                                                                | Run the intent layer — `references/intent-interview.md` — then route once using § 2's table.                                                                                                                |

If a fresh request does not identify the subject or input, ask what the video is about before routing. Check preferences and recipes before asking anything (`references/intent-interview.md`, step 1). A `figma.com` input or a named recipe changes intake, not routing — the interview's "Adapt orthogonal inputs" section handles both.

### Keep the project's CLI current

A scaffolded project pins `hyperframes@<version>` in its `package.json` scripts so renders stay reproducible; the pin never advances on its own, and a pinned run of an older CLI prints no warning about it. When resuming a project whose scripts carry a pin, probe once before the first render-affecting command:

```bash
npx hyperframes@latest upgrade --project . --check
```

The probe is read-only and reports the pin against the latest release; keep the explicit `.` — on older CLI releases a bare `--project` followed by another flag consumes that flag as its directory value. When it reports the project behind — or any CLI output already shows it (the stderr notice `This project pins hyperframes@… (latest …)`, or `_meta.updateAvailable: true` in a `--json` result from a pinned script) — apply with `npx hyperframes@latest upgrade --project .`, then verify with `npx hyperframes check`. A passing check confirms the project's compositions still validate on the new version — not that rendered output is frame-identical to the old pin — so a successful bump is never silent: name the old and new version in the run's summary. A project with no composition yet needs no verification. If the check fails, revert the `package.json` change, continue on the pinned version, and report which version the project stays on and why. Act on the signal rather than relaying it to the user; never leave a bumped pin unverified.

## 2. Route fresh creation

Use the first matching row. Match the requested **deliverable**, not a word or file type mentioned in passing.

| Priority | Request                                                                                                            | Workflow                   |
| -------- | ------------------------------------------------------------------------------------------------------------------ | -------------------------- |
| 1        | Explicitly port an existing Remotion source                                                                        | `/remotion-to-hyperframes` |
| 2        | Author a presentation, pitch deck, or navigable interactive deck                                                   | `/slideshow`               |
| 3        | Add plain captions or subtitles to existing talking-head footage without changing it                               | `/embedded-captions`       |
| 4        | Add designed graphic overlays to existing talking-head, interview, or podcast footage without changing the footage | `/talking-head-recut`      |
| 5        | Build a beat-synced video from a music track, with no narration or website capture                                 | `/music-to-video`          |
| 6        | Create an explicitly short, unnarrated, motion-first unit, typically under 10s                                     | `/motion-graphics`         |
| 7        | Explain a GitHub pull request or code change from a PR reference                                                   | `/pr-to-video`             |
| 8        | Market or showcase a website, product site, app, or company from a URL or site-specific brief                      | `/product-launch-video`    |
| 9        | Explain a topic, article, or notes with invented visuals and no product or site capture                            | `/faceless-explainer`      |
| 10       | Any other custom video or composition                                                                              | `/general-video`           |

Before finalizing the route, read `references/routes/<workflow>.md` — one small file per route: the canonical input/output/trigger contract (available before lazy-installed workflow skills are present) plus that route's interview entry. If the candidate does not satisfy its contract, continue routing instead of forcing the match. Read only the matched route's file.

### Resolve common ambiguities

- A short animated title, logo sting, stat hit, chart hit, map hit, or standalone lower-third is `/motion-graphics` when it is unnarrated and motion is the message. A static title card, narrated sequence, longer montage, or custom loop is `/general-video`.
- An explicitly short motion graphic may use a URL, tweet, article, or screenshot as source material. A generic "make a video from this site" request is `/product-launch-video`.
- Existing footage with captions routes to `/embedded-captions`; footage with designed information cards routes to `/talking-head-recut`. Retiming, reordering, recoloring, reframing, or remixing footage is a custom edit and falls through to `/general-video`.
- A music file selects `/music-to-video` only when its beat grid drives the piece. Music used as a bed does not override the subject-matched route.
- "I want a storyboard" changes the review process, not the workflow. With no other routing signal, use `/general-video`. A confirmed sketched board may itself be the requested deliverable; the review loop defines that stop point.
- Specialized narrative workflows support up to about 3 minutes and are strongest around 30–90s. Route a clearly longer piece to `/general-video`. Length never overrides an explicit port, deck, caption, overlay, or music-driven deliverable.

## 3. Route once, then leave

For fresh creation the intent layer (`references/intent-interview.md`) runs the full conversation — memory, triage, pitch round, must-haves, run-shape, hand-off — and **ends by writing `BRIEF.md`. The brief is the only routing artifact the workflow reads**; nothing later re-opens this skill or the interview. Answer every later "what did the route require?" from `BRIEF.md`.

## 4. Install and enter the workflow

Before reading the selected workflow, install or refresh it and the core domain skills:

```bash
npx hyperframes skills update <workflow-name>
```

Use the bare name without `/`. If the command fails, surface the error; do not reconstruct the workflow from memory. Everything else about installation — the core-vs-lazy split, what `init` refreshes, diagnosis, CI opt-out, and the no-CLI fallback — lives in `references/skill-lifecycle.md`.

## 5. Load domain skills on demand

| Need                                                                                                                | Skill                    |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| Composition structure, timing attributes, tracks, variables, determinism                                            | `/hyperframes-core`      |
| Motion rules, scene blueprints, transitions, runtime adapters                                                       | `/hyperframes-animation` |
| Seek-safe GSAP, CSS, Anime.js, WAAPI, FLIP, paths, masks, SVG, 3D keyframes, or `hyperframes keyframes` diagnostics | `/hyperframes-keyframes` |
| Design specs, concept, palette, typography, narration, beat planning                                                | `/hyperframes-creative`  |
| Images, icons, logos, audio, captions, grades, LUTs, reusable media                                                 | `/media-use`             |
| Init, lint, check, snapshots, compare, batch render, Studio, render, publish, or diagnostics                        | `/hyperframes-cli`       |
| Registry blocks and components                                                                                      | `/hyperframes-registry`  |
| Figma assets, tokens, components, or storyboard frames as reconstructed motion                                      | `/figma`                 |

Broad feedback about how photographic media looks or behaves also routes to
`/media-use`, even when the user never says “color grading” or “effect”: fix
dark/flat/boring footage, stylize a clip, hide a face, or improve a media
reveal. Read `../media-use/references/media-treatments.md` before editing a
treatment; it governs how footage is treated, never whether media may be used.
Do not substitute a generic LUT, CSS filter/overlay, or opacity tween for an
existing canonical treatment primitive. Keep text/layout/motion-only edits in
their owning domain.
During a build with important photographic media, include one grounded
media-polish scan in the final quality pass; leaving suitable media unchanged is
a valid result.

Domain skills never take ownership of the end-to-end deliverable. Load only what the active workflow needs.

© coco-research · MIT · coco-research/coco

Similar skills

All skills for Design →

hyperframes by other authors comes first.

hyperframes heygen-com hyperframes — a Claude Code skill that renders video from HTML by seeking a paused timeline frame by frame. CX Codex +1 1,600,000installs hyperframes boraoztunc Build HyperFrames HTML video compositions with animated scenes, captions, voiceovers, audio-reactive effects, and transitions. CX Codex +1 230installs hyperframes calesthio This skill routes video and motion requests through HyperFrames, which renders compositions from HTML. Use it for editing, animation, captions, and finished video. CX Codex +1 ★ 78,316repo stars motion-graphics Liamrjohnston Runs preflight asset research and enforces strict gate checks before authorizing video composition builds. Designed for authentic product motion graphics. CX Codex +1 1,900installs remotion-to-hyperframes heygen-com remotion-to-hyperframes ports video code from Remotion, Motion Canvas, Lottie, or 3D renders into HyperFrames. Runs automated frame-by-frame diffs against the original video file to catch visual drifts. CX Codex +1 651,200installs react-animation notedit react-animation — a collection of React components for building videos in Remotion with pre-built animations and visual effects. Organized by aesthetic style: elegant, modern, luxury, retro, dramatic, and abstract. CX Codex +1 191installs hyperframes-registry official HeyGen hyperframes-registry helps install and wire registry blocks and components into HyperFrames video compositions. CX Codex GP ChatGPT +1 2installs apple-launch-film charlie947 apple-launch-film builds an Apple-style Mac launch film entirely in code: menu bar, notch, widgets and gradient wallpapers. Useful when you need a launch video without screen recording or After Effects. CX Codex +1 3,300installs explainer-engaging Barty-Bart explainer-engaging is a skill that builds a 10–30 second video with sound: one object travels through a product interface without cuts as the camera follows it and reveals the full path. CX Codex +1 3,000installs

From the same set82

The whole set →
pmstudio-meeting-notes pmstudio-meeting-notes converts call transcripts into structured Markdown meeting notes. Cross-references people against stakeholder tables, logs decisions, and flags PRD updates. CX Codex +1 ★ 328repo stars hyperframes-cli The hyperframes-cli skill guides HyperFrames projects from composition checks to preview and rendering. It also helps diagnose build and render failures. CX Codex +1 ★ 328repo stars _index _index — a Claude slash command that reads, searches and triages Outlook mail through subcommands such as unread, summary and triage. CX Codex +1 ★ 328repo stars brain:wiki brain:wiki is a Claude Code skill that searches, generates, and merges articles about people, systems, and teams from a distributed knowledge graph. CX Codex +1 ★ 328repo stars code-verification code-verification runs a mechanical 7-category audit on code changes. Catches temporal dead zone bugs, import mismatches, dead code, and React state mistakes. CX Codex +1 ★ 328repo stars openai-agents Guides building text and voice workflows with the OpenAI Agents SDK, schemas, and multi-agent handoffs without common runtime traps. CX Codex +1 ★ 328repo stars engineering-super-intelligence engineering-super-intelligence — a Claude skill with 70 named engineers in 11 cells, invoked through /SI-Eng-* slash commands when an architecture, cost or security decision needs a documented stance. CX Codex +1 ★ 328repo stars project-docs project-docs scaffolds a standard 16-document folder ecosystem, sets up CLAUDE.local.md project memory, and audits repo structure against baseline documentation rules. CX Codex +1 ★ 328repo stars

Project sponsors

Companies that keep this analytics open