agentleFS
OpenMinisOpenMinis/MinisSkills/hyperframes-cli/SKILL.md

hyperframes-cli

Skill584 starsChanged 59 days agoMITView on GitHub

HyperFrames CLI and Minis rendering. Use for: (1) CLI commands — init, lint, preview, render, transcribe, tts, doctor; (2) Minis iOS rendering via hf-render.py (set_viewport + minis-browser-use + ffmpeg, no Chrome required); (3) Website-to-video workflow — capture a URL and produce a professional MP4 in 7 steps; (4) Preview/snapshot compositions at correct resolution. Trigger when user says render, init project, lint, transcribe audio, generate TTS, capture a website for video, or run any hyperframes CLI command.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before any task, verify the environment is ready:

    line 27
  2. Distinctive:

    After installing missing skills, restart the conversation for them to take effect.

    line 56
  3. Very specific:

    Always set_viewport before navigating — otherwise the browser uses the phone's default viewport and the composition renders at the wrong …

    line 118
  4. Very specific:

    Wait for window.__hf ({ duration, seek }) — works with GSAP and pure CSS animations

    line 172
  5. Very specific:

    DURATION must equal the GSAP timeline's actual duration: If ambient animations use repeat, calculate carefully:

    line 195
  6. Very specific:

    No scale wrappers, no transform: scale() on the stage — these break pixel accuracy

    line 213
  7. Very specific:

    Run doctor first if rendering fails.

    line 289

“Common” is measured: kept by at least 6 in 10 of the 50 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HyperFrames CLI

Environment Check (Run First)

Before any task, verify the environment is ready:

python3 /var/minis/skills/hyperframes-cli/scripts/check-env.py

This checks:

  • minis-browser-use — built-in Minis tool for browser control (required for rendering and preview)
  • ffmpeg — video encoding
  • hyperframes skill — composition authoring
  • hyperframes-cli skill — this skill itself (hf-render.py)

If anything is missing, run with --fix to auto-install:

python3 /var/minis/skills/hyperframes-cli/scripts/check-env.py --fix

Or install a specific skill manually:

# From heygen-com/hyperframes (HyperFrames skills)
python3 /var/minis/skills/hyperframes-cli/scripts/install-skill.py \
  hyperframes --repo heygen-com/hyperframes --subdir skills

# From OpenMinis/MinisSkills (community skills)
python3 /var/minis/skills/hyperframes-cli/scripts/install-skill.py notion-hub

If minis-browser-use is missing: it is a Minis built-in tool. Update Minis App to the latest version — it ships with the app and cannot be installed separately.

After installing missing skills, restart the conversation for them to take effect.

Everything runs through npx hyperframes. Requires Node.js >= 22 and FFmpeg.

Workflow

  1. Scaffold — npx hyperframes init my-video
  2. Write — author HTML composition (see the hyperframes skill)
  3. Lint — npx hyperframes lint
  4. Preview — npx hyperframes preview
  5. Render — npx hyperframes render

Lint before preview — catches missing data-composition-id, overlapping tracks, unregistered timelines.

Scaffolding

npx hyperframes init my-video                        # interactive wizard
npx hyperframes init my-video --example warm-grain   # pick an example
npx hyperframes init my-video --video clip.mp4        # with video file
npx hyperframes init my-video --audio track.mp3       # with audio file
npx hyperframes init my-video --non-interactive       # skip prompts (CI/agents)

Templates: blank, warm-grain, play-mode, swiss-grid, vignelli, decision-tree, kinetic-type, product-promo, nyt-graph.

init creates the right file structure, copies media, transcribes audio with Whisper, and installs AI coding skills. Use it instead of creating files by hand.

Linting

npx hyperframes lint                  # current directory
npx hyperframes lint ./my-project     # specific project
npx hyperframes lint --verbose        # info-level findings
npx hyperframes lint --json           # machine-readable

Lints index.html and all files in compositions/. Reports errors (must fix), warnings (should fix), and info (with --verbose).

Previewing

npx hyperframes preview                   # serve current directory
npx hyperframes preview --port 4567       # custom port (default 3002)

Hot-reloads on file changes. Opens the studio in your browser automatically.

