hyperframes-studio
Use when working with a person on a HyperFrames project in Studio: first, whether their message asks for a change at all (questions, loose ideas and "don't change anything" get an answer and a plan, not an edit); for a new film, the plan, storyboard and build order that the HyperFrames launch films follow; and 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`.
Why we recommend it: Guides working on HyperFrames video projects in Studio: planning, storyboarding, timeline layout, caption tracks, and safe zones. Covers video editing structure and scripting.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
---
name: hyperframes-studio
description: >
Use when working with a person on a HyperFrames project in Studio: first,
whether their message asks for a change at all (questions, loose ideas and
"don't change anything" get an answer and a plan, not an edit); for a new
film, the plan, storyboard and build order that the HyperFrames launch films follow;
and 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`.
---
**Plugin installs:** Before setup or freshness commands, follow [plugin execution rules](../hyperframes/references/plugin-installation.md) when this skill is inside a HyperFrames plugin. Standalone installs keep the update instructions below.
# 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.
## 0. Talk before you build
Read the message before you open a file. Decide what it asks for:
| The person | You |
| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| names a change, however politely ("make the title bigger", "can you cut the third scene?") | Make it. |
| gives a felt note on the built film ("the intro feels jolty", "it doesn't go long enough") | Find the cause, change the measurable thing, say what the note meant and what moved, and record it per `/hyperframes-creative` `references/storyboard-recipe.md` § 4. |
| asks a question and names no change ("why does the title jump?") | Answer it. Change nothing. |
| says don't change anything, hold, "just thinking", "let's talk" | Change no file, not even a fix you noticed. Offer it in words. |
| brings an idea for this film with no concrete change ("I want the ending to feel bigger") | Propose the change and add it to the plan (below). Change no composition file. |
| asks for a new film | Plan it (§ 5). |
| approves a plan ("build it", "go") | Build what was approved. |
A message that asks a question and names a change gets the answer and the change. Only when you
cannot tell whether it asks for anything is it a conRead the full source on GitHub (opens external page)