to-storyboard
Skill191 starsChanged 8 days agoMITView on GitHub
Use when complete, lineage-valid video scenes need to be translated into HyperFrames frame boundaries, shot moments, transitions, and timing before production.
In this repository10 other files it gives its agents.
- boring-videoSkill
- develop-topicSkill
- record-terminalSkill
- setup-boring-video-skillsSkill
- to-articleSkill
- to-narrationSkill
- to-scenesSkill
- to-spec-beatsSkill
- to-videoSkill
- verysmallwoods-videoSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
start a new frame for a hard edit, independent transition, new visual world, materially different media source, or independently buildable …
- Distinctive: line 15
keep continuous camera movement and shared object state in one frame, describing its internal shot moments.
- Very specific: line 16
Treat each HyperFrames frame as one buildable block.
- Very specific: line 24
Use the scene's world, hero, event, continuity, rhythm, and feasibility as constraints.
- Very specific: line 26
When a frame shows terminal-hosted code entry, shell commands, CLI output, database output, or a TUI, REQUIRED SUB-SKILL: Use …
- Very specific: line 27
Treat canonical HyperFrames fields as authoritative.
- Very specific: line 28
Leave every new frame at status: outline.
- Very specific: line 32
Before presenting STORYBOARD.md or any later revision, follow ../boring-video/references/markdown-review.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
To storyboard
Turn SCENES.md and NARRATION.md into HyperFrames STORYBOARD.md. Scenes define events; the storyboard defines how the viewer sees them.
Process
- Recompute the beats, narration, and scenes artifact digests. Continue only when
NARRATION.mdpoints to the current beats andSCENES.mdpoints to the current beats and narration, with every stored artifact digest matching its file. Open the HyperFrames project and revision recorded bySCENES.md, then load/hyperframesand read its currentreferences/storyboard-format.md. That canonical contract is authoritative for the single currentSTORYBOARD.md. - Choose the HyperFrames frame boundary:
- start a new frame for a hard edit, independent transition, new visual world, materially different media source, or independently buildable unit;
- keep continuous camera movement and shared object state in one frame, describing its internal shot moments.
- Treat each HyperFrames frame as one buildable block. Within its narrative body, write an ordered
Shot momentslist at changes in viewpoint, shot scale, subject action, or information focus. Each moment declares:- moment ID and approximate offset;
- initial state → action → final state;
- camera and attention path;
- narration anchors, or
silent; - handoff to the next moment or frame.
For screen evidence or explanatory visual sequences, read
../to-scenes/references/screen-evidence.md. Express the selected temporal structure as numeric state intervals, dependencies, narration cues, and readable holds in these shot moments, including deliberate simultaneous views. Budget the entire taught operation, including input and confirmed result, within the available narration window. Record any content or timing tradeoff.
- Use canonical metadata wherever the current contract already carries the meaning. Put the document-level
boring_source_scenes_digest,boring_source_narration_digest,boring_hyperframes_project,boring_hyperframes_revision, andboring_artifact_digestexactly once as unknown keys in the global YAML frontmatter, where the canonical parser preserves them underglobals.extra. Computeboring_artifact_digestas SHA-256 of the complete storyboard file after removing only that single digest line. Frame-level workflow extras, such asboring_scene_id, remain on their frames and never carry document digests or project identity. - Use the scene's world, hero, event, continuity, rhythm, and feasibility as constraints. Preserve the cognitive job from
BEATS.md.- Preserve each demonstration's exact content, truth mode, and visible code labels in the relevant shot moments. Do not upgrade an instructional reconstruction into apparent evidence.
- When a frame shows terminal-hosted code entry, shell commands, CLI output, database output, or a TUI, REQUIRED SUB-SKILL: Use
record-terminal. Carry its evidence-backed, seek-safe replay contract and selected visual treatment into the shot moments.
- Treat canonical HyperFrames fields as authoritative. A
boring_*extra supplements the contract; it never restates a canonical field. - Leave every new frame at
status: outline; planning does not create or claim an implementedsrc. Reference relevant scene proofs when a frame's composition depends on an already reviewed visual decision. HyperFrames production owns composition HTML and advances frames tobuiltoranimated. - Audit the sequence: every narration anchor is covered by one or more shot moments, the visual state supports the spoken idea at that moment, intentionally silent moments carry no anchor, frame boundaries follow the rules above, demonstrations preserve their declared truth and labels, and duration allocations fit the target. Screen-state holds and causal reveal intervals must be inspectable in the shot moments; resolve an insufficient budget before marking the plan complete. Treat timing as a plan until HyperFrames Studio confirms it against the built timeline.
- Carry forward the rendered-evidence decisions recorded by
SCENES.mdand project state. Record the current project identity and revision for continuity, but do not mutate the project or build an animatic in this stage.
Before presenting STORYBOARD.md or any later revision, follow ../boring-video/references/markdown-review.md. Review frame boundaries, shot moments, narration mapping, planned durations, and transitions in the authoritative Markdown. HyperFrames Studio later owns playable motion, timing, and transition review.
The storyboard is complete when every frame is an independently buildable outline, its shot moments fully describe the scene event, every narration anchor and planned transition is accounted for, the shared project identity and source revision are recorded, and the Markdown review completion criterion is satisfied. No playable animatic is required before /to-video begins production.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

