Every SKILL.md already declared the new name — name: frames, frames-cli, frames-core, and so on — but the directories were never moved, so the tree carried frames-* in content and hyperframes-* on disk. Everything that resolves a skill by path missed: the core-skill list, the plugin marketplace pin, and the docs the CLI reads at runtime. Eight tests failed on main because the files they open do not exist. The directories now match what the files say they are, and the guide the claude-design contract reads takes the name that contract already used.
@hanzo/frames
CLI for creating, previewing, and rendering HTML video compositions.
Install
npm install -g @hanzo/frames
Or use directly with npx:
npx @hanzo/frames <command>
Both install the frames command.
Requirements: Node.js >= 22, FFmpeg
Commands
init
Scaffold a new Hyperframes project from a template:
npx @hanzo/frames init my-video
cd my-video
preview
Start the live preview studio in your browser:
npx @hanzo/frames preview
# Studio running at http://localhost:3002
npx @hanzo/frames 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 @hanzo/frames render -o output.mp4
npx @hanzo/frames render -c ./my-composition.html -o output.mp4
lint
Validate your Hyperframes HTML:
npx @hanzo/frames lint ./my-composition
npx @hanzo/frames lint ./my-composition --json # JSON output for CI/tooling
npx @hanzo/frames 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 @hanzo/frames compositions
benchmark
Run rendering benchmarks:
npx @hanzo/frames benchmark ./my-composition.html
doctor
Check your environment for required dependencies (Chrome, FFmpeg, Node.js):
npx @hanzo/frames doctor
browser
Manage the bundled Chrome/Chromium installation:
npx @hanzo/frames browser
info
Print version and environment info:
npx @hanzo/frames info
docs
Open the documentation in your browser:
npx @hanzo/frames docs
upgrade
Check for updates and show upgrade instructions:
npx @hanzo/frames upgrade
npx @hanzo/frames upgrade --check --json # machine-readable for agents
Documentation
Full documentation: frames.hanzo.ai/packages/cli
Related packages
@hanzo/frames-core— types, parsers, frame adapters@hanzo/frames-engine— rendering engine@hanzo/frames-producer— render pipeline@hanzo/frames-studio— composition editor UI