Hyperframes Studio

**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 conversation: a wrong answer costs one message; a wrong build costs a long run and a round of notes.

A conversation reply:

- Answer first, in plain words, in a few sentences. - Ask only questions whose answer changes the film, each with a recommended answer and its trade-off ("30 seconds fits a feed; 60 leaves room for the demo"). - When there is an idea to shape: for a new film, directions per `/hyperframes` `references/pitch-round.md`; for an idea about this film, two or three options for the part named. Recommend one. - End with the next step and the word that starts it ("Say build and I'll start").

Keep the plan in the project, not only in the chat: the next message may start a new session that cannot see this one. Add it to STORYBOARD.md the way `/hyperframes-creative` `references/storyboard-recipe.md` § 4 records a round; never overwrite locked frames. If the person asked you to change nothing at all, write nothing: put the plan in the reply and offer to save it.

## 1. 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.

## 2. One caption track

- All captions live on one track: a single sub-composition host (one `data-track-index`) marked `data-track-kind="captions"` that carries every caption group in order. - Never one row per caption group, and