Creative ProductionAI ChatVideo GenerationPrompt Enhancement

Video producers, marketers, creators, and agencies

Video Storyboarding

Turn an approved message into a scene plan, shot list and route-aware generation briefs. Keep the story, source assets, motion directions and editing notes separate so a producer can evaluate each shot before spending time or budget on production.

Practical guidance

Know what you are making

A storyboard packet with scene purpose, visual direction, motion, reference requirements, audio notes and an edit plan. It is not a finished video, a guaranteed sequence of matching clips or proof that the app exposes a requested control.

Before you start

A message and viewing context

Specify the intended audience, purpose, destination and desired final edit length. Provide approved claims and the action a viewer should understand. Final edit timing is a production target, not an instruction that guarantees a model's clip length or output pacing.

Authorized source material

Inventory the product images, references, logos and footage you are allowed to use. Note missing material and exact details that must stay consistent. Use fictional or authorized subjects; do not assume a generated lookalike grants permission to use a person's identity.

Production and review constraints

Choose the intended format, an owner for final review and a budget you control. Separate text-to-video, image-to-video and video-editing tasks. Check the exact model guide before assuming an image, reference video, audio track or parameter is accepted.

Practical guidance

From input to reviewed output

  1. Define the story in beats

    Ask AI Chat for a beginning, development and ending tied to the approved message. Give each beat one purpose. Establish what the viewer needs to understand without relying on a dense voiceover or unreadable generated text.

    Checkpoint: Remove any scene that adds an unsupported product claim or does not support the core message.

  2. Turn beats into a shot table

    List subject, framing, action, camera direction, source asset and intended transition for each shot. Treat timings as editorial estimates. Put titles, captions and narration in separate columns so generation instructions remain focused on visual motion.

    Checkpoint: A producer should know which assets already exist, which need permission and which are only proposed.

  3. Adapt one shot to one route

    Use the selected model guide to check prerequisites. For an image-to-video route, prepare a suitable starting image and describe a bounded motion relative to it. For another route, rewrite the brief according to its own input contract instead of copying provider-specific settings.

    Checkpoint: Do not paste a full multi-scene screenplay into a single clip prompt and assume the route will edit it.

  4. Review previews against the board

    If you choose to generate or film footage, inspect each returned clip for action, continuity, framing and unwanted changes. Record actual duration and visible defects. Revise one property at a time, or choose a simpler shot rather than repeatedly submitting an unclear prompt.

    Checkpoint: A generated preview is an observation to assess, not an automatic approval of fidelity, timing or usage rights.

  5. Prepare the external edit handoff

    Assemble approved clips, titles, narration, music and captions in your chosen editing workflow. Inspect the complete sequence for pacing and clarity. Keep a list of missing assets and an alternate shot for a concept that cannot be produced reliably.

    Checkpoint: Check the finished export, including audio and captions, rather than approving only the individual source clips.

Technical details

What the workflow does—and does not do

Runway provider guidance; not an app contract

Use route-specific prompting guidance

Runway's Gen-4 guide recommends simple visual instructions, a suitable input image and text focused on motion. It discourages packing many scene changes into one generation. Apply that advice only where relevant; it does not establish EZ Ai Assist's available duration, resolution, seed or camera controls.

App capability boundary

A storyboard is not an editing timeline

Scene tables, transitions and timing notes are planning text. This guide does not establish native timeline editing, automatic assembly, caption rendering or narration synchronization in the app. Use an external editor unless the exact required feature has been separately confirmed in your session.

W3C media guidance

Plan accessible media before production

W3C recommends planning accessibility from the start and distinguishes captions, transcripts and descriptions of important visual information. Put those needs in the board before filming or generation. A prompt requesting subtitles does not establish accurate, synchronized captions in the final exported video.

Editorial verification practice

Measure the result instead of inferring settings

Record actual frame dimensions, clip duration and usable action from returned media. A desired aspect ratio written in prose is not necessarily a supported setting. Continuity between independent generations, synchronized audio and exact on-screen text remain review tasks, not guarantees from the script.

Technical details

Choose by task, not by a universal ranking

These are editorial starting points, not measured comparisons. Check the exact model guide and current app access before using a model; linked catalogs may also contain historical entries.

Writing and shot planning

Use AI Chat to transform the approved message into a shot list and identify production dependencies. Request one action per shot and separate narration from visual instructions.

Tradeoff: A text model's cinematic vocabulary does not prove a video route can perform the requested camera move or maintain continuity.

Explore Anthropic models

Image-led motion

The website's owner-audited guide describes an image-required app mapping. Read it before planning the starting frame and motion. Runway's broader prompting guidance can inform clear movement descriptions.

Tradeoff: Provider documentation and the audited gateway mapping are different evidence. Exact controls and output behavior must be checked for the selected route.

Read the Gen-4 Turbo guide

Comparing another video family

Evaluate another available route when its documented inputs suit the shot better. Preserve the creative intent while rebuilding the input brief around that model's requirements.

