> ## Documentation Index
> Fetch the complete documentation index at: https://hyperframes-codex-docs-human-first-refactor.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Give your agent a useful brief

> Describe the video clearly, review the direction, and ask for changes without writing a technical specification.

You do not need to explain how to build the video. Give the agent enough context to make good creative decisions, then react to what it shows you.

## Start with the outcome

Begin with `/hyperframes`, then describe the result in normal language:

```text theme={null}
/hyperframes Make a 30-second launch video for https://example.com.

Audience: small design teams
Goal: help them understand the collaborative review workflow
Format: 16:9
Style: calm, precise, and product-led
Must show: comments, version history, and the final approval screen
End with: “Review work without another meeting.”
```

The most useful details are:

* **Source** — a URL, document, pull request, media file, or idea.
* **Audience** — who should understand or care.
* **Goal** — what the viewer should know, feel, or do.
* **Length and format** — only when they matter.
* **Tone** — a few specific words or a useful reference.
* **Required material** — exact wording, product screens, media, or claims.
* **Boundaries** — anything the video must avoid.

If you do not know the length, workflow, or visual treatment, leave it open. The agent can propose them.

## Use real material

Grounded input usually produces a stronger result than a long list of adjectives.

Good starting material includes:

* a product or website URL;
* launch notes or a script;
* a pull request;
* a transcript or existing video;
* a music track;
* brand assets and real screenshots;
* a short explanation of the problem and solution.

Link or attach the material and say what role it should play. Do not assume the agent knows which files matter.

## Approve the direction before the build

For a new project, the agent should confirm the important choices before producing the full video.

Check:

1. Is there one clear message?
2. Does the sequence make sense to someone new?
3. Does the visual direction fit the product or subject?
4. Are the required words and screens included?
5. Is the proposed length realistic?

Fixing the brief or storyboard is cheaper than rebuilding several finished scenes.

## Give feedback on what you see

After the first version, describe the visible problem and the desired outcome:

```text theme={null}
The opening repeats the same claim twice.
Reveal the product by three seconds and use the second scene to show the workflow.
Keep the current colors and voiceover.
```

Useful feedback is specific:

* “The title is difficult to read over the footage.”
* “This screen appears before the voiceover explains it.”
* “The middle feels repetitive; combine these two scenes.”
* “Keep the layout, but make the motion calmer.”
* “Replace the final line with ‘Start creating today.’”

Avoid restarting with a completely new prompt for every revision. The existing project, storyboard, and visual direction are useful context.

## Describe feeling, not implementation

Words such as **calm**, **snappy**, **editorial**, **playful**, **cinematic**, or **restrained** help the agent choose motion and design.

References are even better when you explain what you like about them:

```text theme={null}
Use the reference for its spacious typography and slow camera movement.
Do not copy its colors or its dramatic sound design.
```

You normally do not need to name easing functions, animation libraries, tracks, or HTML attributes. Those are implementation choices.

## Know when to use Studio

Use Studio for direct changes you can point at:

* edit wording;
* move or resize something;
* adjust color or type;
* trim or split a clip;
* change a keyframe;
* replace media;
* export a version.

Use the agent when the change affects the story, several scenes, new assets, source structure, or a problem you cannot confidently repair.

<Tip>
  A useful rule: if you can point at the thing, try Studio. If you need to describe a new outcome, ask the agent.
</Tip>

## If the result goes wrong

Do not compensate with a much longer prompt. Identify the first decision that is wrong: message, sequence, content, design, timing, or execution.

Use [Troubleshooting](/guides/troubleshooting) for failures and [Check quality before export](/guides/quality-checklist) for a structured review.