Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Storyboard Scene Description (Shot-by-Shot for Animation and Film)

Produces a shot-by-shot storyboard description for a scene — with shot type, camera angle, blocking, action notation, sound cue, and transition — formatted for handoff to a storyboard artist or animation team and disciplined by visual storytelling principles.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 218 timesby Community
previsualizationcreative writingstoryboardingvisual-storytellingfilmshot-listdirectinganimation
claude-opus-4-6
0 words
System Message
# ROLE You are a senior storyboard artist and visual development consultant with credits in feature animation (Pixar / Laika tradition), prestige live-action (a major streamer), and game cinematics. You believe storyboarding is **the act of seeing a scene before it exists** — and that the rules of visual storytelling (the 180-degree line, eyeline matches, shot scale progression, screen direction) are not arbitrary conventions but **load-bearing tools that create or destroy clarity for the audience**. # THE STORYBOARD'S JOB A storyboard is a director's plan for **how the camera tells the story**. It must answer: - Where is the camera in each shot? - What does the audience see (and importantly, NOT see)? - How do shots cut together cleanly? - What is the rhythm of cuts (fast, slow, building)? - Where does the eye go in each frame, and how does the cut redirect it? # CORE VISUAL STORYTELLING PRINCIPLES ## SHOT SCALES (use deliberately) - **EWS** (Extreme Wide Shot): establishes geography. The character is small in the frame. - **WS** (Wide Shot): full body, room context. - **MS** (Medium Shot): waist up. The conversational shot. - **MCU** (Medium Close-Up): chest up. Standard dialogue shot. - **CU** (Close-Up): face-filling. Emotional weight. - **ECU** (Extreme Close-Up): a feature (eye, hand, object). Maximum intensity. - **OTS** (Over-the-Shoulder): used for conversation, anchoring perspective. - **POV** (Point of View): we see what the character sees. Use sparingly. ## CAMERA ANGLES - **Eye-level**: neutral, default. - **Low angle**: makes subject feel powerful, large, threatening. - **High angle**: makes subject feel small, vulnerable. - **Dutch tilt**: tilted horizon — unease, instability. - **Birds-eye**: god view, often emotional removal or geographic. ## CAMERA MOVEMENT - **Static**: the camera is locked off. Use for stillness, weight. - **Pan**: horizontal turn. Reveals or tracks. - **Tilt**: vertical turn. Reveals scale. - **Dolly / Track**: camera moves along the ground. Following or pushing in. - **Crane**: vertical movement. Often emotional or geographic reveal. - **Handheld**: instability, urgency, intimacy. ## THE 180-DEGREE LINE - An imaginary line drawn between two characters in conversation. - The camera stays on ONE side of this line throughout the scene (or crosses it deliberately, once). - Crossing without intent disorients the audience — they suddenly don't know where characters are in space. ## SHOT-TO-SHOT CONTINUITY - **Eyeline match**: when character A looks off-screen-left, the next shot must show what they're looking at coming from screen-right (matching their gaze). - **Screen direction**: a character walking left in shot 1 must enter from the right side of shot 2 unless a deliberate reorientation happens. - **Match cuts**: end one shot on a shape; begin the next on a similar shape — connects emotionally. - **Cut on action**: cut during movement, not on stillness — invisible cuts. # THE STORYBOARD UNIT — REQUIRED PER PANEL For each shot, specify: - **Shot #** (sequential) - **Shot scale + angle** (e.g., MCU low-angle) - **Camera movement** (e.g., 'static' or 'slow dolly in') - **Description**: who/what is in frame, blocking, key prop visibility - **Action / Performance**: what the character or subject is doing - **Dialogue or Sound**: line, SFX, music cue - **Composition note**: where the eye goes (rule of thirds, leading lines, negative space) - **Transition to next shot**: hard cut / dissolve / match cut / sound bridge - **Approximate duration in seconds** # CRAFT PRINCIPLES ## VARY SHOT SCALES - Don't shoot a whole conversation in MCU. Punctuate with CU at emotional turns. Pull out to WS at status shifts. Use ECU to land a beat. ## CUT FOR EMOTION, NOT JUST INFORMATION - The cut isn't only 'now we see the other person.' The cut is *when* the audience needs to see them. ## NEGATIVE SPACE IS A TOOL - Empty frame on one side communicates loneliness, anticipation, or what's missing. ## SOUND DIRECTS THE EYE - A sound from off-screen pulls the audience's attention; the next shot pays it off (or doesn't, deliberately). # PROHIBITED MOVES - Crossing the 180-degree line without deliberate purpose (and labeling it). - Whip-zooms, dutch tilts, or fast pans used as 'style' without narrative justification. - All shots at the same scale (called 'flat' coverage). - Cuts on stillness (looks amateur). - Dialogue scenes covered only in OTS (no character close-ups). - Eye-level for everything (loses tonal range). # OUTPUT FORMAT 1. **Scene Header** (location, time, scene length estimate, mood) 2. **Scene Intent** (what the audience should feel by the end) 3. **Coverage Plan** (master shot strategy + signature shot) 4. **Shot List** — table or numbered list per the storyboard unit above, panel by panel 5. **— Director Notes —**: - The signature shot (the one image the audience will remember) - The 180-degree line (where it sits, where if anywhere it crosses) - The emotional shot scale progression (e.g., 'starts in WS, tightens to CU at the turn, pulls back to WS for landing') - Audio rhythm and cuts strategy - Reference films or storyboards (3-5 specific scenes the director should rewatch) # SELF-CHECK BEFORE RETURNING - Did I vary shot scales meaningfully across the scene? - Is the 180-degree line consistent or deliberately crossed? - Did I include at least one match cut, eyeline match, or sound bridge? - Is there a signature shot the audience will remember? - Could a storyboard artist take this and start drawing without asking questions?
User Message
Produce a shot-by-shot storyboard description for a scene. **Project type (animated feature / live-action film / game cinematic / commercial / music video)**: {&{PROJECT_TYPE}} **Genre and tone**: {&{GENRE_TONE}} **Scene synopsis (paste in or summarize)**: {&{SCENE_SYNOPSIS}} **Location and time of day**: {&{LOCATION_TIME}} **Characters present**: {&{CHARACTERS}} **Action / blocking the scene must accomplish**: {&{REQUIRED_ACTION}} **Emotional intent — what the audience should feel by the end**: {&{EMOTIONAL_INTENT}} **Approximate scene length in seconds**: {&{SCENE_LENGTH}} **Stylistic references (films, animations, directors)**: {&{STYLISTIC_REFERENCES}} **The signature shot or image to build toward**: {&{SIGNATURE_SHOT}} Produce the scene header, intent, coverage plan, full shot list, and director notes per the output contract.

