Custom Prompts and Snippets

Snippets are saved blocks of prompt text — brand rules, tone, motion constraints, anything you would otherwise paste into every brief.

Find them in Library → Snippets.

Two ways they get used

This is the important part, and it is easy to miss:

1. Automatically. Your saved snippets are given to the agent as standing guidance on every message in that workspace, and it follows them when they are relevant. You do not have to insert anything.
2. Manually. In the composer, Add content → Text snippets drops the snippet's text straight into your draft so you can edit it for this specific brief.

Because of the first behavior, keep snippets to durable rules. Anything one-off belongs in the message itself.

Managing snippets

In the Snippets tab you can create (New snippet), edit, and delete. Each one has a name and a body.

What makes a good snippet

Good snippets are short, specific, and about constraints rather than content.

Brand lock

Always use the attached brand SVG inline — never redraw or replace the mark.
Palette: #0A0A0A / #F06E2C / #FAFAF9. No other accent colors.
Type stays large and high-contrast.

Motion house style

Sharp ease-outs, no bounce, no elastic easing.
No cut shorter than 8 frames.
Every scene keeps some ambient motion — nothing freezes.

Tone

Premium but approachable. Never use exclamation marks.
Headlines under six words. Always end on a clear call to action.

What not to put in a snippet

Make exactly the same video as project X with all previous context and random changes.

This fails for three reasons: it is ambiguous, it is not reusable, and because snippets apply to every message, a vague one quietly fights with your live instructions on unrelated projects.

Also avoid:

• Full scripts or one-off copy — those belong in the brief
• Aspect ratio and duration, unless every single video you make uses the same ones
• Anything that contradicts another snippet

Related