Skip to main content

Prompt Guides -> what they are and how to set them up

Updated today

Prompt Guides are instructions that tell Agent One exactly how to behave when working with a specific model. Instead of describing your preferences every single time you generate something, you set them once and Agent One follows them automatically.

Think of them as standing orders for each model, your rules, your style, your non-negotiables, baked in from the start.

How to find Prompt Guides

Inside your project, click the Context tab β†’ click [ edit ] β†’ in the pop-up window, select Prompt Guides.

You'll see a set of default guides already in place, one for each major model invideo uses, including Nano Banana, Veo, Sora, Kling, and ElevenLabs Voice Design. These are worth reading through before you start, they give you a clear picture of how each model thinks and what it responds well to.

Default Prompt Guides

Invideo ships with ready-made guides for the following models:

  • Nano Banana - for image generations

  • Veo - for video generations

  • Sora - for video generations

  • Kling - for video generations

  • ElevenLabs Voice Design - for voice generation

These are active by default and have been written to get the best out of each model out of the box. You can read through them, edit them, or leave them as they are.

Creating your own Prompt Guide

Have a specific way you want a model to behave? Click + New prompt guide at the bottom of the Prompt Guides section to create your own.

You might use this to:

  • Always generate images in a specific visual style

  • Ensure a consistent camera angle or lighting across all video generations

  • Set a default voice tone or pacing for all audio output

  • Define rules for a specific character or brand asset

The more specific your guide, the more consistently Agent One delivers exactly what you're after, without you having to repeat it every time.

A few things worth knowing

  • Prompt Guides apply automatically to every generation using that model within your project

  • You can have multiple guides and they stack alongside your Context

  • Editing a guide updates it immediately for all future generations in that project

  • Guides are per project, they don't carry over to other projects automatically

Did this answer your question?