> ## Documentation Index
> Fetch the complete documentation index at: https://docs.videngineer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scene prompts

> How to use scene prompts, Cut Blueprints, and tool-specific handoffs without losing the original mechanism.

Scene prompts answer: **where do I paste the production directions from a teardown?**

Every completed teardown includes tool-ready scene prompts. They bridge the gap between understanding a reference and planning your own video. This page is the usage guide; the [Recipe & Cut Blueprint](/layers/recreation) page documents the fields.

## Cut Blueprints - the deep dive on one cut

Scene prompts cover the whole video. When one specific cut is the thing you need to understand - the slow-burn reaction shot, kinetic text montage, product reveal, or hard transition - open that cut in **The Cuts** and generate a **Cut Blueprint**.

A Cut Blueprint costs **2 credits**, with the first one free as a taste. It saves onto the teardown permanently: reopening it later is free, and you are only charged after the blueprint is stored. It contains:

* **Shot table** - frame-by-frame direction with source timestamps, frame prompts, camera position/move, and transition into the next frame
* **The mechanism** - how the cut was made: camera setup, lighting plan, lens/depth-of-field, motion rig, grade, or animation approach
* **Your-subject recipe** - build steps with `[YOUR SUBJECT]` swap slots
* **Swap note** - which elements to replace with your own and which mechanics should stay consistent
* **Build handoff** - a numbered sequence for your editor, designer, or production workflow

Every blueprint carries the same principle: it is a study of mechanism. Bring your own subject, footage, and brand.

API: `POST /api/v1/project/{job_id}/cut-brief` with `{"technique_id": "cut-001"}`. The call is idempotent: it returns `202 running` while generating and the stored blueprint once ready. A wrong `technique_id` returns the valid set. The same blueprint is available as `get_cut_brief(job_id, cut)` through [the connector](/agents/mcp-connector), which reports the credit result in the response.

## What each scene entry contains

```json theme={null}
{
  "scene_number": 3,
  "timestamp": "0:12-0:17",
  "duration_seconds": 5,
  "subject": "Hands on a laptop keyboard, papers scattered around",
  "image_prompt": "Close-up of hands on a laptop keyboard, papers scattered around, shallow depth of field, muted warm office lighting, slight motion blur. Shot: static with slow push-in. Style: candid, UGC-adjacent realism.",
  "video_prompt": "Camera: static with subtle push-in. Motion: ambient - fingers shift slightly, paper edge flutters. Duration: 5s. Style: naturalistic, no dramatic movement.",
  "camera_movement": "static with slow push-in",
  "style_notes": "UGC-realist, warm desaturated, tight-frame intimacy"
}
```

**`image_prompt`** describes the still frame: composition, lighting, subject framing, and visual style.

**`video_prompt`** extends the frame prompt with camera direction and motion for a short clip.

**`camera_movement`** is the motion direction on its own for tools that take movement separately.

**`style_notes`** is the visual fingerprint. Keep this consistent across scenes to maintain cohesion.

## Where to use them

| Tool                      | What to paste                     | Notes                                                                              |
| ------------------------- | --------------------------------- | ---------------------------------------------------------------------------------- |
| **Midjourney**            | `image_prompt`                    | Add `--ar 16:9 --style raw` for video-oriented output                              |
| **DALL-E / ChatGPT**      | `image_prompt`                    | Works well for realistic styles                                                    |
| **Adobe Firefly**         | `image_prompt`                    | Good for brand-safe stock-style outputs                                            |
| **Kling I2V**             | Image from above + `video_prompt` | 5-10s clips; use V3 for realistic, Omni for stylized                               |
| **SeedAnce**              | Image from above + `video_prompt` | Better for longer motion arcs                                                      |
| **A production workflow** | The full recipe                   | Use the complete set when you want image, animation, and assembly handled together |

## Production workflow

<Tabs>
  <Tab title="Manual">
    <Steps>
      <Step title="Pick the key scenes">
        Start with the hook, proof moment, strongest transition, and close. You rarely need every scene.
      </Step>

      <Step title="Generate keyframes">
        Use the `image_prompt` and keep `style_notes` consistent.
      </Step>

      <Step title="Animate or shoot">
        Use `video_prompt` and `camera_movement` as direction, then adapt it to your own subject and footage.
      </Step>

      <Step title="Assemble">
        Cut to the reference timing, then add your own voice, music, SFX, and CTA.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Handoff">
    Export the recipe and send it to your editor, designer, or connected production workflow. The useful handoff includes the beat sheet, The Cuts, scene prompts, Sound layer, and any Cut Blueprints you generated.
  </Tab>
</Tabs>

## Tips

* **You do not need all the scenes.** Five to eight strong scenes can carry a 30-60 second video.
* **Keep the style notes consistent.** Visual style drift across cuts reads as weak production.
* **Adapt the shot type.** "Close-up of hands on a keyboard" is a shot type; replace the subject with yours.
* **For B2B ads, watch for workhorse patterns.** Tight talking-head plus product-screen proof is common because it is efficient and clear.
* **Go deeper per cut.** Use Cut Blueprint only for shots where the mechanism matters.