Design storyboards from real scenes

Create episode-level shots tied to derived scenes and keep shot design separate from media generation.

Start from the screenplay scene

Storyboard shots belong to scenes, and scenes come from screenplay headings. Confirm the scene's action, characters, location, and dramatic turn before designing coverage. A shot list cannot repair a scene whose purpose is still unclear.

The Storyboard dimension offers panel, table, and canvas views. They present the same episode-level shots in different forms: visual sequence, structured comparison, or spatial organization.

Design decisive shots first

Begin with the few shots that define the scene's dramatic logic. The AI assistant is guided to default to roughly three decisive shots and to reconsider plans that exceed six. This is a creative discipline, not a hard UI maximum: establish geography, pressure, and the turn before adding coverage.

Each shot should express subject, framing, camera position or movement, action, and dramatic purpose. Use actual character names and scene facts so generated references and production discussion remain connected to the project.

Chat writes design; generation is a separate action

The Script assistant can read scenes and create or edit shot records. It should not promise that a chat message has generated finished media. Image, video, and audio outputs run through explicit generation tasks with visible cost, status, retry, and asset results.

Review continuity

Check screen direction, eyelines, entrances, prop states, and the relationship between adjacent shots. If the screenplay changes, revisit shots in that episode. Project-level character and location references help consistency, but the shot sequence remains tied to the episode's current scene.