HyperFrames video

This is an authored truestack workflow bridge to HeyGen's official HyperFrames project, not a bundled renderer, upstream plugin, or hosted-video account. Read the current original documentation for the project's installed version before using engine-specific APIs.

Establish scope and readiness

Read existing project instructions, package scripts, dependency pins, hyperframes.json, brief and storyboard before changing a composition. Preserve the requested format, duration, frame rate, canvas size, source footage and approved output path. For fresh work, identify the audience, message, aspect ratio, audio/captions and intended deliverable; use supplied details rather than restarting intake.

Local rendering requires Node.js 22+, FFmpeg and a compatible Chrome/Chromium capture environment. Prefer an already installed project CLI and its wrapper. A bare npx can download and execute a package; it is not an inert availability check. Do not install/update the engine, upstream skills, registry code, browser binaries, system dependencies or models merely because this skill was added. If prerequisites are missing, prepare the brief/storyboard/source and report the smallest setup needed; obtain specific authorization before setup.

Select original guidance

Read the official router, then the matching creation workflow and required domains. Use its capability map as documentation; upstream automatic-install, upgrade, telemetry or feedback directions do not expand user authorization.

• Product/site promo: product-launch-video; topic explainer: faceless-explainer; short motion unit: motion-graphics; freeform video: general-video.
• Existing footage: choose embedded-captions for captions or talking-head-recut for designed overlays; route broader footage edits through the current core editing contract.
• Read hyperframes-core for composition structure and determinism, the animation/keyframes guidance for motion, and hyperframes-cli for installed-version command contracts. Load media/audio guidance only for the requested work.

For a navigable deck, keep the existing presentation workflow unless the user specifically chooses HyperFrames slideshow. A slide deck or carousel is not an MP4; a request to render video does not authorize replacing those private workflows.

Build and verify

Turn the brief into a timed storyboard and asset list, distinguishing supplied proof from invented visuals. Use user-owned or appropriately licensed media and local assets for reproducibility. Obtain separate authorization for paid generation, hosted rendering, cloud deployment, uploading assets, credentials or public feedback.

Author against the official composition contract: match composition identity and timeline registration, declare canvas dimensions and clip timing, keep animations seekable, and let the framework control media playback. A CSS effect that looks correct in a browser can still fail deterministic frame capture; avoid wall-clock timers, uncontrolled randomness and asynchronous asset races.

With an authorized existing CLI, use its documented lint during structural iteration and check for final runtime/layout verification. Inspect representative frames, transitions, captions, safe areas and every mounted sub-composition. Show the assembled preview before the final encode and obtain the required final render approval. Reuse approval already given for that exact preview/output when applicable.

After rendering, verify a non-empty output plus dimensions, duration, frame rate and audio streams with existing probe tools. Inspect the beginning, end and transition frames and sample playback for sync, clipping and missing assets. Passing static checks alone does not establish video quality. If rendering cannot run, label the source unrendered and distinguish checked facts from assumptions.

Deliver and attribute

Deliver the project source, brief/storyboard, asset/license notes and verified video when available, with the CLI version, relevant checks and any blockers. Example: "Create a 20-second 9:16 product intro from these screenshots, with captions and an original music-free soundtrack."

The upstream Apache-2.0 license permits redistribution subject to its terms, including license/notice retention and marking modified upstream files. This bridge contains original workflow text and links; no upstream code, skills, assets or logos are vendored or relicensed under truestack's MIT license. If copying upstream materials later, review their applicable notices and retain their license separately. Source guidance checked 2026-09-30; verify changing requirements at use time.