DVP · Core Suite · Workflow Guide

The AI
Filmmaker's
Pipeline

Five tools. One workflow. From a reference image or idea to a complete, platform-ready shot list — with visual consistency locked across every frame and your best prompts saved into a reusable project bible. Character Sheet Builder remains an optional character-prep tool when continuity is critical.

Start with FrameDNA → See the Workflow
The 5-Step Pipeline
01 FrameDNA → 02 CinePrompt → 03 Consistency Keeper → 04 Script to Shots → 05 CineBible
Step One

Extract Your Visual DNA

Start with a reference image — a film still, location photo, or mood board. FrameDNA reads the cinematography and outputs a platform-ready prompt in seconds.

01
Tool
FrameDNA
Drop any image. FrameDNA extracts the shot type, camera movement, lighting style, color grade, and mood — then builds a prompt optimized for your chosen AI platform.
What you do
  • Drop a reference image — film still, photo, or screenshot
  • Select your target platform
  • Review the extracted cinematography DNA
  • Click Open in CinePrompt to continue building
Pro tips
Director's eye
Use film stills from movies with a look you want to replicate. FrameDNA reads the lighting and color grade directly — it's faster than writing descriptions from scratch.
When to skip this step
If you already know exactly what you want, go straight to CinePrompt and describe your scene manually.
Open FrameDNA →
Step Two

Build Your Cinematic Prompt

CinePrompt is your prompt architect. Choose from hundreds of cinematic parameters — camera, lens, lighting, color grade, texture — or translate any existing prompt across platforms instantly.

02
Tool
CinePrompt
Two modes: Build a prompt from scratch using cinematic dropdowns, or paste an existing prompt and Translate it to any other platform automatically. Supports 9 platforms.
BUILD mode — what you do
  • Describe your scene or subject in the text field
  • Select platform, camera, lens, aperture, shot type
  • Choose lighting, color grade, film texture, and format
  • Click Generate — get a platform-optimized prompt
  • Click Lock with Consistency Keeper to continue
TRANSLATE mode — what you do
  • Paste any existing prompt — any platform, any format
  • Select your source platform
  • Check the target platforms you want
  • Click Translate — AI rewrites for each platform's syntax
Key insight
Every platform has a different prompt dialect. Kling wants comma-separated descriptors. Runway wants evocative sentences. Veo wants director instructions. Translate mode handles all of this automatically.
Supported platforms
Kling 3.0 Runway Gen-4.5 Veo 3.1 Luma Dream Machine Hailuo / MiniMax Seedance 2.0 Midjourney 8 Grok Nano Banana 2 Pika 2.5 WAN 2.1
Open CinePrompt →
Step Three

Lock Visual Consistency

The hardest problem in AI video: keeping your character, scene, and style identical across multiple shots. Consistency Keeper solves this by anchoring a Visual DNA lock across every prompt it generates.

03
Tool
Consistency Keeper
Define your subject once. Describe color grade, camera style, and lighting. Set how many shots you need. The AI generates a full set of locked, consistent prompts — each tailored to your chosen platforms.
What you do
  • Write a detailed Visual DNA anchor — describe your subject or location completely
  • Set color grade, camera style, and lighting — these stay locked across all shots
  • Select your target platforms
  • Set shot count (1–6 per generation)
  • Click Generate Consistent Prompts
  • Export a Reference Card or send directly to Script to Shots
How consistency works
Visual DNA Lock
The more detail you put in the anchor, the stronger the lock. For a character: exact clothing, hair color, build, age, accessories. For a location: architecture, time of day, specific light sources, surface materials.
Reference Card
Download the Reference Card as a .txt file and paste it into your project notes. It becomes your style bible — share it with collaborators or use it to re-generate more shots later.
Character-first projects
If your film depends on one lead character appearing across many shots, use Character Sheet Builder before or alongside this step. It is optional, but it gives you a clean 7-panel turnaround and prompt block to strengthen consistency.
Open Consistency Keeper →
Step Four

Build Your Shot List

Paste a scene, script excerpt, or story beats. Script to Shots breaks it into individual shots and writes a platform-optimized prompt for every one — ready to generate in Kling, Runway, or wherever you work.

04
Tool
Script to Shots
Any format works — screenplay, prose, bullet points, rough notes. Set the pacing, camera style, and target platforms. Get a complete shot list with one prompt per shot per platform.
What you do
  • Paste your script or scene text
  • Set visual style (or leave blank for auto-detection)
  • Choose pacing — minimal, standard, or detailed
  • Select your target platforms
  • Click Generate Shot List
  • Copy individual prompts or download the full list
