Storyboard Board

Before final delivery of a substantive authored, revised or generated creative artifact, automatically apply output review. Reuse domain QA in one bounded loop; inspect actual media, preserve accepted locks and stop unchanged on a pass. This does not run for greetings, menus or onboarding questions. When Superpowers is in the skill list, load superpowers:systematic-debugging before diagnosing a reproducible technical defect and superpowers:verification-before-completion before calling a deliverable ready; Studio keeps ownership.

Own the graphic organization of the board, not the time-based sequence. A
board can help people compare selected moments, preserve references, or brief
production. It is not automatically a sequence, a final storyboard animatic,
an approved source frame, an image-to-video carrier, or a generated result.

Begin from supplied materials (when a reference board lacks pictures, search the Open Assets reference base) and classify the board purpose: temporal story,
coverage comparison, or non-temporal reference. Only a temporal story board
needs approved events/order and shot IDs; route its missing time-based decisions
to storyboard-sequence-architect
or label proposed story content provisional. Coverage boards may compare views
of one moment; reference boards may compare identity, wardrobe, product, light,
or material without any events or timing. Use panel IDs only when useful for
mapping, and visible labels only when supplied or authorized. Do not invent a
sequence, dialogue, durations, or a story to fill a reference board.

Read board layout and exact copy for
format selection, panel grammar, legibility, and text locks. Read
reference authority and carriers
to classify each source asset. Read
board delivery and handoffs to
prepare promptability, QA, and downstream use. If the board needs image
generation, transfer the completed visual specification to
image-prompt-architect; respect that
skill's model-aware research and actual tool boundaries.

Apply the conditional public research gate before committing to substantive board design. Search board, film or presentation references when the user asks for them, and fact-check material production claims; synthesize the principle rather than copying a board layout.

When choosing panels, reconciling a locked camera, comparing references or reserving space for captions, use the applied board workshop. Its optional panel map and three-purpose example produce a board specification, not extra story events or an automatically bound video carrier.

Board files

Where Python with Pillow runs, compose the approved board with scripts/board_compose.py board.json --out-dir boards/: frames in a grid with their shot, time, camera, action, audio and supers set in the bundled Inter, as PNG pages and one PDF. Set language to the board's language code (Polish typesetting and „…” supers apply only to pl; other languages keep the text exactly) and labels for localized Audio and Super labels. Labels wrap and move to the next page, never cut; a panel without its frame shows a marked placeholder. Without Python, deliver the board specification and say the file was not composed.

Board brief

For an executable FrameCut project with available assets, use its storyboard command and hashed coverage receipt to obtain actual composition panels and invoke this skill's page compositor. Use preview-frame for individual corrections. Add authored moments for content changes that structural event/keyframe coverage cannot infer; inspect full chronology and every requested deliverable. Reuse the existing project and return panel IDs, receipt and sheets to FrameCut. A receipt is not user acceptance.

For a FrameCut storyboard, the contact sheets visualize the entire timed sequence, from opening to ending. Use Shot Sequence's complete scene-to-panel coverage map; do not reduce it to a few attractive stills or a fixed panel count. Show the designed composition, framing and exact copy in the film's aspect ratio, using source images/planned still states and extra panels for meaningful within-shot changes. Put stable scene/panel IDs, time/interval, action/motion, transition and audio notes outside the image. Group readable pages chronologically; display the actual pages in chat and provide files where supported. A table, prompt or sheet of placeholders is a labelled draft, not the completed visual storyboard. Inspect legibility, image/label pairing and complete coverage, then return the board revision and sheet paths to FrameCut for user feedback. Regenerate affected panels and dependent transitions after corrections, and show the updated full board before acceptance and final rendering. Composing a still board does not require a video sample; a requested sample stays optional.

Capture only what changes the design:

• purpose and audience of the board;
• source sequence/version and selected shots for temporal work; otherwise the reference/coverage purpose and selected properties or views;
• viewing context and delivery size/orientation, if known;
• required panels, ordering, identifiers, labels, and exact copy;
• which information is visual, textual, or intentionally omitted;
• reference assets and authority by property;
• prompt-only, board-generation, review, or handoff request;
• constraints, uncertainties, and one success criterion.

The board grid follows the number and function of panels, reading path, usable
image area, label length, and viewing distance. A 3x2 contact sheet, 16:9
landscape board, or 4:1 strip can be a candidate, never a mandatory default.
For very few panels, use a deliberately paced row or sparse board; for many,
group by scene/beat and use more than one sheet if legibility would otherwise
collapse. Never stretch a contact sheet's cells into a final delivery aspect
ratio.

Lock every visible string exactly: shot ID, title, caption, dialogue excerpt,
duration, or note. Preserve language, spelling, punctuation, numerals, and
diacritics. Do not invent film titles, production credits, dates, camera data,
or explanatory microcopy. If exact typesetting cannot be trusted in a raster,
surface the risk and offer a board prompt plus separate copy deck/spec; do not
pretend the prompt guarantees error-free text. Never silently abbreviate a
required string to fit a panel.

Before release, check that a reader can tell the intended panel grouping/order,
shot or reference identity where relevant, relative scale, and label-to-image
pairing at intended display size. Use
adequate safe margins, alignment, spacing, consistent gutters, contrast, and
intentional image crops. Avoid decorative film-strip clichés, faux UI,
unmotivated stamps, random lens data, and repeated thumbnail variants that add
no planning value. Each panel needs a distinct role for the chosen board purpose.
Repeated locked-camera compositions are valid when they compare approved changes
in action, expression, lighting, or another relevant property; preserve the fixed
camera instead of manufacturing variety. A non-temporal palette comparison is
valid when that comparison is the requested purpose.

When a user asks for both the board and prompts, first establish its purpose and
specification and identify what each requested panel or shot prompt needs. Do not
turn one board prompt into a bundle of generator-specific shot prompts unless
that is requested. A storyboard/keyframe/board image is not automatically the
carrier for each subsequent video request; the exact selected still must be
bound to the relevant request and approved for that role.

For temporal work, use the sequence contract
to avoid mixing beat order with panel layout. Non-temporal boards do not acquire
sequence requirements by using this owner. The final response distinguishes
design specification, prompt, generated board, inspected board, and accepted
board. Creation of a prompt alone proves none of the later states.

Integrated workflow contracts

Use the integrated workflow-kit method for this owner’s artifact fields, bounded review and downstream handoffs. Read Studio integration authority for precedence and the single active route. Preserve this owner’s domain craft and the user’s requested stage.

Production sheets

Use production reference sheets for exact panel metadata, requested labels, readable geometry, product/character state and individual-frame handoff. Preserve one-shot/multiple-panel timing and do not mistake a sheet for a bound video carrier.