Download for macOS
Skill

hyperframes-studio

@heygen-com 345k installs Trending #25 on Skills.Sh Updated 2026-09-26

Use when building or editing a HyperFrames project that people open in Studio: how the timeline should be laid out so it reads well (one caption track, one element kind per track, every scene a sub-composition) and where captions and key content may sit (safe zones). Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is `creator-editing-recipes.md` in `/hyperframes-core`.

aianimationffmpegframeworkgsaphtmlmcppuppeteer

Install

git clone https://github.com/heygen-com/hyperframes /tmp/hyperframes && ln -s /tmp/hyperframes/skills/hyperframes-studio ~/.claude/skills/hyperframes-studio

From README

HyperFrames Studio conventions Studio draws one timeline row per top-level element. A project that follows the rules below opens as a short, readable timeline; one that does not opens as a wall of unlabeled rows the user cannot edit. These are conventions for what to build. For how to change a clip, follow /hyperframes-core references/creator-editing-recipes.md and never invent a different form of the same edit. Every scene is a sub-composition The root composition holds only timed hosts, media and audio. Any scene with nested structure (a div containing children, a title with a subtitle, a chart) is its own file loaded with data-composition-src, wiring in references/sub-compositions.md. Nested markup left inside the root does not become a row of its own. It hides inside one opaque row that cannot be trimmed or moved part by part. Author as if a structure lint rejects any violation.