Spec a product video in Kiro and build it with Remotion
Kiro builds from specs: requirements, a design and a list of tasks. A video is a natural spec. The reference supplies the design (every shot, its frames and motion) and each shot becomes a task.
This guide connects a library of real launch videos so Kiro can write that spec from a measured reference.
Want only the install and a few prompts? The Kiro launch video page has them on one screen.
Why Kiro suits video work
- Specs turn the shot plan into reviewable requirements, design and tasks.
- One task per shot makes progress easy to follow and to redo.
- Steering files keep brand rules in every session.
- Servers are three lines in mcp.json, per user or per workspace.
Start a Remotion project
Remotion turns React components into video: every frame is a render of your component at that frame number, so Kiro edits a video the way it edits any other code. You need Node.js. Ask Kiro to scaffold the project, or run it yourself:
npx create-video@latestGive Kiro a reference to work from
A blank prompt gets a generic video. A real launch video measured frame by frame gets one with a rhythm: when each shot starts, how it enters and how much moves. The library at https://kuchi.kalarislabs.com/mcp is a free MCP server with no sign-in and no API key. Add it to Kiro:
1. Add this to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json for one workspace). No sign-in is needed.
{
"mcpServers": {
"kuchi": {
"url": "https://kuchi.kalarislabs.com/mcp"
}
}
}2. Kiro picks up the change; check Kuchi in the MCP servers view.
3. Paste the setup prompt from this page into a new session.
Then paste the setup prompt, so the agent knows how to use the library:
Connect the Kuchi MCP server at https://kuchi.kalarislabs.com/mcp (Streamable HTTP, no sign-in) and confirm it works by listing its tools.
Kuchi is a library of real product-launch videos to use as inspiration templates. When I want a launch video, read kuchi_get_workflow and follow it: get a short list with kuchi_suggest_templates and show me each one's poster and link so I can choose, in chat or by picking a video on kuchi.kalarislabs.com and pasting its link. Once I pick one, study it with kuchi_get_breakdown, look at its storyboard and note what each shot shows, then call kuchi_plan_remake with my product details and your shot analysis, and ask me for my logo, screenshots and anything else it lists as missing. Build to the blueprint's frames. Before you deliver, run kuchi_check_remake and compare your frames with the reference. Copy only the reference's motion and taste; everything on screen comes from my product.The prompts, in order
- Suggest launch video templates for a cloud dashboard and show me the posters.
- Study my pick and write a spec: requirements from my product, design from the reference shots, one task per shot.
- Run the tasks: scaffold Remotion and build each shot on its planned frames.
- Add a final task to check the remake against the reference and render.
- Fix the tasks the check flags.
Writing one shot in Remotion
A Remotion video is a React component rendered once per frame. Inside a shot, useCurrentFrame() returns the frame number counted from the start of that shot's <Sequence>, and useVideoConfig() gives the fps and size. Everything that moves is a function of that number, which is why Kiro can match a reference to the frame: an entrance that takes 12 frames in the reference takes exactly 12 frames in yours.
The blueprint says how each shot enters. Each entrance has a direct translation:
| Blueprint `enters` | In Remotion |
|---|---|
cut | No entrance animation: the shot is fully on screen at its first frame. |
transition | Animate over the first frames: interpolate(frame, [0, 12], [0, 1], { extrapolateRight: 'clamp' }) for opacity, or a spring() for scale or position. |
hold | Same scene as the shot before: keep the layout and resume the motion where it stopped. |
blank_black, blank_white | Put a frame or two of solid black or white between the shots, as the reference does. |
Here is a product-screen shot that enters with a short transition, written the way Kiro should write every shot: assets from public/ through staticFile(), timing from the frame number, nothing random.
import { AbsoluteFill, Img, interpolate, spring, staticFile, useCurrentFrame, useVideoConfig } from 'remotion';
// Blueprint shot 3: kind ui_screen, enters "transition", motion "medium".
export const Shot3 = () => {
const frame = useCurrentFrame();
const { fps } = useVideoConfig();
const opacity = interpolate(frame, [0, 12], [0, 1], { extrapolateRight: 'clamp' });
const rise = spring({ frame, fps, config: { damping: 200 } });
return (
<AbsoluteFill style={{ background: '#0b0b0f', alignItems: 'center', justifyContent: 'center' }}>
<Img
src={staticFile('screens/dashboard.png')}
style={{ width: '78%', borderRadius: 16, opacity, transform: `translateY(${(1 - rise) * 40}px)` }}
/>
</AbsoluteFill>
);
};For a screen recording use <OffthreadVideo src={staticFile('screens/demo.mp4')} /> instead of <Img>. Never use Math.random() or the clock inside a shot: Remotion renders frames in parallel and out of order, so anything not derived from the frame number flickers. Use Remotion's random(seed) when you need variation.
Preview, check and render
Open the Remotion Studio to scrub through the video while Kiro works, render single frames to compare with the reference at the times the check gives, then render the file. Launch stands for your composition id.
npx remotion studio
npx remotion still Launch out/frame-90.png --frame=90
npx remotion render Launch out/launch.mp4What trips people up in Kiro
- Writing the spec before the shot analysis. Study the reference first.
- Workspace and user mcp.json both defining the server. Keep one.
- Tasks that span several shots. Keep one shot per task so a fix stays small.
Questions
Where is the Kiro MCP config?
In ~/.kiro/settings/mcp.json for every workspace, or .kiro/settings/mcp.json for one.
Can Kiro build a video?
Yes. It writes the Remotion project from its tasks and runs the render.
Why use a spec for a video?
A spec makes the plan reviewable before code, and each shot task can be checked on its own.

