for custom composition authoring. If the input clearly fits a specialized workflow, prefer it: marketed product →
/product-launch-video
; general site →
/website-to-video
; topic explainer →
/faceless-explainer
; GitHub PR →
/pr-to-video
; existing footage →
/embedded-captions
·
/graphic-overlays
; short unnarrated motion graphic →
/motion-graphics
; Remotion port →
/remotion-to-hyperframes
.
Out of scope
live / at-render-time data, NLE-style editing of a finished video, or producing footage HyperFrames can't capture. Unsure?
Read
/hyperframes-read-first
first.
Build exactly what was asked.
A title card is a title card — not a title card + three supporting scenes + ambient music + captions. If extra scenes or elements would genuinely improve the piece,
propose
them; don't add them silently. For small edits (fix a color, adjust one duration, add one element), skip the planning steps and go straight to the build.
Approach
Discovery — open-ended requests only
For vague, exploratory requests ("make something for our brand", "a cool intro") — understand intent before picking colors:
Audience
— who watches? developers / executives / general consumers?
Platform
— where does it play? social (15s) / website hero / product demo / internal?
Priority
— what matters most? motion quality / content accuracy / brand fidelity / speed?
Variations
— one best shot, or 2-3 meaningfully different options (different pacing, energy, or structure — not just color swaps)?
For specific requests ("add a title card", "fix the timing on scene 3"), skip discovery.
Show more
Installs
771
Repository
heygen-com/hyperframes
GitHub Stars
27.5K
First Seen
Today
Security Audits
Gen Agent Trust Hub
Pass
Snyk
Pass