---
name: video
description: "House rules for any video Loki makes: product promo, demo, explainer, PSA or screen recording, with any tool (Remotion, screen capture, Veo or Flow). Covers the story order, scope, pacing, motion, voice-over checks and the review loop before delivery. Use when planning a script or storyboard, building or rendering a video, or reviewing a cut. Triggers on '做影片', '宣傳片', '宣導片', 'demo 影片', '介紹影片', '腳本', '分鏡', '配音', 'Remotion', 'promo video', 'explainer video', 'storyboard', 'voice-over'. NOT how a generated shot looks; that's photo-realism."
---

# video

Rules for every video, whatever the tool. Each rule comes from a correction
Loki made more than once. Story rules are settled before any animation is
built. Production rules are checked before every delivery.

## Story

Settle these in the script, before building a frame.

1. **Follow the order a viewer understands.** The pain or need comes first.
   Then what the thing is. Then how it does it. The tagline comes last. A
   tagline only lands after the viewer has seen the thing work.
2. **Keep the case consistent.** The problem in the opening, the action and
   the result are one and the same thing. The case must also make sense in
   real life.
   - Bad: an automatic task that still asks a person to approve it every day.
   - Good: the person asks the agent to drop the approval step, and the agent does it.
3. **One video, one main line.** Cut every scene that does not move the main
   line forward, even a working feature. One tool or framing does not have to
   open every video in a series.
4. **Spend time on the point.** Speed up typing, waiting and loading. A slow
   step that is not the message makes the viewer wait.
5. **Agree on scope first.** List the features or points the video will
   cover. Loki ticks the list before the script is written. A video that
   covers too little gets rebuilt.

## Production

1. **Make 1 test clip first.** Build 1 short section in full style. Loki
   approves the style, then the rest follows that pattern.
2. **Offer looks side by side.** For a visual choice (look, color, layout),
   render 2 to 3 options as stills next to each other. Loki picks. Keep the
   others in the code as options.
3. **Keep motion continuous.**
   - Every element that enters also exits. Nothing pops in or vanishes.
   - Content that a product generates appears the way the product makes it:
     text streams, forms stream, nodes grow.
   - Camera moves ease in and out.
4. **Check every voice-over line.**
   - Keep a pronunciation file for the project: polyphonic characters,
     product names and English words, each with its intended reading.
   - After synthesis, run speech-to-text on each line and compare it with
     the script. Fix and regenerate any line that differs.
   - Use real voices and real data when they exist, instead of a stand-in.
5. **Inspect frames before delivery.** Grab a still at each key moment
   (scene change, click, element entering or leaving). Put them in a grid
   and look at them. Fix what is wrong, then deliver.

## Screens and end cards

- Draw product screens from the product's own code or design system when
  the repo is available. A screenshot is a fallback.
- The end card names the product. It does not show a URL.
- Copy on screen and in subtitles follows Loki's text rules: no dashes and
  no middle dot.

## Before delivery

1. Story rules 1 to 5 hold for the final cut.
2. Every voice-over line passed the speech-to-text check.
3. The frame grid shows no element that pops in, vanishes or overlaps.
4. The file opens and plays from start to end.