Prompting Guide

fluos responds to creative direction, not to keywords. The best mental model is briefing a motion designer who is fast, literal, and has never seen your brand before.

The four things that matter most

Every strong brief answers these. If you leave one out, fluos will pick a default or ask.

A 20-second 16:9 product teaser for a cold brew brand.
Editorial look: big serif type on warm off-white, one burnt-orange accent.
Fast cuts on the beat, no narration.
End on the logo with the tagline underneath.

Describe motion, not just layout

The difference between a passable video and a good one is almost always pacing. fluos understands motion language directly:

• Energy — "fast cuts", "slow and confident", "punchy", "let it breathe"
• Timing — "the headline should settle by 1.5s and hold"
• Choreography — "stagger the bullet points", "the logo draws itself in"
• Transitions — "wipe between scenes", "cross-dissolve", "hard cuts"

If a scene feels wrong, name the feeling: "scene 2 drags", "the open has no hook", "the end card appears too abruptly."

Reference versus embed

This trips people up more than anything else. When you attach an image, fluos treats it as a reference by default — it studies the look and recreates it, rather than dropping your file on screen.

If you want the actual file visible, say so explicitly:

Show this product photo full-bleed in scene 2, don't recreate it.

Logos are the exception — an attached SVG logo is always meant to appear, and fluos animates the real paths.

Iterate narrowly

One change per message. It sounds slow; it is much faster in practice, because a narrow request cannot accidentally rewrite the parts you liked.

Prompts worth stealing

Launch teaser

A 15-second 9:16 launch teaser for our new running shoe.
Hook in the first second, fast cuts, a bold price tag reveal, high-energy motion.
End on the logo and "Available now".

Logo sting and lower-third

Animate our logo and brand colors into a reusable 4-second intro sting,
plus a matching lower-third for name and title. Same motion language for both.

Narrated explainer

A 45-second 16:9 explainer of how our billing works.
Calm narration, one idea per scene, headlines under six words.
Show the interface doing the thing — no slideshows of static screenshots.

Data story

Use the attached CSV. Build a 20-second animated bar chart race of monthly revenue,
with the year counting up in the corner. Dark background, single accent color.

Recompose an existing build

Recompose this for 9:16 Reels. Keep the same story beats, logo, and palette.
Rework layout and type for vertical safe areas — don't rebuild from scratch.

What fluos does by default

Knowing the defaults tells you what you do not need to specify — and what to override when you disagree:

• Readable copy stays inside safe margins, well clear of the frame edges.
• Entrances resolve early in a scene and then hold, so nothing is still moving when you are trying to read it.
• Nothing freezes: every scene keeps some ambient motion, and static end cards are avoided.
• Narrated videos treat the voiceover as the master clock — visuals are cut to the narration, not the other way round.
• Social cuts get a hook in the first second and oversized type.
• fluos avoids generic default typefaces in favor of something with a point of view.

Reuse a brief

If you keep typing the same brand rules, save them once as a snippet and insert them with one click. See Custom Prompts and Snippets. For deeper, reusable playbooks, use Skills.

Related