Somansh Reddy
7acabbcdeb
* docs(guides): resolve the fidelity contradiction (preserve substance, adapt form) The guide called the rebuild 'lossy by nature' while the checklist demanded 'content match the brief exactly', with no rule for what to preserve vs adapt. On a live import CD kept fonts/palette/hero but genericized the source's real figures (2.4M signals/sec, +240% spike) into vague phrases. Resolve around one principle: substance (real copy, exact palette/fonts, distinctive figures/data, product names, signature visuals) is preserved verbatim; only the form (static page to timed multi-scene motion) adapts. * test(guides): pin the Send-to fidelity contract against silent regression Address review on #2620: the resolved 'preserve substance, adapt form' instruction is load-bearing LLM-facing prompt text, but validate-docs only proves syntax. Add a semantic pin (mirroring packages/cli figma skillContent.test.ts) asserting the three positive concepts are present and the two retired contradictory phrases ('lossy by nature', 'content match the brief exactly') cannot silently return. * style(guides): oxfmt the Send-to fidelity-contract test Wrap the readFileSync call to oxfmt form (printWidth 100); unblocks required Format + its preflight/preview-regression cascade on #2620.
hyperframes
CLI for creating, previewing, and rendering HTML video compositions.
Install
npm install -g hyperframes
Or use directly with npx:
npx hyperframes <command>
Requirements: Node.js >= 22, FFmpeg
Commands
init
Scaffold a new Hyperframes project from a template:
npx hyperframes init my-video
cd my-video
preview
Start the live preview studio in your browser:
npx hyperframes preview
# Studio running at http://localhost:3002
npx hyperframes preview --port 4567
render
Render a composition to MP4. Run from the project directory; the positional
argument is the project directory (not a file), so render the project's
index.html directly, or point at a specific composition file with -c:
npx hyperframes render -o output.mp4
npx hyperframes render -c ./my-composition.html -o output.mp4
lint
Validate your Hyperframes HTML:
npx hyperframes lint ./my-composition
npx hyperframes lint ./my-composition --json # JSON output for CI/tooling
npx hyperframes lint ./my-composition --verbose # Include info-level findings
By default only errors and warnings are shown. Use --verbose to also display informational findings (e.g., external script dependency notices). Use --json for machine-readable output with errorCount, warningCount, infoCount, and a findings array.
compositions
List compositions found in the current project:
npx hyperframes compositions
benchmark
Run rendering benchmarks:
npx hyperframes benchmark ./my-composition.html
doctor
Check your environment for required dependencies (Chrome, FFmpeg, Node.js):
npx hyperframes doctor
browser
Manage the bundled Chrome/Chromium installation:
npx hyperframes browser
info
Print version and environment info:
npx hyperframes info
docs
Open the documentation in your browser:
npx hyperframes docs
upgrade
Check for updates and show upgrade instructions:
npx hyperframes upgrade
npx hyperframes upgrade --check --json # machine-readable for agents
Documentation
Full documentation: hyperframes.heygen.com/packages/cli
Related packages
@hyperframes/core— types, parsers, frame adapters@hyperframes/engine— rendering engine@hyperframes/producer— render pipeline@hyperframes/studio— composition editor UI