🍎 Minis (iOS) Alternative — Preview & Snapshot

Set viewport to composition size first, then navigate. This gives accurate preview at the correct resolution.

# Preview at correct resolution
minis-browser-use set_viewport --width 960 --height 540
minis-browser-use navigate --url minis://workspace/<project>/index.html

# Snapshot at specific timestamps
minis-browser-use execute_js --script 'window.__hf.seek(2.5)'
minis-browser-use screenshot   # saves to /var/minis/browser/

Always set_viewport before navigating — otherwise the browser uses the phone's default viewport and the composition renders at the wrong scale.

Rendering

npx hyperframes render                                # standard MP4
npx hyperframes render --output final.mp4             # named output
npx hyperframes render --quality draft                # fast iteration
npx hyperframes render --fps 60 --quality high        # final delivery
npx hyperframes render --format webm                  # transparent WebM
npx hyperframes render --docker                       # byte-identical
FlagOptionsDefaultNotes
--outputpathrenders/name_timestamp.mp4Output path
--fps24, 30, 603060fps doubles render time
--qualitydraft, standard, highstandarddraft for iterating
--formatmp4, webmmp4WebM supports transparency
--workers1-8 or autoautoEach spawns Chrome
--dockerflagoffReproducible output
--gpuflagoffGPU-accelerated encoding
--strictflagoffFail on lint errors
--strict-allflagoffFail on errors AND warnings

Quality guidance: draft while iterating, standard for review, high for final delivery.

🍎 Minis (iOS) — hf-render.py

npx hyperframes render requires Puppeteer + Chrome (unavailable on iOS). Use the Minis-native renderer instead — it uses minis-browser-use set_viewport to lock the browser to the exact composition size, captures frames at Retina resolution, and encodes with FFmpeg.

One-line render:

python3 /var/minis/skills/hyperframes-cli/hf-render.py <project_dir>

Full options:

python3 /var/minis/skills/hyperframes-cli/hf-render.py <project_dir> \
  --fps 24 \
  --quality high \
  --output /var/minis/workspace/<project>/renders/output.mp4
FlagOptionsDefaultNotes
--fps24, 302430fps increases render time ~25%
--qualitydraft, standard, highstandarddraft=2Mbps, standard=4Mbps, high=8Mbps
--outputpath<project>/renders/output.mp4Output path
--width / --heightpxauto from data-width/heightOverride composition size

How it works:

  1. set_viewport W H — locks browser CSS viewport to composition size
  2. Navigate to minis://workspace/<rel-path>/index.html (supports subdirectories)
  3. Wait for window.__hf ({ duration, seek }) — works with GSAP and pure CSS animations
  4. For each frame: execute_js __hf.seek(t) → screenshot --with-base64 → save JPEG
  5. Frames captured at Retina resolution (e.g. 2880×1620 for 960×540 @ DPR=3)
  6. ffmpeg lanczos-downscale → MP4 (h264_videotoolbox, fallback libx264)
  7. set_viewport --reset always runs — even on error or Ctrl-C

Performance: ~10fps capture (~12s for a 5s@24fps video on iPhone).

Requirements for index.html:

The composition MUST expose window.__hf at the end of its <script> block:

// Required: __hf render protocol
const DURATION = 5.0; // seconds — must match your actual animation length
window.__hf = {
  get duration() { return DURATION; },
  seek(t) { tl.pause(); tl.seek(Math.max(0, Math.min(t, DURATION)), false); }
};
window.__playerReady = true;
window.__renderReady = true;

DURATION must equal the GSAP timeline's actual duration. If ambient animations use repeat, calculate carefully:

// WRONG — glow-gold ends at 0.4 + 2.0*(2+1) = 6.4s, timeline extends past 5s → black frames
tl.to("#glow", { duration: 2.0, repeat: 2, yoyo: true }, 0.4);

// CORRECT — calculate max repeats that fit within DURATION
const DURATION = 5.0;
tl.to("#glow", {
  duration: 2.0,
  repeat: Math.floor((DURATION - 0.4) / 2.0) - 1,  // = 1 repeat, ends at 4.4s
  yoyo: true
}, 0.4);

