Feature announcement

This is the video we announced remocn/ui with. A launch video sells the whole product; a feature announcement sells one release — and it earns its runtime by showing the feature work, not by talking about it. Eight beats, about forty seconds, and the demo beat gets the most screen time.

The storyboard8

1. 1
   The momentsThree quick situations your users know, swapping in one spot, then the problem lands in one line.
2. 2
   The reveal"Meet <Feature>", with your one-line promise.
3. 3
   The mechanismThe single idea behind the feature, one calm beat.
4. 4
   The demoThe feature acting on camera: a fake app screen doing the real thing. The longest part of the video.
5. 5
   The breadthA fast montage of what else ships in this release.
6. 6
   The valueThree claims stack up.
7. 7
   The installA terminal types your command or call to action.
8. 8
   The outroYour logo, one quiet closing line.

Your words10

Ten blanks:

Feature name

• <FEATURE NAME>

Three momentsSituations where users need it, two to four words each

• <MOMENT 1>
• <MOMENT 2>
• <MOMENT 3>

Problem lineThe claim that lands after the moments

• <PROBLEM LINE>

Promise lineWhat changes now, one sentence

• <PROMISE LINE>

Mechanism lineHow it works, one plain sentence

• <MECHANISM LINE>

Demo actionsTwo or three things we should watch happen ("a dialog opens, a menu filters, a form fills itself")

• <DEMO ACTIONS>

What else shipsThree to six short names; skip this beat if the release is one thing

• <OTHER ITEMS>

Three value claims

• <THREE CLAIMS>

Install command or CTA

• <COMMAND OR CTA>

Closing line

• <CLOSING LINE>

The prompt

Paste it into your agent with your words in place of the highlighted blanks.

I'm making a feature announcement video with remocn (remocn.dev).

Build a ~40-second, 1920×1080, 30fps release video for <FEATURE NAME> in this
Remotion project, using remocn components — install anything you need with
`npx shadcn add @remocn/<name>`:

1. Hook — three quick moments swapping in one center slot: "<MOMENT 1>",
   "<MOMENT 2>", "<MOMENT 3>" — then the problem lands beneath them:
   "<PROBLEM LINE>".
2. Reveal — "Meet <FEATURE NAME>", then the promise: "<PROMISE LINE>".
3. Mechanism — one calm beat naming the idea: "<MECHANISM LINE>".
4. Demo — the feature acting on camera: a fake app screen where
   <DEMO ACTIONS>. Give this the most screen time — it is the proof.
5. Breadth — a fast montage of what else ships: <OTHER ITEMS>.
6. Value — three claims stacking line by line (line-by-line-slide):
   <THREE CLAIMS>.
7. Install — a terminal line that types itself: `<COMMAND OR CTA>`.
8. Outro — my logo (<LOGO FILE, or: use the product name as a wordmark>)
   with a quiet closing line: "<CLOSING LINE>".

Style: warm dark background (#141318), off-white text, one accent color
<ACCENT COLOR>, Manrope. One quiet shader-simplex-noise field runs behind the
entire video with a radial scrim. Keep transitions restrained — crossfades,
plus one signature transition at the reveal. Use my copy exactly as written.

Directing the result

• The demo is too fast — I can't follow what the screen does.
• Give the reveal more room to breathe.
• Cut the breadth montage — this release is one thing.
• The hook moments should swap faster.

Get the file