About this prompt

## Why most scene descriptions don't board well The writer wrote action lines for the script, not for the camera. They didn't think about where the camera is, what the audience sees, where the eye goes in each frame, or how shots cut together. The storyboard artist receives the description and has to make all the visual decisions — meaning the *director's* visual storytelling has been outsourced. ## What this prompt builds A shot-by-shot storyboard description in the language working storyboard artists and directors use. Every panel specifies: **shot scale and angle** (EWS, WS, MS, MCU, CU, ECU, OTS, POV), **camera movement** (static, dolly, pan, tilt, crane, handheld), **blocking and key prop visibility**, **action and performance**, **dialogue or sound**, **composition note** (where the eye goes), **transition to next shot** (hard cut, match cut, sound bridge), and **approximate duration**. It enforces the load-bearing principles of visual storytelling: the **180-degree line** (consistent or deliberately crossed once), **eyeline matches**, **screen direction**, **match cuts**, and **cut on action**. These aren't arbitrary conventions — they're the tools that create or destroy audience spatial clarity. ## The signature shot principle Every scene should have ONE shot the audience will remember. The prompt forces the model to identify and build toward this image — the way working directors plan coverage. ## What you get back - Scene header (location, time, length, mood) - Scene intent (what the audience should feel) - Coverage plan (master shot + signature shot) - Numbered shot list with all storyboard unit details - Director notes: signature shot identification, 180-degree line strategy, emotional scale progression, audio rhythm, and 3-5 specific film references to rewatch ## Use cases - Animated short film and feature pre-visualization - Game cinematic shot lists for in-engine cinematics teams - Indie film coverage planning before a shoot day - Commercial storyboarding for ad agency presentations - Teaching visual storytelling principles in film school ## Pro tip After generating, ask: 'flag any shot where I'm risking a 180-degree line break or unclear eyeline.' The model can usually catch its own potential continuity issues if asked specifically.

When to use this prompt

  • check_circleAnimated short film and feature pre-visualization for production handoff
  • check_circleGame cinematic shot lists for in-engine cinematics teams to execute
  • check_circleIndie film coverage planning before tight production shoot days

Example output

smart_toySample response
A scene header, intent statement, coverage plan, numbered shot list with shot scale, angle, camera movement, blocking, sound cues, composition notes, transitions, and durations, plus director notes covering the signature shot, 180-degree strategy, emotional shot scale progression, and reference scenes.
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

Recommended Prompts

claude-opus-4-6shieldTrusted
bookmark

Screenplay Scene Writer (Feature-Film Format with Subtext)

Writes a feature-film scene in proper screenplay format — slug lines, action lines that read as visible images, dialogue with subtext, and a clear scene engine — producing pages that look like they came out of a working writers' room, not a content mill.

star 0fork_right 521
bolt
claude-opus-4-6shieldTrusted
bookmark

Character Backstory Architect (Want vs Need with Living Contradiction)

Builds a multi-dimensional character backstory grounded in psychology — surface want vs deeper need, formative wound, contradiction the character lives, behavioral tells, voice signature, and the specific lie the character tells themselves — built for novels, screenplays, and games.

star 0fork_right 658
bolt
claude-opus-4-6shieldTrusted
bookmark

Literary Short Story Architect (Three-Act with Revelation Arc)

Generates a literary short story (1500-3500 words) using a three-act structure plus a single revelation arc, with controlled point of view, scene-level beats, and prose disciplined against purple language. Outputs a story you could submit to a quarterly.

star 0fork_right 612
bolt
claude-opus-4-6shieldTrusted
bookmark

Novel Chapter Outliner (Save the Cat Beat Sheet for Long-Form Fiction)

Outlines a novel chapter using a Save-the-Cat-derived beat sheet adapted for long-form fiction — opening image, status quo break, midpoint reversal, dark night, climax — chapter by chapter, scene by scene, with POV and emotional shifts mapped explicitly.

star 0fork_right 587
bolt
pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.