Production-ready animations, transitions, backgrounds, and scenes for Remotion
TypeScript ai-agentsclaude-codedemo-videomcpmcp-servermodel-context-protocolmotion-designproduct-demoreactremotionshadcnvideo
feat: added some practices
kapishdima242ddacec8f7
diff --git a/content/docs/guides/directing-your-agent.mdx b/content/docs/guides/directing-your-agent.mdxnew file mode 100644index 00000000..d4ae453a--- /dev/null+++ b/content/docs/guides/directing-your-agent.mdx@@ -0,0 +1,49 @@+---+title: Directing your agent+description: The first cut is a draft — how to get from there to the video you meant+---++Your agent's first cut will be roughly right and specifically wrong. That's not failure — that's where directing starts. You watch, you say what's off in plain sentences, you watch again. Two or three rounds is normal.++## The loop++1. Watch the whole video once, start to finish, without commenting.+2. Go beat by beat and say what's wrong, referring to beats by number.+3. Put several notes in one message — one sentence per note.++```text+In beat 1, hold each line longer — I can't finish reading.+In beat 3, the background is too loud, calm it down.+Cut beat 5 entirely.+```++## Pacing words++- **"Hold it longer"** / "it goes by too fast"+- **"Tighter"** — cut the dead air between beats+- **"Let it breathe"** — add a pause after a big moment+- **"Make the whole thing two seconds shorter"**++## Motion words++- **"Snappier"** — faster, more decisive movement+- **"Softer"** / "calmer" — less travel, less drama+- **"Come in from the left"** (or right, or below)+- **"Less bouncy"** — when things wobble too much+- **"The background is too loud"** — dim it or slow it down++## Asking for options++When you can't name what's wrong, don't try — ask for variants instead: *"Show me two different openings for beat 1."* Watch both, pick one, move on.++## Redirect or restart++The one judgment call that saves the most time:++- **The details are wrong** — pacing, a color, one beat's motion → direct, with the words above.+- **The structure is wrong** — wrong story, wrong order, wrong number of beats → don't patch it. Rewrite your beat list and prompt again from scratch. Rebuilding structure through comments is always slower than restating it.++## Finishing++- **"Render the video."** — you get an `.mp4` in the project folder.+- Need another shape? Ask: *"Render a vertical version too."*diff --git a/content/docs/guides/how-a-video-is-built.mdx b/content/docs/guides/how-a-video-is-built.mdxnew file mode 100644index 00000000..2e674c0a--- /dev/null+++ b/content/docs/guides/how-a-video-is-built.mdx@@ -0,0 +1,58 @@+---+title: How a video is built+description: Think in beats — the one mental model behind every video you'll make+---++Every video in these guides — and every video you'll invent yourself — is built the same way: as a list of beats.++## Beats++A beat is one idea on screen. A line of text landing. A feature name over a background. A logo drawing itself on. When the idea changes, the beat changes.++Three rules cover most of it:++- **One idea per beat.** If describing a beat needs the word "and", it's two beats.+- **A text beat lives about two seconds** — long enough to read once, not twice.+- **A video is five to ten beats.** The [launch video](/docs/guides/launch-video) is eight.++## The skeleton++Every video that works has the same three acts:++1. **Hook** — why anyone should care: a pain, a bold claim, a question.+2. **Body** — what it is: features, value, proof.+3. **Close** — what to do next: a command, a URL, a date.++Not sure what beats to write? One or two hook beats, three to five body beats, one close beat. That's a video.++## The vocabulary++When you describe a beat to your agent, plain words work — and some plain words map especially well to what remocn can build:++- **"an animated headline"** — a line of text that enters with motion+- **"lines that stack up"** — claims appearing one after another+- **"a living background"** — slow, animated color behind everything+- **"a hard cut" / "a scene change"** — how one beat hands over to the next+- **"a terminal that types"** — a command line typing itself out+- **"a fake app screen"** — an interface with buttons, menus, and dialogs that act+- **"a logo that draws itself on"**+- **"a counter"** — a number counting up to a milestone++You never need to know what any of these are called internally. Your agent does.++## From beats to prompt++Write your video as a numbered list of beats — one line each, your copy in quotes. That list is 80% of a prompt; add a format line and a style line and it's done:++```text+Build a ~15-second, 1920×1080, 30fps video in this Remotion project,+using remocn components:++1. Hook — an animated headline: "<YOUR LINE>".+2. Body — three lines that stack up: <YOUR CLAIMS>.+3. Close — a terminal that types: `<YOUR CTA>`.++Style: dark background, one accent color <HEX>, calm pacing.+```++When the first cut plays, switch hats: you're the director now — see [Directing your agent](/docs/guides/directing-your-agent).diff --git a/content/docs/guides/index.mdx b/content/docs/guides/index.mdxindex be8e72bc..338cb240 100644--- a/content/docs/guides/index.mdx+++ b/content/docs/guides/index.mdx@@ -7,6 +7,15 @@ Each guide starts from a finished video and ends with your version of it. You doFirst time here? Do the one-time [Setup](/docs/guides/setup) — about ten minutes, all copy-paste.-## The guides+## The videos- [Launch video](/docs/guides/launch-video) — the ~35-second video we launched remocn with, rebuilt around your product.++## The practices++Recipes tell you what to make. Practices make you better at every one of them:++- [How a video is built](/docs/guides/how-a-video-is-built) — think in beats, and write your own videos beyond the recipes+- [Directing your agent](/docs/guides/directing-your-agent) — from the first cut to the video you meant+- [Words on screen](/docs/guides/words-on-screen) — lines people can read in two seconds+- [Your brand](/docs/guides/your-brand) — hand your brand over once, stay on-brand foreverdiff --git a/content/docs/guides/launch-video.mdx b/content/docs/guides/launch-video.mdxindex 6ab73922..02d37aa5 100644--- a/content/docs/guides/launch-video.mdx+++ b/content/docs/guides/launch-video.mdx@@ -37,6 +37,8 @@ This is the whole creative work — nine blanks:Have a logo? Drop the SVG into the project folder and mention the file name in the prompt. No logo — your agent will use the product name as a wordmark.+Struggling with the lines? [Words on screen](/docs/guides/words-on-screen) is the cheat sheet.+## The prompt```text@@ -79,6 +81,8 @@ The first cut won't be the final one — that's normal. Direct with plain senten- "The tagline should come in from the left."- "Make the outro two seconds shorter."+More directing vocabulary: [Directing your agent](/docs/guides/directing-your-agent).+## Get the fileAsk your agent: **"Render the video."** You'll get an `.mp4` in the project folder, ready to post.diff --git a/content/docs/guides/meta.json b/content/docs/guides/meta.jsonindex 11f5a2e1..107599a6 100644--- a/content/docs/guides/meta.json+++ b/content/docs/guides/meta.json@@ -1,5 +1,15 @@{"title": "Guides","collapsible": false,- "pages": ["index", "setup", "launch-video"]+ "pages": [+ "index",+ "setup",+ "---Videos---",+ "launch-video",+ "---Practices---",+ "how-a-video-is-built",+ "directing-your-agent",+ "words-on-screen",+ "your-brand"+ ]}diff --git a/content/docs/guides/words-on-screen.mdx b/content/docs/guides/words-on-screen.mdxnew file mode 100644index 00000000..1a8d4bd2--- /dev/null+++ b/content/docs/guides/words-on-screen.mdx@@ -0,0 +1,39 @@+---+title: Words on screen+description: Video copy is not website copy — how to write lines people can read in two seconds+---++On a landing page the reader controls the clock — they can reread. In a video the line is gone in two seconds. Writing for the screen is its own small craft, and this page is all of it.++## The rules++- **Six words or fewer.** If a line doesn't fit, it's two beats — or it's too clever.+- **One idea per line.** Split sentences; don't compress them.+- **Verbs over adjectives.** "Ships in one command" beats "incredibly simple".+- **Concrete over grand.** Numbers, commands, names: "110+ components", not "a huge library".+- **No adjectives you can't prove.**+- **Read it aloud once.** If you stumble, the viewer will too.++## Formulas for common beats++**Pain lines** — name the problem in the viewer's words, not yours; the second line twists or promises a way out:++> "Every launch needs a video" / "Yours shouldn't take a week"++**Taglines** — what it is plus who it's for, zero filler:++> "Cinematic video components for React"++**Positioning** — borrow a shape people already know; nothing transfers a mental model faster:++> "Like shadcn/ui, for video"++**Value claims** — three, each concrete, each provable:++> "110+ components" / "One command to install" / "The code is yours"++**The close** — the single shortest next action. A command *or* a URL — one, not both.++## The two-second test++Whatever you're filling in — a worksheet, a prompt, a rewrite — say each line out loud at speaking pace. Longer than two seconds to say? Tighten it.diff --git a/content/docs/guides/your-brand.mdx b/content/docs/guides/your-brand.mdxnew file mode 100644index 00000000..71e97dab--- /dev/null+++ b/content/docs/guides/your-brand.mdx@@ -0,0 +1,40 @@+---+title: Your brand+description: Hand your brand to the agent once — every video after that comes out looking like yours+---++The recipes default to remocn's look — a warm dark background and one lime accent. Your videos should look like your product instead. Do it once: write a brand brief, have your agent save it in the project, and reference it forever.++## The brand brief++Fill this in and paste it to your agent:++```text+Save this as BRAND.md in the project and use it for every video we make here:++# Brand brief++- Product: <NAME> — <one line on what it does>+- Background: <HEX> (dark or light)+- Text color: <HEX>+- Accent color: <HEX> — use sparingly, one accented element per beat at most+- Font mood: <e.g. clean and geometric / warm and rounded / mono and technical>+- Logo: <FILE NAME in this folder, or — use the wordmark "NAME">+- Copy tone: <e.g. plain and confident, no exclamation marks>+```++From then on, start every new video prompt with one line: **"Use the brand brief."**++## Picking the values++- **Background** — your app's or landing page's background is usually right. Dark backgrounds forgive more.+- **One accent, used sparingly.** If everything is accented, nothing is.+- **Text color** — off-white on dark, near-black on light. Pure white on pure black reads harsh on video.+- **Font mood** — you don't have to name a font; describe the mood and your agent picks one. If you know your font's name, name it.+- **Logo** — an SVG beats a PNG: it scales cleanly and can be drawn on.++## Staying on brand++- Open every new video prompt with "Use the brand brief."+- Rebranded? Ask your agent to update `BRAND.md` — every video after that follows.+- Consistency compounds: three videos with one look read as a channel; three looks read as three experiments.