Skip to content
motion lab

09 Prompt lab

Put it together: a structured brief an agent can execute frame by frame.

Floor
09 of 09
Demos
Brief builder, Prompt check

Put it together

“Make a cool launch video” gives an agent nothing to work with, so it falls back on the average of everything it has seen: fades, bounces, gradients. Every floor so far adds one thing a good brief needs: timing and easing (01), a reveal order (02), interface rules (03), physics (04), frames (05), beats and ratios (06), tempo (07) and export settings (08).

The most useful habit is frame-numbered thinking. When the plan says “hook runs f0 to f107, title settled by f18”, the agent can build exactly that, check it, and you can review it with the same numbers.

Brief builder

Fill in what you know. The brief turns it into frame ranges, keyframes, motion rules and a checklist an agent can work through frame by frame.

Film
30 s · 900 frames
Frame rate
Aspect
Tone
#0f1216
#ed4423
Engine
120 BPM

fieldnote-brief.md

# Motion brief: Fieldnote · Launch film

You are directing a 30-second launch film in Remotion. Think in frames: plan every beat as a frame range at 30 fps, and name keyframes by frame number (f0, f18, …) in your plan and in your self-review.

## Goal
- Message: “Meeting notes that write themselves.”
- Audience: product teams at growing startups
- Call to action: “Start free at fieldnote.app”

## Format
- 30 s at 30 fps = 900 frames (f0–f899)
- 16:9, 1920×1080. Keep text inside a 54px title-safe margin.
- One <Composition id="FieldnoteFilm" width={1920} height={1080} fps={30} durationInFrames={900} />, one <Sequence> per beat.

## Brand (locked)
- Colors: #0f1216 and #ed4423, plus white and neutral grays. No other hues.
- Type: Host Grotesk. Two sizes per scene at most.
- Avoid: stock footage, lens flares, bounce easing, gradients.

## Motion language
- Entrances: cubic-bezier(0.16, 1, 0.3, 1) over 18 frames (0.6 s).
- Exits: ease-in cubic-bezier(0.55, 0, 1, 0.45) over 12 frames.
- Crossfades and slow 2% pushes. Holds of at least 1.5 s. No overshoot anywhere.

## Beat plan
### 1. Hook · f0–f104 (0.0–3.5 s)
- Fieldnote in motion within the first second. No logo intro.
- f0: first frame is already worth stopping on (it is the thumbnail)
- f0–f18: main element enters and settles
- f93–f104: exit, or hard cut on f105
### 2. Problem · f105–f269 (3.5–9.0 s)
- One concrete shot of the pain product teams at growing startups feel today.
- f105: cut lands on the beat
- f105–f123: main element enters and settles
- f258–f269: exit, or hard cut on f270
### 3. Reveal · f270–f539 (9.0–18.0 s)
- Fieldnote arrives and the message lands: “Meeting notes that write themselves.”.
- f270: cut lands on the beat
- f270–f288: main element enters and settles
- f528–f539: exit, or hard cut on f540
### 4. Proof · f540–f764 (18.0–25.5 s)
- The feature working on real interface, or one number that matters.
- f540: cut lands on the beat
- f540–f558: main element enters and settles
- f753–f764: exit, or hard cut on f765
### 5. Call to action · f765–f899 (25.5–30.0 s)
- End card: “Start free at fieldnote.app”. Hold it still and readable.
- f765: cut lands on the beat
- f765–f783: main element enters and settles
- f783–f899: hold the end card completely still

## Sound
- Music at 120 BPM: one beat every 15.00 frames, a bar every 60.0.
- Beat boundaries above are snapped to the beat grid: f0, f105, f270, f540, f765.
- Every on-screen impact gets a sound; never let a picture hit land after its sound.

## Before rendering, check these frames
- f0: is the first frame worth stopping on?
- f104: has the viewer seen Fieldnote yet?
- f288: is the main element settled, readable and inside the safe margin?
- f765–f899: is the call to action readable for at least 60 frames (2 s)?
- Every entrance: settled within 18 frames, no bounce.
- Only #0f1216, #ed4423 and neutrals anywhere in the frame.
- Render f0, f104, f288 and f899 as stills and review them before the full render.

## Deliverables
- 1920×1080 H.264 MP4 at 30 fps with AAC audio, plus the editable project source.

Check before you send

A brief is only as good as its missing pieces. Before you hand a prompt to an agent, check it for the details that decide the result: length, frame rate, format, audience, brand, structure, motion language and a review step. The check below runs entirely in your browser.

Prompt check

Paste any motion prompt. The check looks for the details an agent needs to get it right the first time.

0 / 13

  • Length: missing

    Say how long: “30 seconds”.

  • Frame rate: missing

    Pick a frame rate: “30 fps”.

  • Format: missing

    Name the ratio: 16:9, 9:16, 1:1 or 4:5.

  • Audience: missing

    Who is it for? “For product teams at startups”.

  • Message: missing

    Quote the one line it must say.

  • Brand colors: missing

    Give exact colors: “#0f1216 and #ed4423 only”.

  • Typeface: missing

    Name the typeface.

  • Structure: missing

    List the beats: hook, problem, reveal, proof, CTA.

  • Frame numbers: missing

    Give key moments as frames: “title settled by f18”.

  • Motion language: missing

    Describe the motion: easing, speed, overshoot or not.

  • Call to action: missing

    End on an action: what should the viewer do?

  • Engine: missing

    Name the engine: Remotion or HyperFrames.

  • Review: missing

    Ask for a self-review of specific frames before rendering.

Rules of thumb

  • Lock the brand in the brief, not in feedback. Colors, type and motion rules up front.
  • Give ranges in frames and the frame rate once. Seconds are for humans; frames are for the renderer.
  • Ask for stills of key frames before the full render. They are cheap and catch most problems.
  • Load the skills the job needs: Remotion or HyperFrames for the engine, impeccable for design checks, video-shotcraft or lemo-opuscar for shot and style vocabularies.
  • Keep the brief. The next video starts from it, and only the message changes.