HTML template rules (required for correct rendering):

  • Fixed width/height on html, body, and #stage — match data-width/data-height
  • No <meta name="viewport"> — the renderer sets viewport externally via set_viewport
  • No scale wrappers, no transform: scale() on the stage — these break pixel accuracy
  • Project must be under /var/minis/workspace/ — the renderer converts the path to a minis:// URL
  • Multi-scene layout: use position:absolute; inset:0 per scene — see note below

⚠️ Minis layout difference from standard HyperFrames: The standard skill says .scene-content should use width:100%; height:100%. In Minis/iOS WebKit, set_viewport sets the CSS viewport width but iOS Safari's height is influenced by system UI, so height:100% on a flex container can exceed the stage height. Content then centers relative to that oversized container and lands outside the screenshot crop.

Fix: for compositions with multiple sequential scenes, give each scene its own position:absolute; inset:0 container (see the hyperframes skill → "Multi-scene compositions" section). For single-scene compositions, width:100%; height:100% is fine.

<!-- Correct HTML structure -->
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<!-- NO viewport meta -->
<style>
  html, body { margin: 0; padding: 0; width: 960px; height: 540px; overflow: hidden; }
  #stage { width: 960px; height: 540px; position: relative; overflow: hidden; }
</style>
</head>
<body>
<div id="stage" data-composition-id="my-comp" data-width="960" data-height="540">
  <!-- content -->
</div>
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js"></script>
<script>
  window.__timelines = window.__timelines || {};
  const DURATION = 5.0;
  const tl = gsap.timeline({ paused: true });
  // ... tweens ...
  window.__timelines["my-comp"] = tl;

  window.__hf = {
    get duration() { return DURATION; },
    seek(t) { tl.pause(); tl.seek(Math.max(0, Math.min(t, DURATION)), false); }
  };
  window.__playerReady = true;
  window.__renderReady = true;
</script>
</body>
</html>

Transcription

npx hyperframes transcribe audio.mp3
npx hyperframes transcribe video.mp4 --model medium.en --language en
npx hyperframes transcribe subtitles.srt   # import existing
npx hyperframes transcribe subtitles.vtt
npx hyperframes transcribe openai-response.json

Text-to-Speech

npx hyperframes tts "Text here" --voice af_nova --output narration.wav
npx hyperframes tts script.txt --voice bf_emma
npx hyperframes tts --list  # show all voices

Troubleshooting

npx hyperframes doctor       # check environment (Chrome, FFmpeg, Node, memory)
npx hyperframes browser      # manage bundled Chrome
npx hyperframes info         # version and environment details
npx hyperframes upgrade      # check for updates

Run doctor first if rendering fails. Common issues: missing FFmpeg, missing Chrome, low memory.

Other

npx hyperframes compositions   # list compositions in project
npx hyperframes docs           # open documentation
npx hyperframes benchmark .    # benchmark render performance

Website → Video Workflow

Turn any URL into a video in 7 steps. Read each step's reference file before executing it.

StepWhatReference
1Capture website (screenshots, tokens, assets)references/website-to-video/step-1-capture.md
2Write DESIGN.md (brand colors, fonts, style)references/website-to-video/step-2-design.md
3Write SCRIPT.md (narration, scene durations)references/website-to-video/step-3-script.md
4Write STORYBOARD.md (per-beat creative direction)references/website-to-video/step-4-storyboard.md
5Generate VO + map word timestamps to beatsreferences/website-to-video/step-5-vo.md
6Build compositions (use the hyperframes skill)references/website-to-video/step-6-build.md
7Lint, snapshot, render, handoffreferences/website-to-video/step-7-validate.md

Visual techniques (SVG drawing, Canvas 2D, 3D, typing, MotionPath, Lottie): references/website-to-video/techniques.md

Quick formats

TypeDurationBeatsNarration
Social ad (IG/TikTok)10-15s3-4Optional
Product demo30-60s5-8Full
Feature announcement15-30s3-5Full
Brand reel20-45s4-6Optional

Landscape: 1920×1080 · Portrait: 1080×1920 · Square: 1080×1080

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.