> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/compose/shot-details.md).

# Shot details

Name and description per shot. The metadata that feeds the visualizer's auto-prompt for that specific shot.

Naming a shot and describing what happens in it is how the visualizer learns what the shot is for. It reads both into the prompt at render time. The difference between a vague *"action shot"* and a specific *"low-angle hero, supercar accelerating from a stop, helicopter visible in the background"* is what determines whether the render lands.

## Where to find it

The two fields live in a dialog, not a docked panel. Open the shot's **…** menu, either on its card in the Storyboard or on its row in the [Scene Outliner](/build/scene-outliner.md), and choose **Edit Details**.

![The Edit Details dialog with its name field reading Lambo animated, its description field reading Car moving through an intersection, and Cancel and Confirm beneath them](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-33eda9dacb06e9928f4851e0c3d6fb168f783730%2Fshot-details-panel-01.png?alt=media)

The dialog is headed **Edit Details** and subtitled *Edit the name and description*. It carries the two fields, then **Cancel** and **Confirm**. Confirm commits; Cancel and the close control both discard.

## What it does

The auto-prompt's \[Scene Context] block reads from the scene name and description, the shot name and description, and the camera lens and aspect ratio. Of those, the shot's own metadata is the only piece that varies per shot in the same scene. A scene called "Manhattan street" with three shots called "shot-1", "shot-2", "shot-3" produces three nearly identical prompts; the same scene with shots called "low-angle hero", "wide establishing", "interior dashboard POV" produces three meaningfully different ones.

## The two fields

Edit Details has two writable fields:

### Name

Short label, used for the storyboard thumbnail and for the auto-prompt. Aim for descriptive and short – "low-angle hero" rather than "the shot where the camera goes low to make the car look big".

### Description

A sentence or two on what's happening or what mood the shot has. *"Lamborghini accelerating from a stop"*, *"Helicopter circles overhead, surveying the chase"*. Reads into the auto-prompt verbatim.

## How shot details flow into the render

```mermaid
flowchart LR
    A[Shot name] --> B[Auto-prompt Scene Context]
    C[Shot description] --> B
    E[Lens] --> B
    F[Aspect ratio] --> B
    B --> G[Diffusion model]
    G --> H[Render]
```

Both fields reach the model alongside the lens and aspect ratio. Treat them as production-grade text the model will use.

## When to fill it in

The honest answer: the moment you create the shot. Fill the name first, the description second. The friction of doing it later is higher than doing it now, and unnamed shots multiply faster than you'd think.

## Common mistakes

* **Generic names.** "Shot 1", "Shot 2", "Wide". Reads identically to the model. Always describe what makes this shot different.
* **Description is the whole brief.** Keep it tight. The model honors short, specific descriptions better than rambling ones; the truncation rule from [Object details](/build/object-details.md) applies here too.

## Related

* [Shots](/compose/shots.md)
* [Lenses](/compose/lenses.md)
* [Aspect ratios and film gates](/compose/aspect-ratios-and-film-gates.md)
* [Auto-prompt](/visualize/auto-prompt.md)
* [How the visualizer thinks](/overview/concepts/how-the-visualizer-thinks.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/compose/shot-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.