Tips for best results
From Consistency Keeper
Use the "→ Script to Shots" button in Consistency Keeper to send your Visual DNA and style directly here — the tool pre-fills your scene and style automatically.
Pacing guide
Minimal = 1–3 key shots per beat (action, commercial). Standard = 3–5 shots (drama, narrative). Detailed = full coverage of every moment (cinematic, complex scenes).
Open Script to Shots →
Step Five

Save the Project Bible

CineBible is where the workflow becomes reusable. Save the prompts that worked, attach references and character notes, and keep each project's visual memory in one place so future revisions do not drift.

05
Tool
CineBible
A project vault for recipes, references, and characters. Save winning prompts from CinePrompt or Consistency Keeper, track platform-specific IDs, and build a continuity record you can reopen later.
What you do
  • Save your strongest prompts from CinePrompt or Consistency Keeper into a project vault
  • Attach characters, reference IDs, thumbnails, seeds, ratings, and notes
  • Keep multiple versions so you can compare iterations and avoid visual drift
  • Export the vault when you want a portable production bible for collaborators or backup
How it should work in the flow
Not a starting tool
CineBible is the memory layer, not the ideation layer. Use it after you have built prompts, references, or consistency locks worth keeping.
Best use
Treat CineBible as the place you save approved looks, tested prompt recipes, character continuity notes, and reusable reference data for the whole production.
Open CineBible →
Quick Start

Your First Project in 15 Minutes

New to the suite? Follow this checklist. You'll go from zero to a full shot list with consistent prompts on your first run, then save the winning setup into CineBible.

1
Set up your API key
Get a free key at console.anthropic.com. Paste it into any tool — it saves automatically and works across the entire suite.
2
Find a reference image
A film still that matches your intended look. Drop it into FrameDNA and hit "Open in CinePrompt" — your visual style is captured in seconds.
3
Build or refine your prompt
In CinePrompt, refine the scene description, adjust camera and lighting settings, then click "Lock with Consistency Keeper" to pass your prompt forward.
4
Lock your visual style
In Consistency Keeper, describe your subject in detail and set your style lock. Generate 3–5 consistent prompts. Download the Reference Card. If it is a character-heavy project, Character Sheet Builder is a useful optional prep step here.
5
Build your shot list
Click "→ Script to Shots" from Consistency Keeper, or paste your scene text directly. Get one prompt per shot, per platform.
6
Save the approved recipe
Send your strongest prompt recipes, references, and character notes into CineBible so the project has a persistent memory you can reopen later.
7
Generate your shots
Copy prompts into Kling, Runway, Veo, or your platform of choice. Your Reference Card and CineBible vault keep the visual style consistent across every generation session.
FAQ

Common Questions

Do I need to use all five tools every time?
No. The pipeline is modular. If you already have a strong prompt, go straight to Consistency Keeper. If you're working from a script, go straight to Script to Shots. CineBible is where you save the approved work, and Character Sheet Builder is optional when character continuity matters.
Is my API key secure?
Yes. Your key is stored only in your browser's localStorage — it never touches DVP servers. You're billed directly by Anthropic for any Claude API usage (typically $0.01–$0.05 per generation). We have no access to your key or usage data.
Why do different platforms need different prompt formats?
Each AI model was trained differently. Kling responds to comma-separated descriptors and rewards camera movement first. Runway prefers evocative, period-separated sentences. Veo wants director-style instructions. Seedance anchors the subject in the first 20 words. Using the wrong format on any platform reduces quality significantly — that's why CinePrompt builds and translates platform-specifically.
What's the best platform for beginners?
Start with Kling 3.0 — it's the most forgiving with prompts and produces high-quality photorealistic video. Runway Gen-4.5 is excellent for stylized or VFX-heavy work. Veo 3.1 is best for physics-accurate motion and native audio. Try all three with the Translate tool to compare results from the same prompt.
How do I maintain consistency across sessions?
Download the Reference Card from Consistency Keeper after every project. It contains your full Visual DNA lock — subject description, style settings, and platform IDs. Paste it back into the Anchor field in any future session to pick up exactly where you left off.
Can I skip FrameDNA?
Absolutely. FrameDNA is a starting point accelerator. If you know your visual style well, go straight to CinePrompt and describe your scene. FrameDNA is most useful when you have a reference image and want to extract its cinematography DNA rather than describe it from scratch.
Does Character Sheet Builder need to be part of the workflow?
Not for every project. It should be treated as an optional support tool for character-led work, especially when you need a repeatable turnaround sheet and stronger prompt guidance for missing views. For environment-only, abstract, or one-off shots, you can skip it.