Tradeoff: Switching routes is a human planning choice here, not a promise of automatic fallback, identical parameters or matching output style.

Explore Luma AI models

Practical guidance

Create, refine and review

Replace every bracketed placeholder with authorized context. These are original templates, not generated-output demonstrations or generation-tested recipes. Copying does not submit anything or incur a generation charge.

Create a production-aware storyboard

Where to use it: Paste into AI Chat; this is a planning template, not a video-generation prompt.

Storyboard [APPROVED MESSAGE] for [AUDIENCE AND DESTINATION]. Target final edit: [FORMAT AND LENGTH]. Available authorized assets: [INVENTORY]. Return [NUMBER] shots with purpose, visual, action, camera direction, required input, estimated edit time and separate audio/text notes. Label missing assets and uncertain capabilities. Do not invent product claims or promise that one generation will create an edited multi-shot video.

Check: Confirm that the shot count and dependencies fit your production plan before creating media.

Refine one image-led motion brief

Where to use it: Paste into AI Chat, then review the resulting short prompt against the chosen video model guide.

Refine shot [SHOT ID] for [SELECTED MODEL/ROUTE]. Starting image description: [AUTHORIZED REFERENCE]. Desired action: [ONE ACTION]. Preserve [SUBJECT AND COMPOSITION DETAILS]. Return a concise motion description and a separate list of required settings to verify in the actual interface. Use simple positive visual phrasing. Do not add multi-scene edits, dialogue, unsupported controls or exact-duration promises.

Check: Use only supported settings and the reviewed motion text; do not paste the separate planning notes into a generation field.

Review clips using observed evidence

Where to use it: Paste into AI Chat with the board and your own clip-review notes.

Compare [SHOT TABLE] with [OBSERVED CLIP NOTES INCLUDING ACTUAL LENGTHS]. Identify missed actions, continuity changes, framing problems and gaps for the final edit. Cite the shot ID and observation for each finding. Suggest one focused revision or a simpler alternate shot. List caption, transcript and rights checks still needed. Do not claim to watch unavailable media, identify an unverified model or certify the finished video.

Check: Watch the relevant clips again and verify each diagnosis before another generation or edit.

Illustrative example

What a useful handoff could contain

An editorial example of structure, not a generated result, customer case study or measured outcome.

Illustrative three-beat board

For a fictional repair workshop introduction: show the workbench, demonstrate one simple tool movement, then present an invitation card in the external edit. The board describes intent; no footage or media performance is implied.

Shot and asset record

Each row names a starting reference, one action, intended framing and an alternate simpler shot. Desired edit timing and actual returned clip timing are separate fields. Logo fidelity, visible text and subject consistency need manual inspection.

Editor handoff

Deliver approved clips with version labels, title copy, caption/transcript requirements and audio permissions. Include notes about unusable frames or abrupt endings. Leave final-export approval open until someone watches and listens to the assembled result.

Technical details

Check the result before relying on it

Quality checklist

  • Every shot supports the approved message and has a known input requirement or a clearly marked missing asset.
  • Model settings come from the selected route, not assumptions copied from another provider's documentation.
  • Actual clips are reviewed for timing, subject changes, artifacts and continuity before assembly.
  • The final export is checked for legible text, suitable audio, accurate captions, necessary descriptions and applicable permissions.

When the result misses the brief

One prompt contains an entire commercial

Split the idea into single-purpose shots. Plan cuts and transitions in the external edit instead of expecting a short generation to follow a full timeline.

The subject changes between shots

Review authorized reference options for the chosen route and simplify the shot plan. A repeated name or description alone does not guarantee consistent identity across generations.

The requested length is treated as guaranteed

Check the actual route and inspect the returned clip. Adjust the edit plan around usable footage; wording in a prompt does not create a missing duration control.

Provider maximums, picker estimates and actual customer charges are different things. Read the pricing explanation.

Common questions

Before you start the workflow

Does this create a finished edited video?

No. It creates planning material and route-aware briefs. Generating clips is a separate action, and assembly, captions and final export require an appropriate editing workflow unless separately verified app features cover them.

Can I use the same prompt for every provider?

Preserve the creative goal, but check and adapt the input contract. Text-only, image-required and video-input routes are not interchangeable, and documented provider features are not necessarily exposed by the app.

Were the example shots actually generated?

No. The board is an original editorial illustration. No paid generation was used to validate the templates, and no claims are made about actual output quality, continuity, duration or cost.

Evidence and review

Sources & boundaries

The linked technical references were reviewed on . Documentation and app availability can change.

Prompts and storyboard examples are ungenerated editorial material. Runway guidance supports the attributed prompting principles, while app mapping statements refer to the linked owner-audited model guide. W3C supports media-accessibility planning, not certification of a final export. Controls, output quality and permissions require separate verification.

Opening EZ Ai Assist does not prefill these templates or automatically run the workflow. Choose the relevant mode and review your input before submitting it.

Continue exploring

View all use cases