mirror of
https://github.com/hanzoai/frames.git
synced 2026-09-24 00:08:03 +00:00
zooqueen
75094e0d60
@hanzo/frame is taken by the hero video primitive — one full-bleed video element — which has held that name on npm since it shipped. This repo is the video toolchain: a CLI, a renderer, a studio, a player. Plural is what it is, so the CLI publishes as @hanzo/frames and the workspace packages follow it (@hanzo/frames-core, @hanzo/frames-engine, and the rest). The binary stays `frames`, and now actually ships. The manifest mapped it to bin/frames.mjs while the file on disk was bin/hyperframes.mjs, so a global install produced no working command. The paths that name a package to fetch were pointing elsewhere. The update check read registry.npmjs.org/frames, a different author's package, and the npm, bun and pnpm installers would have pulled it over the CLI; the render image installed the upstream hyperframes; scaffolded projects and the docs pinned the unscoped name. All of them now name @hanzo/frames.
1.1 KiB
1.1 KiB
Finalize / repair subagent
Perform snapshot QA and one in-place repair pass. Dispatch only when Step 5 lint, check, or snapshot review reports a defect. The orchestrator owns final approval and render; this agent never renders.
Dispatch context
SKILL_DIR / PROJECT_DIR / proof snapshot times / lint and check output tails, when present.
Flow
- Snapshots — run
npx @hanzo/frames snapshot --at <proof-times>and inspect overflow, off-canvas content, text collisions, empty frames, wrong content, and unreadable motion. - One in-place repair pass — edit
compositions/index.htmlfor the visible issues. Never change a fixeddata-duration; timing is set upstream. - Recheck — rerun
npx @hanzo/frames lint,npx @hanzo/frames check, and the affected snapshots. Return the result to the orchestrator without rendering.
STOP / escalate
Only when the shot is fundamentally wrong (whole content off, needs recomposition) — return to Step 3/4 (re-design + re-build), don't force it with edits. Small fixes never escalate.