b9be0b2625
* feat(studio,cli): per-frame board comments, self-refreshing storyboard, status-aware preview landing Per-frame comment boxes on the storyboard board batch into .hyperframes/frame-comments.json (a resubmit wins per frame; unconsumed comments on other frames are kept). Submitted-but-unconsumed comments stay visible — a toolbar banner plus a per-tile echo — until the agent consumes the file; the banner also says what to do next (reply anything in the agent chat). The board keeps itself current: GET /projects/:id/signature exposes the watcher-cached project signature, the storyboard payload carries the signature it was derived from, and the view polls at 2s (hidden tabs skipped, re-checked on visibility), refetching in place with no loading flash. Posters bake the signature into their URL so tiles fill in as sketches land and a poster that failed mid-write retries on the next version; the empty state upgrades itself when STORYBOARD.md appears, and its handoff prompt now points the agent at the review loop and uses the parser's real status vocabulary (outline, not planned). preview lands the browser on the storyboard view while the board is the review surface — any frame built, or pure planning (srcs declared, none on disk yet) — and on the timeline once the video is assembled. * feat(skills): the review loop — plan, sketch, build as one shared process hyperframes-core/references/review-loop.md is the single source for the three-pass collaborative review: the plan proposed on a live board (§ 1), wireframe sketches marked built with one layout question (§ 2 — real words on plain blocks, run no CLI; a confirmed board is itself a valid deliverable when the user asked for a storyboard, not a video), the build dressing confirmed layouts (§ 3, worker or inline), and the final look (§ 4). Autonomous runs skip every gate and keep one question before render. The three narrative workflows' Steps 3/4/6 collapse to references plus their sketch stand-ins (captured-asset blocks for product-launch-video, plain code panels for pr-to-video); the confirmed-sketch handoff stays in each frame-worker prompt. general-video plans on a board for multi-scene narrative pieces in collaborative mode — its sketch pass is layout-before-animation with the user watching. The router treats "I want a storyboard" as a process request rather than a route, and closes exploratory intake by recommending a route plus how the run will review. The supporting contracts land next door: the comments channel (silent submit, one reply picks it up, check the file before the words) in brief-contract § 1; the sidecar schema and the built status rung in storyboard-format; the mode question asked first and alone in the three workflows' Step 0. * feat(media-use): user memory — remembered preferences and frozen recipes Two tiers of memory on media-use's existing two-tier storage split. Preferences (lightweight): confirmed brief answers — destination, aspect, language, mode, voice, style preset — recorded to the project's .media/preferences.json (committed, the team inherits it) and promoted to the personal ~/.media/preferences.json once the same value is confirmed in two different projects (a sightings ledger accumulates the cross-project evidence user-side, since project files can't see each other). prefs.mjs get/record; merge reads project-over-user; a changed value restarts its provenance. Recipes (heavyweight): one approved run frozen as a named, versioned bundle — frame.md, the storyboard skeleton (structure kept: durations, transitions, srcs, Video direction; statuses reset to outline; content blanked to per-frame fill-ins naming the beat's role), and the confirmed brief values. Named folders, not content hashes: re-freezing bumps version and archives <name>@v<N>; a freeze is already confirmed, so it promotes to the user tier immediately. recipe.mjs freeze/list/use, plus resolve --type recipe --entity <name> delegating like grade/lut. 16 new node --test cases; the media-use lib suite is 168/168. * feat(skills): wire user memory into the brief and the review loop brief-contract § 2 gains Remembered defaults: read the merged preferences before Round 2 and let a remembered value become the recommended option with a receipt naming its source project. Memory changes the default, never the question — every ask-marked field still gets asked, and what the request says this time beats what was picked last time. Record only what the user actually confirmed (a defaulted voice nobody chose is not an answer; a "go" that accepts the recommended defaults is). The first record announces itself once; after that the receipts carry the reminder. In autonomous mode a remembered value becomes the decided value, receipt included. The three narrative workflows read the remembered defaults before Round 2, record the confirmed answers at the Step 0 gate, record the chosen preset at the Step 2 gate (pr-to-video excepted — its preset is fixed), and fall back to the remembered voice when the request names none. general-video's discovery reads the same defaults. Recipes wire in at both ends: Step 0 checks for a matching recipe before the mode question — one question, plural-aware, and adopting one fills the brief, skips the design step, and drafts the storyboard from the frozen skeleton while every review gate still runs. The review loop's final look (§ 4) offers the freeze once after approval, and the confirmation teaches the recall phrase — the name is something the system reminds the user of, never something they must remember. The router recognizes a named recipe or "like last time" as a route. * docs(skills): the sketch pass names check, not the deprecated validate * feat(skills): intent-layer references — process, route briefs, capability menu, BRIEF.md format * feat(media-use): brief skeleton as the recipe's fourth artifact; flow/storyboard preference keys * feat(skills): the intent layer conducts every brief — workflows execute BRIEF.md * feat(skills): retire the mode preference key; sync catalog surfaces for intent layer * refactor(skills): dedupe router vs intent-layer guidance — one owner per rule * feat(skills): the design ask — own spec, pick by eye from showcases, or defer * docs(skills): the design ask says the honest line on capture routes * feat(skills): product-launch-video absorbs website-to-video as the tour angle * refactor(skills): keep product-launch-video pristine — a tour is brief intent, not a pipeline branch * feat(skills): production loop + genre lenses; general-video goes freeform (route yours, laws hold) * refactor(skills): /hyperframes is the front door - route tables and scope lists leave the workflows * docs(skills): review-loop pass across skill catalog * fix(cli): pass project dir to openStudioBrowser in background-server path * feat(skills): add pitch-round reference - verbalized sampling concept gate * feat(skills): wire pitch round into intent layer - completeness triage + route eligibility * feat(skills): editorial capability recommendations, handoff disciplines, menu-probe split * feat(skills): pitches carry their machinery; source-only-formed requests pitch the telling * feat(skills): companion goes director - ceiling treatment plus blueprint/rule citation discipline * fix(scripts): sandbox npx-leak guard - private npm global prefix keeps npx on the branch CLI * chore(skills): resync manifest hash after formatter pass reflowed general-video tables * fix(skills): recipe freeze reads workflow from BRIEF.md; style_preset records require workflow scope Two holes found by a live companion-run freeze: the agent-supplied --workflow contradicted the run's actual workflow (recipe.json said faceless-explainer, brief-skeleton said general-video), and the style_preset lookup missed because the preference had been recorded under the bare key. - freezeRecipe resolves the workflow from BRIEF.md frontmatter; the flag is a fallback for briefless projects and a contradicting flag is ignored (noted). - recordPreference refuses a bare style_preset — the scoped key is the only writable shape; freeze tolerates legacy bare records via read fallback. - review-loop § 4 / media-use SKILL / brief-format wording follow the machinery.
262 lines
10 KiB
Plaintext
262 lines
10 KiB
Plaintext
---
|
|
title: Quickstart
|
|
description: "Create, preview, and render your first Hyperframes video in under two minutes."
|
|
---
|
|
|
|
Go from zero to a rendered MP4 — either by prompting your AI agent or by starting a project manually.
|
|
|
|
## Option 1: With an AI coding agent (recommended)
|
|
|
|
Install the HyperFrames skills, then describe the video you want:
|
|
|
|
```bash
|
|
npx skills add heygen-com/hyperframes
|
|
```
|
|
|
|
The installer shows a picker. Select the **core set** every project needs — these register as slash commands in Claude Code (Cursor, Gemini CLI, Codex, [Google Antigravity](/guides/antigravity), and [GitHub Copilot CLI](/guides/copilot-cli) load them too):
|
|
|
|
| Core skill (install all) | What it does |
|
|
|--------------------------|--------------|
|
|
| `/hyperframes` | **The entry skill — read it first.** Orients you to the whole surface and routes "make me a video" to the right workflow |
|
|
| `/hyperframes-core` | Composition contract — HTML structure, `data-*` attributes, clips, tracks |
|
|
| `/hyperframes-animation` | All animation + the GSAP / Lottie / Three.js / Anime.js / CSS / WAAPI / TypeGPU runtime adapters |
|
|
| `/hyperframes-creative` | Design direction — palettes, typography, narration, beat planning |
|
|
| `/hyperframes-cli` | Dev-loop CLI — init, lint, preview, render, doctor |
|
|
| `/media-use` | Asset preprocessing — TTS, transcription, background removal |
|
|
| `/hyperframes-registry` | Install catalog blocks and components |
|
|
| `/general-video` | The general authoring workflow — the fallback for any video that doesn't match a specific workflow |
|
|
|
|
The **workflow skills** are optional — add the ones that match your inputs, and `/hyperframes` routes to whichever you've installed: `/product-launch-video`, `/faceless-explainer`, `/pr-to-video`, `/embedded-captions`, `/talking-head-recut`, `/motion-graphics`, `/music-to-video`, `/slideshow`, `/general-video`, `/remotion-to-hyperframes`. See the [skills catalog](/guides/skills) for the full list with one-line "use when" descriptions.
|
|
|
|
<Tip>
|
|
To skip the picker and install everything (core + every workflow) in one shot, run `npx skills add heygen-com/hyperframes --all`.
|
|
</Tip>
|
|
|
|
These skills teach your agent how to write correct compositions, GSAP and runtime-adapter animations, Tailwind v4 browser-runtime styles, captions, and voiceovers. Invoking a slash command loads its context explicitly, which produces correct output the first time — and **starting at `/hyperframes` lets it route your request to the right workflow.**
|
|
|
|
<Note>
|
|
Claude Design uses a different entry path. Open [`docs/guides/claude-design-hyperframes.md`](https://github.com/heygen-com/hyperframes/blob/main/docs/guides/claude-design-hyperframes.md) on GitHub, click the download button (↓) to save it, then attach to your Claude Design chat. It produces a valid first draft you can refine in any AI coding agent. See the [Claude Design guide](/guides/claude-design).
|
|
</Note>
|
|
|
|
### Try it: example prompts
|
|
|
|
Copy any of these into your agent to get started.
|
|
|
|
<CardGroup cols={1}>
|
|
<Card title="Cold start — describe what you want">
|
|
> Using `/hyperframes`, create a 10-second product intro with a fade-in title over a dark background and subtle background music.
|
|
</Card>
|
|
<Card title="Warm start — turn existing context into a video">
|
|
> Take a look at this GitHub repo https://github.com/heygen-com/hyperframes and explain its uses and architecture to me using `/hyperframes`.
|
|
|
|
> Summarize the attached PDF into a 45-second pitch video using `/hyperframes`.
|
|
|
|
> Turn this CSV into an animated bar chart race using `/hyperframes`.
|
|
</Card>
|
|
<Card title="Format-specific">
|
|
> Make a 9:16 TikTok-style hook video about [topic] using `/hyperframes`, with bouncy captions synced to a TTS narration.
|
|
</Card>
|
|
<Card title="Iterate — talk to the agent like a video editor">
|
|
> Make the title 2x bigger, swap to dark mode, and add a fade-out at the end.
|
|
|
|
> Add a lower third at 0:03 with my name and title.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
The agent handles scaffolding, animation, and rendering. See the [prompting guide](/guides/prompting) for more patterns, or the [pipeline guide](/guides/pipeline) for the 7-step structure (DESIGN, SCRIPT, STORYBOARD, …) that AI agents follow for multi-beat videos.
|
|
|
|
<Tip>
|
|
Skills encode HyperFrames-specific patterns — like required `class="clip"` on timed elements, GSAP timeline registration, adapter registries such as `window.__hfLottie`, and `data-*` attribute semantics — that are not in generic web docs. Using skills produces correct compositions from the start.
|
|
</Tip>
|
|
|
|
## Option 2: Start a project manually
|
|
|
|
### Prerequisites
|
|
|
|
- **Node.js 22+** — runtime for the CLI and dev server
|
|
- **FFmpeg** — video encoding for local renders
|
|
|
|
<Accordion title="Install instructions">
|
|
<Steps>
|
|
<Step title="Install Node.js 22+">
|
|
Hyperframes requires Node.js 22 or later. Check your version:
|
|
|
|
```bash
|
|
node --version
|
|
```
|
|
|
|
```bash Expected output
|
|
v22.0.0 # or any version >= 22
|
|
```
|
|
</Step>
|
|
|
|
<Step title="Install FFmpeg">
|
|
FFmpeg is required for local video rendering (encoding captured frames into MP4).
|
|
|
|
<CodeGroup>
|
|
```bash macOS
|
|
brew install ffmpeg
|
|
```
|
|
```bash Ubuntu / Debian
|
|
sudo apt install ffmpeg
|
|
```
|
|
```bash Windows
|
|
# Download from https://ffmpeg.org/download.html
|
|
# or install via winget:
|
|
winget install ffmpeg
|
|
```
|
|
</CodeGroup>
|
|
|
|
Verify the installation:
|
|
|
|
```bash
|
|
ffmpeg -version
|
|
```
|
|
|
|
```bash Expected output
|
|
ffmpeg version 7.x ...
|
|
```
|
|
</Step>
|
|
</Steps>
|
|
</Accordion>
|
|
|
|
### Create your first video
|
|
|
|
<Steps>
|
|
<Step title="Scaffold the project">
|
|
```bash
|
|
npx hyperframes init my-video
|
|
cd my-video
|
|
```
|
|
|
|
This starts an interactive wizard that walks you through example selection and media import. To skip prompts (e.g. in CI or from an agent), use `--non-interactive`:
|
|
|
|
```bash
|
|
npx hyperframes init my-video --non-interactive --example blank
|
|
```
|
|
|
|
See [Examples](/examples) for all available examples.
|
|
|
|
This generates a project structure like:
|
|
|
|
<Tree>
|
|
<Tree.Folder name="my-video" defaultOpen>
|
|
<Tree.File name="meta.json" />
|
|
<Tree.File name="index.html" />
|
|
<Tree.Folder name="compositions" defaultOpen>
|
|
<Tree.File name="intro.html" />
|
|
<Tree.File name="captions.html" />
|
|
</Tree.Folder>
|
|
<Tree.Folder name="assets" defaultOpen>
|
|
<Tree.File name="video.mp4" />
|
|
</Tree.Folder>
|
|
</Tree.Folder>
|
|
</Tree>
|
|
|
|
| Path | Purpose |
|
|
|------|---------|
|
|
| `meta.json` | Project metadata (name, ID, creation date) |
|
|
| `index.html` | Root composition — your video's entry point |
|
|
| `compositions/` | Sub-compositions loaded via `data-composition-src` |
|
|
| `assets/` | Media files (video, audio, images) |
|
|
|
|
If you have a source video, pass it with `--video` for automatic transcription and captions:
|
|
|
|
```bash
|
|
npx hyperframes init my-video --example warm-grain --video ./intro.mp4
|
|
```
|
|
|
|
`hyperframes init` installs AI agent skills automatically, so you can hand off to your AI agent at any point.
|
|
</Step>
|
|
|
|
<Step title="Preview in the browser">
|
|
```bash
|
|
npx hyperframes preview
|
|
```
|
|
|
|
This starts the Hyperframes Studio and opens your composition in the browser. Edits to `index.html` reload automatically.
|
|
|
|
<Tip>
|
|
The dev server supports hot reload — save your HTML file and the preview updates instantly, no manual refresh needed.
|
|
</Tip>
|
|
</Step>
|
|
|
|
<Step title="Edit the composition">
|
|
Open the project with your AI coding agent (Claude Code, Cursor, etc.) — skills are installed automatically and your agent knows how to create and edit compositions.
|
|
|
|
Or edit `index.html` directly — here's a minimal composition:
|
|
|
|
```html index.html
|
|
<div id="root" data-composition-id="my-video"
|
|
data-start="0" data-width="1920" data-height="1080">
|
|
|
|
<!-- 1. Define a timed text clip on track 0 -->
|
|
<h1 id="title" class="clip"
|
|
data-start="0" data-duration="5" data-track-index="0"
|
|
style="font-size: 72px; color: white; text-align: center;
|
|
position: absolute; top: 50%; left: 50%;
|
|
transform: translate(-50%, -50%);">
|
|
Hello, Hyperframes!
|
|
</h1>
|
|
|
|
<!-- 2. Load GSAP for animation -->
|
|
<script src="https://cdn.jsdelivr.net/npm/gsap@3/dist/gsap.min.js"></script>
|
|
|
|
<!-- 3. Create a paused timeline and register it -->
|
|
<script>
|
|
const tl = gsap.timeline({ paused: true });
|
|
tl.from("#title", { opacity: 0, y: -50, duration: 1 }, 0);
|
|
window.__timelines = window.__timelines || {};
|
|
window.__timelines["my-video"] = tl;
|
|
</script>
|
|
</div>
|
|
```
|
|
|
|
Three rules to remember:
|
|
|
|
- **Root element** must have `data-composition-id`, `data-width`, and `data-height`
|
|
- **Timed elements** need `data-start`, `data-duration`, `data-track-index`, and `class="clip"`
|
|
- **GSAP timeline** must be created with `{ paused: true }` and registered on `window.__timelines`
|
|
</Step>
|
|
|
|
<Step title="Render to MP4">
|
|
```bash
|
|
npx hyperframes render --output output.mp4
|
|
```
|
|
|
|
```bash Expected output
|
|
✔ Capturing frames... 150/150
|
|
✔ Encoding MP4...
|
|
✔ output.mp4 (1920x1080, 5.0s, 30fps)
|
|
```
|
|
|
|
Your video is now at `output.mp4`. Open it with any media player.
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Requirements summary
|
|
|
|
| Dependency | Required | Notes |
|
|
|-----------|----------|-------|
|
|
| **Node.js** 22+ | Yes | Runtime for CLI and dev server |
|
|
| **npm** or bun | Yes | Package manager |
|
|
| **FFmpeg** | Yes | Video encoding for local renders |
|
|
| **Docker** | No | Optional — for deterministic, reproducible renders |
|
|
|
|
## Next steps
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Browse the Catalog" icon="grid-2" href="/catalog/blocks/data-chart">
|
|
50+ ready-to-use blocks — transitions, overlays, data visualizations, and effects
|
|
</Card>
|
|
<Card title="GSAP Animation" icon="wand-magic-sparkles" href="/guides/gsap-animation">
|
|
Add fade, slide, scale, and custom animations to your videos
|
|
</Card>
|
|
<Card title="Examples" icon="rocket" href="/examples">
|
|
Start from built-in examples like Warm Grain and Swiss Grid
|
|
</Card>
|
|
<Card title="Rendering" icon="film" href="/guides/rendering">
|
|
Explore render options: quality presets, Docker mode, and GPU acceleration
|
|
</Card>
|
|
</CardGroup>
|