Skip to main content
Use this as a fast reference when you are directing agents, cutting timing, making visual layout tweaks, previewing, and sharing HyperFrames projects.

The Fast Loop

Keep the preview running while your agent edits index.html or files in compositions/. The Studio updates automatically, so you can direct the agent, scrub the result, make manual visual tweaks, then repeat. Most production work should feel like this:
  1. Ask the agent for the first cut, scene, caption pass, transition, or cleanup.
  2. Use the Studio preview and timeline to check timing.
  3. Use manual DOM editing for Figma-like layout tweaks: select elements, move them, and adjust visual properties directly.
  4. Ask the agent to clean up or generalize anything you changed manually.
  5. Lint, validate, render, and publish.
Before showing or rendering a project:
For fast iteration renders, use draft quality:
For final delivery:

Terminal Shortcuts

Move around projects quickly:
Common HyperFrames project folders:
Run HyperFrames commands from the project root, where index.html lives. If you are not sure where you are, run pwd then ls. If you see index.html, you are in the right place.

Preview Shortcuts

Start the Studio:
Use a different port if 3002 is already busy:
Inside the Studio, shortcuts are grouped the same way the playbar’s panel groups them — playback first, then work-area markers, view controls, and app-level commands. Open the panel in the playbar for an in-app cheatsheet, a frame-jump input, and live readouts of the in/out points.

Playback

J and L build the classic NLE shuttle: each repeat ramps the playback rate up. Tap K between shuttle bursts to stop. With K held, tapping J or L steps one frame in that direction.

Work area (in / out points)

The in and out points define a work area. When loop is on, both forward and backward playback loop within those boundaries — useful for tightening a transition or scrubbing a single clip without trimming it. The seek bar renders a teal band between in and out, with tick markers at each point. Clear the markers from the panel or with Shift+I and Shift+O.

View

Application

Preview uses the same runtime as rendering, so the visual frame matches the output. If preview stutters on a heavy frame but the render is clean, that is expected — preview plays in real time, render captures one frame at a time.

Agent-Led Editing

Ask the agent to verify visible changes in the browser. For a user-visible edit, a good handoff is:

Manual DOM Editing

In the Studio, you can edit the DOM visually for the final 10% of creative adjustment where dragging is faster than describing. Use manual DOM editing for:
  • moving titles, captions, product cards, logos, and overlays into position
  • adjusting size, spacing, opacity, color, and other visual properties
  • checking composition balance at an exact timestamp
  • making Figma-like placement tweaks
Use agents for:
  • creating scenes from scratch
  • refactoring repeated visual patterns
  • wiring GSAP timelines
  • fixing broken timing, layout overflow, or render errors
  • turning a manual visual tweak into reusable, clean HTML/CSS
After manual DOM edits, ask the agent to inspect the diff and keep the source clean:

CLI Commands Editors Use Most

Timing Cheatsheet

Every visible timed layer should usually be a clip:
Use these attributes like timeline controls: For GSAP animation, register one paused timeline per composition:
If a video cuts off early, check that the GSAP timeline is at least as long as the intended edit. The final tl.set({}, {}, 5) pattern is the fix.

Render Presets

Use WebM for transparent overlays, captions, and lower thirds. Use --docker when you need pixel-consistent output across different machines.

Publish and Share

Use publish when you want to share the editable project, not just the rendered MP4:
Publish zips the current project, uploads it, and prints a stable hyperframes.dev URL. The URL includes a claim token so the recipient can open it, claim the project, and continue editing in the web app.
Publish expects an index.html at the project root. It ignores .git, node_modules, dist, .next, and coverage.

What Agent Browser Is

agent-browser is a browser automation tool for AI agents. It opens Chrome, navigates to your preview, clicks controls, reads page state, and captures screenshots. It is how an agent proves the video preview actually works instead of only saying the code looks right. Typical verification flow:
Use it when you want the agent to open the HyperFrames Studio preview, play or scrub the video, click timeline controls, inspect visible UI text, capture screenshots for review, or record proof of a tested flow. For editor-facing changes, keep npx hyperframes preview running, then have the agent use agent-browser against the local preview URL.

Quick Fixes

Prompt Guide

How to direct AI agents to build better videos

Timeline Editing

Timing, tracks, and GSAP timeline patterns

Common Mistakes

Pitfalls the linter can’t catch

CLI Reference

Full command reference