HyperFrames Studio for Claude Code: Verify Editable Timeline Tracks
Prepare an editable HyperFrames timeline with one track per element kind and a Studio preview. The former HyperFrames Studio skill is retired as a separate install.
中文Setup for Claude Code (current HyperFrames replacement)
Claude Code, Node.js 22 or newer for the local HyperFrames CLI, and a disposable project. The separate hyperframes-studio skill was retired upstream. This example uses its maintained /hyperframes workflow.
- Run `claude plugin marketplace add heygen-com/hyperframes` and `claude plugin install hyperframes@hyperframes` in a terminal. Start a fresh Claude Code session in a scratch project.
- Ask the agent to load /hyperframes and read `skills/hyperframes/references/format.md` and `skills/hyperframes/references/storyboard.md` from the installed bundle or the upstream v0.9.53 tree. Use `npx hyperframes@0.9.53` for the pinned CLI when running the example's checks.
- For historical reading, the original GitHub source below preserves the standalone hyperframes-studio document from before the retirement.
Example task
Ask Claude Code to prepare a 6-second local project with two 3-second scene hosts, a single caption host, and an editable headline variable called headline. Open a local preview and change the headline from 'Morning Notes' to 'Weekly Notes'; verify the caption host stays a separate track.Expected result
The preview shows Weekly Notes with the same scene durations. The timeline has the two scene hosts in order and all caption groups inside the one caption-kind host.
Upstream documentation
Original SKILL.md on GitHub · Apache-2.0 license · Source reviewed
Frequently asked question
How do current HyperFrames skills keep projects editable?
The main skill describes one scene per sub-composition, a separate caption host, predictable IDs, and named variables for content a person can change.