Build, repair, or continue a complete storyboard workflow from script to clean-board guidance. Use when the user wants story-first boarding grounded in FloobyNooby-style planning, clarity, staging, shot progression, motivated cuts, continuity, rough thumbnails, animatic review, structural revision, key panels, full rough board, and clean-pass rules rather than an analysis-heavy shot list.
Use this skill when the user wants a storyboard that truly tells the story, not just a pile of shots.
This skill treats storyboarding as a full pipeline:
script read -> sequence map -> camera strategy -> scene shot flow -> rough thumbnails -> animatic review -> structure revision -> shot-language refinement -> key panels -> rough board -> clean pass -> final delivery
Read in this order before substantial work:
references/floobynooby-core.mdreferences/workflow.mdreferences/templates.mdRead references/night-nuo-case-study.md when you need a full worked example, a trailer calibration, or a sanity check for object-driven stakes, delayed climax, and story-first lens language.
The full bundled case pack now lives under:
references/night-nuo-case/index.mdUse it for any of these:
Do not use this skill when the user only needs:
Before producing output, identify what stage already exists.
Common cases:
When resuming, preserve any completed stage that is still sound. Replace weak stages, not the whole package by reflex.
Follow the full 15-step pipeline unless the user explicitly asks for a narrower slice.
sequence map.shot flow.See references/workflow.md for the detailed purpose, output, and failure mode of each step.
At every stage, verify:
Use the templates in references/templates.md.
Common deliverables:
sequence drama mapshot flowWhen the user needs proof of how the pipeline should feel in practice, load references/night-nuo-case-study.md.
That reference shows how the workflow handles:
For sharing and quick onboarding, keep this compact example in mind even before opening the full case-study reference.
The reference project follows the full 15-step pipeline like this:
Portable lessons from that case:
The pipeline is successful when the user ends up with a storyboard package that can actually be produced:
If those conditions are not met, keep working the earlier stage instead of forcing polish.