Skip to content

hubeiqiao/how-i-make-videos-with-ai / skills/make-a-video

make-a-video

Verified

Make a finished video from someone's own photos, clips, screen recordings or voice, by writing it as code with Remotion and rendering drafts they react to. It follows the five steps of 'How I Make Videos With AI': know what you want, get the whole draft once, fix one section at a time, listen at every join, finish where people see it and save a Skill. Use when a user wants to make, cut or edit a video from their files, especially someone who has never used an editing app.

FileKindSize
SKILL.mdskill md7.7 KB
motion-craft.mdmarkdown4.4 KB

motion-craft.md

View on GitHub
# Motion craft

Read this when a section has animated text, UI, charts or graphics, or when the user says the motion feels cheap, stiff or "like a template". These rules make motion feel designed. They never override the user's notes or `notes/style.md`.

Credit: the brief structure, springs, beat grid, subframe blur and gotchas below are adapted from @twoclipping's open prompt template for Opus 5.5 motion design (x.com/twoclipping/status/2103273003555402193).

## Brief it in tagged parts

When you plan a motion-heavy section, write its brief in `notes/` with these parts, and show it before you build:

- `<inputs>`: what you still need from the user (states, colours, the song). Ask; never invent.
- `<direction>`: the look in a few lines, and a **banned list**. Without one, a model falls back to its defaults: a centred title on a gradient, everything fading in together.
- `<structure>`: the beats in order, at the song's tempo, something happening on every beat.
- `<build>`: how it renders.
- `<gotchas>`: what usually breaks.

Show the state list laid on the beat grid before you write code.

## Rules

1. **Every value is a function of the frame.** In Remotion, compute position, size, radius and colour from `useCurrentFrame()`. No CSS transitions, no timers, no state carried between frames.
2. **Springs, not linear moves.** Use Remotion's `spring()`. A tiny overshoot at most; no bouncy easing. When a value changes target several times, add one spring per change rather than restarting, so the motion stays continuous.
3. **Stagger, don't sync.** The subject moves first; the camera, shadow and text follow a few frames later. Edges of a moving indicator can ride two springs so the leading edge stretches ahead.
4. **One element can carry the story.** Morphing one shape from state to state (size, radius, colour) reads as more designed than cutting between separate cards.
5. **Lock to the beat.** Measure the song's beat grid (for example with numpy) and start on a downbeat. Put big changes on beats and place each sound effect by its measured peak, not the start of the file.
6. **Motion blur on fast moves.** Use `@remotion/motion-blur` (CameraMotionBlur, about 4 to 5 samples) for fast moves only.
7. **Check one frame per beat before the full render.** Render stills on the beats into a contact sheet and fix anything off the grid, cramped or hard to read first.

8. **Holds still breathe.** Any shot held longer than about 2 seconds keeps a slow drift: a photo scales a few percent over several seconds, words float on separate phases, the light moves. Subtle and continuous; never jitter.
9. **Entrances settle; they don't swing.** Use near-critical damping and no rotation overshoot when something flies in. A swinging overshoot reads as camera shake.
10. **Make the key line an event.** The one line the video is about gets a real action, not a fade: something builds, breaks, and the answer arrives (for "not for the tech, for the people": tech glyphs circle the word, a slash, the word blows apart, and photos of people fly in and connect).

## Live Photos and phone clips

- Play a Live Photo once, then hold. Never loop it; the restart reads as a shake.
- Hold on the middle frame (the photo itself) and play only the last ~0.75 s before it. The start is often a shaky pan and the end a swipe.
- Steady handheld clips by smoothing the camera path (track motion between frames, smooth it with a moving average, move each frame by the difference, clamped inside a small crop). Locking every frame to the first one accumulates error and mirrors the edges.
- Live Photos are 13 to 30 fps and variable. Hold each source frame for the same whole number of output frames. Frame blending ghosts faces, and a plain frame-rate conversion judders.

## Gotchas

- In Remotion, `<Sequence>` resets `useCurrentFrame()` to 0 inside it. A scene written in the film's absolute times goes blank there; show it by frame range instead, or write it in local time.

- Don't put `will-change` on anything the camera scales, or text renders blurry.
- Text that swaps inside a morphing container needs its own enter and exit timing, or old and new text overlap.
- For a loop, make the last frame identical to the first, including any cursor's position and speed.

## Keep the user's footage first

These rules polish graphics around the user's real material. They never replace a photo, clip or recording with a drawn imitation, and the user's notes always win.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall