Techniques
The methods and rules that earned their place
50 ideas were collected from public repos, articles, posts and videos. These are the ones that survived a test against the studio's taste and were built into it, with where they live and who they came from.
- 39landed
- 8partly landed
- 6rejected
- 2queued
On this page
The rules we never break
Seven rules sit above every technique. A film that breaks one is not finished.
- 1
Deterministic frames
Every frame is a pure function of the frame number or the time. No CSS transitions, no timers, no random numbers (seeded random only). The same frame must always render the same pixels, so a still you inspect is exactly what ships.
studio/DESIGN_SYSTEM.mdstudio/eslint.config.mjsCLAUDE.md
- 2
One focal point
Each moment has one thing to look at, and the accent colour marks it. Stage, do not stack: the lower third leaves before the captions arrive.
studio/DESIGN_SYSTEM.md
- 3
- 4
- 5
- 6
A banned-effects list per film
The brief names what this film must never do (glows, particle bursts, bounce, stock-template looks), seeded from a global list. The reviewer checks it at the storyboard, after scene one, and on the final sheet.
skills/motion-studio/references/banned-effects.md
- 7
Methods that earned their place
Every card says what the technique is, why it is good and how well that is evidenced, where it lives in the repo, and who to thank. Evidence is honest: a technique shown in a finished film is stronger than one that is only claimed.
Nothing matches. Clear a filter or search for something broader.
Direction 9
Idea, hook, story and the look of a film before any code.
F-A11Concept triple (Idea, Device, Grammar) and kill-tests before any pixel
LandedOnly claimedSmall effort
The technique
A concept is three sentences: the Idea (what the viewer should believe, 8 words or fewer), the Device (one object that carries it through every shot, e.g. a dot handed from shot to shot that ends as the mark), and the Grammar (a rule the form obeys, e.g. opens and closes on the same tick).
More
Filled from an inventory of real specifics first, then three concepts through different lenses, then tests that kill weak ones (ownership, deletion, specificity, could a competitor say it). The companion tell catalogue lists borrowed props (rocket, lightbulb), demo without a cause, a recycled end card, and the device dropping out at a seam.
Why it earned its place
It stops "style posing as idea", which our three-directions step can still produce (three looks, no idea).
Evidence doc-level, with four worked concepts; reasonable, but the strength of the resulting films is only claimed.
What landed
Borrowed tells into banned-effects check (borrowed props, demo with no cause, recycled end card, device dropping at a seam). 10 itself not edited; 19 hands constraints to it. Added as fields and kill tests, not a new stage.
Credit Leonxlnx/cinetic, references/concept-and-story.md §1 to §6 and taste-and-slop.md A group; echris6/motion-video-kit motion-grammar.md (persistent actor rule).
Open in the research findings
F-A12Precedent-based taste rules from real rework
LandedShown in a finished filmSmall effort
The technique
A rule file where each rule has the rule, the case that produced it, and a self-check question.
More
The ones new to us and cheap to adopt: hold a brand wordmark a full second; batch entrances should accelerate, never move at constant speed, and end with a half-second rest; first drafts are almost always too fast, so default one notch slower; no handheld shake in bright UI films; at most one sheen or glint per hero, clipped to its corner radius; sharp text in 3D perspective needs high-resolution rasterising (layout-level zoom, never blame depth of field); no small source or disclaimer text on the last beat (it needs 2.5 s or more at half opacity or higher).
Why it earned its place
These are defects a reviewer repeatedly sent back, so they pre-empt rounds.
Evidence each rule cites a specific rework; first-hand but from one author's product-video projects.
What landed
Added checks: wordmark hold under 1 s, one sheen per hero, handheld shake, last-beat disclaimer 2.5 s. Approved rules go to learnings.md via 70. Merged with existing learnings spirit; rubric lines belong to motion-review.
Credit Vincentwei1021/video-shotcraft, references/aesthetic-rules.md R1 to R4, Q2 to Q5; Vincentwei1021/anything2explainer reference/lessons.md.
Open in the research findings
F-A13Pacing norms as numbers (shot length, energy curve, one earned stillness, accent share)
LandedEvidence not ratedSmall effort
The technique
A table of norms the author measured on professional launch films: median shot about 1.5 s, a new visual beat about every 0.7 s (calm default about 1 s), first frame already moving, first readable word near 0.4 s, product on screen by about 3 s unless a problem act earns the wait, two energy peaks with a designed lull near 65
More
percent and the biggest peak near 82 percent, low-energy stretches under 4 s, one earned stillness of about 1.0 to 1.6 s on the key claim followed by the biggest spike, accent colour about 5 percent of pixels, end card about 2 s with a 0.6 to 1.3 s hold and at most 6 percent creep, repeated reveals about 40 percent faster the second time.
Why it earned its place
It gives storyboards and reviews numbers to check instead of feel; "spend stillness once" is particularly useful. Caveat: the source films are not named in what I read and the numbers are the author's claim.
What landed
Pacing norms in rubric as reading points; forensics supplies the numbers (median shot, still share, hard cuts). Explicitly not pass/fail, except the spent-once stillness rule. Combined with F-C5. Reference table only, not pass/fail gates; source films not named, author's claim.
Credit Leonxlnx/cinetic, references/craft-rules.md §1 and the at-a-glance table.
Open in the research findings
F-B2Negative constraints as the quality lever (a banned list per film, in the direction tag)
LandedShown in a finished filmSmall effort
The technique
The prompts spend as many words on what must not appear as on what must. The photo-print film bans crossfades, blur-ins, brightness "developing", 3D flips, particles, glows, holds over 1 s and "anything that looks like a template"; the UI loop bans bouncy easing, gradients on chrome, mismatched icon strokes and dead time.
More
The ban list is written for the specific film, not generic.
Why it earned its place
Bans remove the model's defaults (fade, glow, particle burst), which is exactly where "AI look" comes from. Our design.md has a global ban list but the per-film list is not a required brief field.
Evidence shown in finished films by two authors; the causal claim ("bans keep it premium") is the gallery's reading, not proven.
What landed
Reviewer rubric change (check the film's own list) is outside prompts/. Mechanism adopted, other authors' specific bans (no serif etc.) not. Rubric check belongs to motion-review.
Credit prompt-motion.com/twoclipping-221cab, prompt-motion.com/twoclipping-5cba86 (zero @twoclipping)
Open in the research findings
F-B8Beat map first: "something happens on every beat", BPM, bar count, and the song's drop as a structural anchor
LandedOnly claimedSmall effort
The technique
The briefs fix BPM and total beats (120 BPM, 7 bars or 54 beats; 130 BPM, 32 beats), start the song a stated number of beats before its drop (12 beats before), and write the structure as beat ranges. The zoom lands on the drop, a quiet breakdown carries the hold scene, the opening word returns on the beat when the loop restarts.
More
The first deliverable shown to the user is the beat map.
Why it earned its place
It makes sync a property of the plan rather than a late edit; our hits-table practice already supports it but the storyboard template does not ask for beats-first on music-led films.
Evidence consistent across four films; sync quality not verified by me.
What landed
Voice-led films explicitly excluded. Not for voice-led films; no dead time does not mean constant motion.
Credit prompt-motion.com/twoclipping-5cba86, prompt-motion.com/ultimaxbt-2ddf1e (zero, ultima)
Open in the research findings
F-B9Perfect-loop discipline: last frame equals first, including cursor position and speed
LandedOnly claimedSmall effort
The technique
Two films end by returning the same objects to the opening state (wordmark returns to the dot, orange dot goes back through halftone, graph and toggle). The gotchas call out the loop stutter causes: cursor position and cursor speed must match at the seam, accent, cursor and type identical in first and last frame.
Why it earned its place
We already note "end by re-setting the opening word in its exact frame-0 position". The new part is the checklist (cursor speed, not only position) and the loop test: diff last frame against first and render a loop-twice draft.
Evidence stated in the prompts; films posted; seam quality not verified.
What landed
Frame-diff tool itself belongs to qa.md on the skills side. Loop-twice preview uses existing inspect.mjs probe frames.
Credit prompt-motion.com/twoclipping-5cba86, prompt-motion.com/ultimaxbt-bbebf5
Open in the research findings
F-C5Vary tension and pacing; keep the polish checklist, drop the dogma
LandedShown in a finished filmSmall effort
The technique
The most-read polish list (five rules: crossfade every cut, one expo-out curve everywhere, film grain and vignette, targeted SFX on chapter cuts only, cut scenes that do not earn their place within about 3 seconds) paired with its own best criticism: AI motion has "terrible pacing", a single even easing gives a bouncy,
More
tensionless ride, with no sharp cuts or short fades. The poster agreed and added hard cuts by hand.
Why it earned its place
The criticism is more useful than the list. Both the 64-vote polish post and two separate comments (on a 30 s launch video and on the 97-vote lower-thirds post, which was heavily criticised as generic and likely to look dated) describe the same fault: even rhythm and long fades.
Evidence the fault is widely reported; the fix is judgement, not a recipe.
What landed
Pacing and tension variance section and checklist: name the hard cut and the fast fade, same duration everywhere flagged, one easing everywhere flagged; crossfade-everything and one-easing-everywhere rejected as rules. Combined with F-A13. Earns-its-place test, flag equal transition durations, SFX only on structural moments. Crossfade-everything and one-easing-everywhere rejected.
Credit u/Top_Commission_8567, www.reddit.com/r/ClaudeAI/comments/1tik0qe/ ; critics u/kylecito (same thread and www.reddit.com/r/ClaudeAI/comments/1t51k8s/ ) and u/Historical_Moose_468 and others at www.reddit.com/r/ClaudeAI/comments/1tn9tyy/ .
Open in the research findings
F-C11Real screen recordings and real assets over synthesised UI
LandedOnly claimedSmall effort
The technique
For product walkthroughs, composite real screen recordings (with code-made cursor, callouts and zooms) rather than redrawing the whole interface, and when stuck on generic graphics, feed real screenshots and brand images and let Claude only animate and layer them.
Why it earned its place
Three separate commenters say fully synthetic UI looks fake and that generated SVG graphics look generic.
Evidence opinion from several people, no test. Also a counter-signal: one builder rendered the app's own components in the film and was happy with it, so "synthetic" is fine when it is the real code.
What landed
61 could take one line next round; start gate and storyboard already list captures. Real components rendered in the film are fine.
Credit u/MoonLabsApp and others at www.reddit.com/r/ClaudeAI/comments/1sya1rc/ ; u/EvolvinAI29 at www.reddit.com/r/ClaudeAI/comments/1t6cvgv/ ; u/Tarun122 at www.reddit.com/r/ClaudeAI/comments/1t51k8s/ .
Open in the research findings
F-B10One thread object + curve drawn from the motion function (proof, not illustration)
Partly landedShown in a finished filmMedium effort
The technique
A single dot is the connective element through a UI toggle, a letter, a spring graph, a growing shape and the end card; the graph is traced by the same spring function that moves the dot, and the circle, rotating square and pill are states of one shape that keeps its position.
More
Motion not attached to something already on screen is banned.
Why it earned its place
It gives a 15 to 20 s multi-technique piece a spine, and the curve-from-same-function rule makes technique demos self-proving. Already captured in the studio showreel inspiration (rules 1 and 5), so value now is making it a reusable component and a showreel-brief default.
Evidence shown in a finished film; rule already adopted in our brief.
What landed, and what did not
Component work left to the studio integrator. Covered conceptually by the Device field; ThreadDot and SpringGraph components belong to the studio code owner.
Credit prompt-motion.com/ultimaxbt-bbebf5 (ultima @ultimaxbt)
Open in the research findings
Camera 1
Moving the world, not the objects: speed curves, zoom and framing.
F-B4Camera driven by an integrated speed curve with a target table, verified by optical flow
LandedOnly claimedMedium effort
The technique
Instead of position keys, the 3D fly-over prompt gives a table of speed as a share of cruise at timestamps (0 at 0 s, 0.5 by 0.6 s, 1.0 by 1.6 s, held 0.94 to 1.1, easing to 0.12 at 8.3 s) and integrates it into position; zoom runs in log space; the rise and dive are separate eased passes that pin an edge of the page to a fixed
More
screen line. The check: measure a quick 30 fps preview with optical flow and require that the speed never dips and the zoom never turns into zoom-in during the flight.
Why it earned its place
Our learnings already have the integrated smoothstep speed curve; what is new is (a) the speed table as the brief's camera language and (b) optical flow as an automated test for "no surges, no stops", a defect that stills and contact sheets cannot show.
Evidence described precisely in the prompt, the film was posted; flow-test results not shown.
What landed
flow = global affine Lucas-Kanade pyramid on a 30 fps copy, speed in frame widths/s incl. zoom, speed dips, zoom reversals, plot. Verified on synthetic pan-with-stall (dip found at 2.03-3.03 s, truth 2-3 s) and zoom reversal (found at 3.03 s, truth 3.0 s). Not a real-camera test beyond the two drafts; local type animation is skipped as non-camera. Speed-table format for briefs left to the motion-studio/director docs. Speed-table brief format could be a later line in 40 once the tool exists. Flow tool is integrator 1's (inspect.mjs flow); table format is the new part, integrated curves already in learnings. The optical-flow check is not built (needs ffmpeg or OpenCV tooling outside studio/).
Credit prompt-motion.com/twoclipping-d89be5 (zero @twoclipping)
Open in the research findings
Transitions 3
How one scene becomes the next.
F-A6Velocity-matched cut and measured entrance/exit curves
LandedEvidence not ratedSmall effort
The technique
The outgoing shot accelerates in one direction and is cut at its fastest frame; the incoming shot starts already moving the same way and brakes to rest, so momentum crosses the edit.
More
Numbers given: exit speeds up about 1.1 to 1.2 times per frame over the last 16 to 24 frames, ending at 25 to 40 px/frame at 60 fps (never above 60); entry starts at 30 to 55 px/frame and decays about 0.92 to 0.94 per frame; text inside a moving shot must be under 20 px/frame by the time it is read; the cut is also an act boundary so motion-blur samples never straddle it. Companion rule: a hard cut works when subject, scale, direction and material continue across it.
Why it earned its place
It turns "make smooth transitions" into numbers and explains why some dissolve-free cuts feel dead. The numbers come from the author's frame measurements of professional films (claimed); the recipe itself is easy to test.
What landed
Add to 41 when vocabulary is next touched. Helpers (velocity-matched cut) referenced as studio/src/lib/transitions.tsx (integrator 3). Numbers are author-measured at 60 fps. Numbers are the source author's claim. Verified by stills: cut frame blurred and sliding, entry brakes. Entry ends with a small residual speed (about 2.6 px per 60-fps frame) with the 18-frame entry.
Credit Leonxlnx/cinetic, technique entry tr-velocity-handoff-cut and references/craft-rules.md §2, §4; echris6/motion-video-kit, motion-grammar.md rules 4 and 5.
Open in the research findings
F-A7Hidden-cut and no-cut transitions (occluder cut, impact slam, light-leak burn, line carry)
LandedDocumented methodMedium effort
The technique
Four recipes with parameters. (A) A soft, out-of-focus foreground object sweeps across and the hard cut happens inside the frames where it covers the screen, with a drag of about 28 px before and a settle after so it reads as one take.
More
(B) Two half-screens with a slanted seam collide: white flash 3 frames, screen shake about 16 px decaying over about 5 frames, a stamp, all on the same frame (a one-frame offset scatters it). (C) A warm diagonal light leak ramps up slowly (ease-in), the cut hides at the peak, and it recedes faster; the old picture must also wash out (brightness up, contrast down) or it reads as a sticker. (D) A progress bar extends out of frame, the camera follows the line, and the line turns corners to draw the next scene's card frame: no cut at all, with the pen tip pinned near x=1480 so it never leaves or lags.
Why it earned its place
Each carries a cause before and a result after, and the failure modes are written down (ease-in on the leak, three impact elements on one frame).
Evidence doc-level cards with the author's tuned frame numbers plus reference demos; the author notes parameters were tuned on placeholder material, so treat them as starting points.
What landed
Entries for 41 later. Impact slam limited to comparison moments and counted in the 3 full-frame hit cap; light-leak must be tinted and flare-free. Line carry (D) needs the scenes to draw the line, impact slam (B) and light leak (C) conflict with the no-glow, one-accent rules: deferred or rejected in this library.
Credit Vincentwei1021/video-shotcraft, references/shots/transition/transition-hidden-cut.md and line-carry-transition.md (github.com/Vincentwei1021/video-shotcraft). Credit: Vincentwei1021. Cards are written in Chinese; I read and paraphrased them.
Open in the research findings
F-B3"Every scene is made out of the previous one" as a hard structural rule, with an explicit morph vocabulary
LandedShown in a finished filmSmall effort
The technique
One continuous take, zero cuts or fades: text rises out of a mask line, an icon pops from zero on a spring, bars draw across, a page pushes in, a black shape floods the frame and contracts into the next scene, a circle becomes a square becomes a bento, a button carries its label into the next page, a lime flood carries a copy of
More
the bubble's words. The brief lists each hand-off as "A becomes B".
Why it earned its place
Writing every transition as a named shared element in the structure tag is what removes crossfade defaults, and a hand-off list is checkable in a contact sheet (does frame N-1 contain the thing frame N grows from?). We already have shared-element transitions as a concept; this adds the discipline: the storyboard transition column must be "X becomes Y", never "cut" or "fade".
Evidence shown in two finished films (photo print, food craving); the studio's own inspiration file already adopted the idea as rule 2.
What landed
Morph vocabulary additions go to vocabulary.md (skills side); 41 not edited. Strict for UI and product pieces; type pieces may still hard cut onto a set page.
Credit prompt-motion.com/twoclipping-221cab, prompt-motion.com/ultimaxbt-2ddf1e (zero, ultima)
Open in the research findings
Typography and copy 5
What the words say, how many, and how they arrive.
F-A2Fragment-chain copy grammar and a hard word budget
LandedEvidence not ratedSmall effort
The technique
Film copy never lands as a sentence. It arrives as fragments of 1 to 4 words with a picture beat between them, in one of two modes: "build" (fragments append to a held line, the newest in the accent, the line re-centres once per fragment) or "replace" (each fragment leaves whole, the next takes the same centre).
More
Recipes: the animation is the verb (words before and after the demo, never describing it), the cliffhanger cut (the picture delivers the payoff word), stem plus rotating slot instead of a list, an image standing in for a word, one giant keyword per film. Budget: about 15 to 25 words for a 30 s launch, 6 or fewer for a muted loop, no more than about 8 words readable on one frame, and a "subtitle film" smell test (copy on more than about 65 percent of frames fails).
Why it earned its place
It is a concrete, checkable answer to text walls and to captions that fight the picture, a common amateur tell. The numbers come from a frame-by-frame study of eight professional films (the author's claim; I could not check those films) and are enforced by a string audit and a layout audit in the author's pipeline. Their blind evaluation credits the ideas and story quality of films made this way, though a neutral judge preferred the baseline in two of four rounds, so evidence for taste is mixed and for discipline is good.
What landed
Copy bans kept as defaults, not laws. Author's no-question ban not adopted. Numbers are the author's measurement. Build mode measures widths with a canvas (needs the loaded font). Recipes (cliffhanger cut, stem plus slot) are prose in the skills, not code.
Credit Leonxlnx/cinetic, references/copy-and-type.md §1, §2b and taste-and-slop.md B4, B8, B9. Credit: Leonxlnx.
Open in the research findings
F-A5A video-native brand spec ("frame.md"): frame-relative type ramp, one accent per frame, text floor
LandedShown in a finished filmSmall effort
The technique
A published launch-video project argues that web design specs make agents build slides (cards, pills, panels).
More
Its fix is a second spec that keeps the brand atoms (colours, type family) and re-expresses scale for a 16:9 frame: sizes in frame-relative units (vw), a hero ramp far larger than the reading ramp (wordmark 30vw, display 14vw, claim 6 to 9vw, stat numeral 18vw), a hard text floor (1.4vw at 1920 wide; chrome labels may go below), a safe area in vw, named easings and durations, and the rule that the accent colour appears once per frame. Motto: atoms are sacred, composition is free, numbers come from the script.
Why it earned its place
It gives the agent a ramp that cannot collapse into a web page layout, and it matches our "one accent" rule in a testable form.
Evidence shown as source of real launch compositions (viewer links were not opened, they are JS viewers); the reasoning is stated in a handoff doc.
What landed
Studio integrator. Rule landed in skill docs; tokens.ts and DESIGN_SYSTEM.md belong to the studio code owner. Numbers are one project's, to be tuned. claim set to 6.5 vw (source 6 to 9) so five words fit the safe area; one accent per frame stays a documented review rule, not enforced in code.
Credit heygen-com/hyperframes-launches, claude-paper-launch/FRAME-claude.md and frame-md-launch-storyboard/HANDOFF.md (github.com/heygen-com/hyperframes-launches). Credit: HeyGen.
Open in the research findings
F-A16Rhythm and type-sync recipes (shooting on 3s then 1s, trailer bumper, karaoke fill, weight pump)
LandedShown in a finished filmMedium effort
The technique
Four small, distinctive recipes. (1) Frame-rate shift: a mover steps every 3 frames (about 69 px per step, a different pose each step) and switches in one frame to every-frame motion with hard overshoot and stretch, so the change of cadence is the highlight; under 30 px per step it reads as dropped frames, and any tween on the
More
switch kills it. (2) Trailer bumper: three framings of 9 frames each, zero transitions, each pushing in 1 to 4 percent so it is not a slideshow, then 6 frames of pure black, then the title. (3) Karaoke fill: each word fills left to right with a soft edge at speaking rate, current word in accent, finished word in ink, a pointer underline on the active word; word times come from the voice, gaps of 4 to 10 frames for breath. (4) Font-weight pump: a variable-font weight envelope on the beat (about 250 to 900), glyphs set in slots laid out at the heaviest weight so the line never reflows; beats must be spaced wider than the decay window.
Why it earned its place
All four are cheap, deterministic and look authored rather than templated.
Evidence documented with Remotion demos; I did not see their output, and the author says parameters were tuned on placeholder material.
What landed
Add treatments to 63 when a component exists. Component work (word-fill mode in WordStagger or Captions) is integrator 3's.
Credit Vincentwei1021/video-shotcraft cards rhythm/sakuga-timing-shift.md, rhythm/trailer-grammar-moves.md, typography/type-rhythm-sync.md.
Open in the research findings
F-C13Captions on cut audio need their own chunking
LandedOnly claimedSmall effort
The technique
Off-the-shelf caption pages split on natural pauses in speech. After cutting between takes the pauses vanish, and one run put 188 words on a single caption page for about 2 seconds. The fix was custom chunking logic.
Why it earned its place
A precise, easily reproduced failure.
Evidence described by the author, not shown.
What landed
51 could take a max-words rule if it ever bites. Maybe-level: our line-by-line Kokoro clips sidestep it. Caption component notes are integrator 3's. Opt-in props maxPageMs and breakOnSentence, defaults keep old behaviour; not tested against real cut audio.
Credit u/FerretVirtual8466, www.reddit.com/r/ClaudeAI/comments/1ry69qi/ .
Open in the research findings
F-C14Hold the box when text types in
LandedShown in a finished filmSmall effort
The technique
For a typewriter effect, render the full text invisibly to fix the container height and overlay the typed characters on top, so the card does not jump as lines wrap.
Why it earned its place
A one-line, well-known layout trick, reported as the fix after the poster saw the card moving.
Evidence shown in the post text; tiny.
What landed
Applies only if a typed-text component is built. Typewriter cursors as decoration stay banned. Verified by stills: two-line box and accent rule stay fixed while typing. No cursor by design.
Credit u/Tarun122, www.reddit.com/r/ClaudeAI/comments/1t51k8s/ .
Open in the research findings
Sound 5
Hits, music, mix and sync.
F-A8Sound cues computed from the animation itself, plus physics-based audio timing
LandedShown in a finished filmMedium effort
The technique
Sound events are never placed by hand. A sync module computes the contact frame of each spring, the 50 percent frame of each pop-in and the velocity peaks of each whip from the same constants and spring functions the picture uses; the cue export feeds the score.
More
In the long historical film, sound cues are derived from the picture's events (each gun, volley, hoofbeat) and delayed by distance at 343 m/s, filtered and panned by position.
Why it earned its place
Sound sync becomes a property of the code, so retiming the animation retimes the sound. Our hits table is hand-authored; this would generate it.
Evidence the cue-export design is documented with sync-audit tolerances (lag up to 48 samples); the historical film is shown on X per the gallery, but I could not watch it.
What landed
Sfx.tsx helper is code. Adopt for UI films with many micro-hits; narrated films keep the hand-authored hits table. Sfx.tsx helper is integrator 3's.
Credit Leonxlnx/cinetic README ("One beat grid, measured sound") and references/sound.md; WinterArc21/Battle-of-Austerlitz-Film README (web/events.js description).
Open in the research findings
F-A9Rigorous beat-grid method and a cap on full-frame beat hits
LandedShown in a finished filmMedium effort
The technique
For a track you did not write: fit a straight line to the detected beat times by least squares, report the residual (accept up to about 15 ms), check half-time and double-time candidates by whether kicks land on whole beats, separate the drum stem for dense mixes, classify onsets by band (kick drives impacts, snare drives swaps
More
and flash cuts, hi-hat drives micro-motion density), keep float seconds until the last step into frames, and measure cut error after rendering (target 3 frames or less). A feedback-derived rule: beat sync does not mean pulsing the whole picture every beat; full-frame or camera-layer impacts at most 3 per film, at least 16 beats apart, the rest only on the hero element. A separate UI-morph-loop guide adds: the last frame, including cursor position and velocity, must equal the first.
Why it earned its place
It is a complete grid-acceptance step the studio lacks, and the 3-impact cap is a hard, evidence-based fix for beat-frequency jitter that kinetic pieces are prone to.
Evidence documented, with a 70 s, 18-shot film reported with all cuts within 2.2 frames (author's measurement) and a user complaint cited as the origin of the cap.
What landed
Landed: sync reports full-frame hit count (max 3) and min gap in beats (16, via --bpm), loop seam in forensics, rubric line. Deferred to prompts/50 and audio.md owners: beat-grid fit, half/double-time check, band-classified onsets. Cap is a user-feedback rule from the source. Our own music.mjs grid is exact; the acceptance steps are for imported tracks.
Credit Vincentwei1021/video-shotcraft, references/music-beat-sync.md, aesthetic-rules.md R4; opusvideo/awesome-claude-video, IMPLEMENTATION_GUIDES.md (UI morph loop case, original post by @twoclipping on X, not opened).
Open in the research findings
F-A15Silence and restraint as sound recipes (one soft sound per text fragment, dropouts spotlight a claim)
LandedShown in a finished filmSmall effort
The technique
House sound style from frame-measured films: one soft sound per text fragment, near-silence while it is read, a big hit only for the one reveal, the lockup is a stop-down plus one clean element, no pitch climbing in a stacked lockup.
More
Spotlight with silence instead of effects: cut a statement card 3 to 12 frames into a 12 to 24 frame hole in the music and bring the beat back about 17 frames later, or give a key claim a 2 to 4 beat bass and kick dropout and land the next visual event on the returning downbeat; mute the sub 12 to 18 frames before the hardest cut and release it on the cut. A calm film can be mastered effects-only at about -18 LUFS.
Why it earned its place
A concrete alternative to "add more SFX", which is how films get busy.
Evidence documented, with a warning rule in the score script; the underlying measurements are the author's.
What landed
Calm effects-only profile mentioned in one clause. Calm-profile -18 LUFS must be stated in the delivery report.
Credit Leonxlnx/cinetic README ("Sound") and references/craft-rules.md §1 item 11.
Open in the research findings
F-B11Voice pipeline details: multiple full takes, per-line regeneration, pause shortening, onset-aligned segment-wise Whisper
LandedShown in a finished filmMedium effort
The technique
Four full-script takes for the user to choose from; a bad line is regenerated 4 times and the best one spliced in; pauses over 0.28 s shortened to 0.2 s; phrase levels pulled 85 percent toward the median using gain changes only inside pauses; word timing from splitting the read at pauses of 100 ms or more, transcribing each
More
segment separately, and aligning each segment's first word to the measured onset (a single Whisper pass is said to place words up to half a second late). Music ducked with a 3-band sidechain (lows 30, mids 85, air 55 percent, 0.3 s hold, 50 ms look-ahead, 0.5 s release) and the voice checked at about 9 dB above music between 300 Hz and 4 kHz per phrase.
Why it earned its place
Our voice.md has Kokoro with 3 to 4 cast samples and plain faster-whisper, and learnings record Whisper misheard one-word lines. Segment-wise alignment to measured onset and the per-phrase voice-to-music ratio check are measurable improvements.
Evidence described precisely in a finished film's prompt; the "half a second late" figure is the author's claim and I did not test it.
What landed
3-band ducker not adopted; cloud TTS rejected. ElevenLabs parts rejected (cloud, keys). 3-band duck optional and untested; half-second-late claim is the author's.
Credit prompt-motion.com/rossaxbt-3085b7 (testarossa @rossaxbt)
Open in the research findings
F-C3Let the picture lead the voice slightly
Partly landedOnly claimedSmall effort
The technique
When a visual is tied to a spoken phrase, start it a fraction of a second before the word, because people expect light to arrive before sound. The commenter suggests about 250 ms for text that accompanies a phrase.
Why it earned its place
It targets the commonest tell of voice-led work: captions and cuts that land exactly on the word feel late.
Evidence only claimed (one comment, no demonstration), but it matches how real editors treat J-cuts and anticipation, and our own hits-table method makes it cheap to test. Do not take 250 ms on faith: for a hard cut or a caption, 80 to 150 ms (2 to 5 frames at 30 fps) is a more usual starting range; a slow reveal can lead by more.
What landed, and what did not
To be A/B tested on the next narrated film, then recorded in learnings.md. Marked to be A/B-tested at 80 to 150 ms, not a fixed rule; current 60 ms word lead stays.
Credit u/Possible-Tone-7627, comment on www.reddit.com/r/ClaudeAI/comments/1tn9tyy/ (post by u/Silver-Range-8108).
Open in the research findings
Pipeline and tooling 6
Scripts, helpers and measured checks that remove guessing.
F-A3Measure motion instead of guessing: velocity plot, and the "buoyant bob" ease
LandedShown in a finished filmSmall effort
The technique
When a move "pauses then snaps", plot position and velocity over time instead of reasoning about it.
More
In a production write-up, five intuitive fixes failed over about an hour; a debug overlay graphing velocity showed zero velocity for 16 percent of the move; the cause was a bob sine covering only the rise phase, fixed by spanning the whole lifetime. The same article's reusable ease: a cubic ease plus a half-sine bob so a rising element keeps drifting through its peak instead of freezing ("buoyant").
Why it earned its place
It replaces the commonest failure mode (an agent retrying eased variants blind) with a 30 second visual check.
Evidence one detailed first-hand production article with numbers; it names no capture tool and I did not see the film.
What landed
buoyant() helper and motion-plot tool are code, not prompts. buoyant() helper referenced as studio/src/lib/motion.ts (integrator 3); plot via inspect.mjs plot. Constants are our own reading of the write-up (bob 0.03). inspect.mjs had no plot subcommand when checked; JSON shape is {name,fps,unit,startFrame,values[]}, whoever adds plot should read that.
Credit Samuel Parks, RapidEye, "Building our launch video with Claude" (rapideye-seo-tools.pages.dev/blog/building-our-launch-video-with-claude/).
Open in the research findings
F-B12Eight motion-blur subframes for fast moves, plus "slow the move down" as the alternative
LandedEvidence not ratedSmall effort
The technique
Two authors independently found that 4 subframes leave ghost copies on fast moves; they render 8 subframes (the fly-over uses 16 across 0.7 of a frame, a shutter angle below 360 degrees) and slow the move down if ghosting remains.
Why it earned its place
Our engine and motion.md standardise on 4 subframes. For flood transitions, wipes and drags, 4 is the likely cause of visible stepping. Making subframe count and shutter fraction per-shot parameters (8 for fast moves, 4 elsewhere) costs render time only where needed.
Evidence stated in three prompts as a known gotcha; I did not measure our own output.
What landed
Skills/engine integrator owns it. Per-section blur=8 render; per-frame shutter control is not in the template yet. @remotion/motion-blur 4.0.537 exists (MIT, about 24 KB), unvetted and not installed; velocityCut uses a cheap SVG directional blur instead.
Credit prompt-motion.com/ultimaxbt-2ddf1e, prompt-motion.com/twoclipping-d89be5
Open in the research findings
F-C12Web-embed delivery checklist
LandedShown in a finished filmSmall effort
The technique
First-hand fixes for a short landing-page loop that played in Chrome but showed black in Safari: use the H.264 High profile, add -tune grain so dark fades do not band, rename the file on re-export so Safari forgets a cached failure, use preload="metadata", and check the size in the network panel (the final file was about 700
More
KB).
Why it earned its place
Concrete and checkable.
Evidence shown by the author's own debugging (4 hours, 19 commits). I would not accept the diagnosis as written: "Safari hates Baseline" is doubtful; the usual causes of a black Safari video are the pixel format (needs yuv420p), a missing -movflags +faststart, and serving without byte-range support, and our own notes already cover range requests for the player.
What landed
delivery.md equivalent is skills side. The doubtful browser-profile claim was omitted and replaced by pixel format, faststart and range requests.
Credit u/Vitalic7, www.reddit.com/r/ClaudeAI/comments/1sq0xcz/ .
Open in the research findings
F-B6Per-scene tuning page with a slider for every number, render only when it looks right
Partly landedShown in a finished filmMedium effort
The technique
Each scene was built as a small web page where every numeric value (size, spread, gravity, easing, per-logo scale) had a slider; the author tuned live and asked for a render only when happy. One scene with a count slider produced 8, 30, 80 and 200 item variants of the same physics for four different cuts.
Why it earned its place
It moves taste decisions from prompt rounds to direct manipulation and makes density variants free. In Remotion this is a props schema plus the Studio's props panel (zod schema), which is the same idea natively.
Evidence written up by the author of a finished launch video; only one source.
What landed, and what did not
Revisit when a scene needs live tuning. Remotion side landed; the HTML player ?tune panel is deferred.
Credit rapideye-seo-tools.pages.dev/blog/building-our-launch-video-with-claude/ (Samuel Parks)
Open in the research findings
F-B16Transparent-background renders for overlays and stingers (alpha export)
Partly landedOnly claimedSmall effort
The technique
Two sources render Remotion output with alpha: a Remotion tutorial for lower thirds and subscribe animations into Final Cut, Premiere or CapCut, and the RapidEye pipeline (4K 60 fps transparent ProRes 4444 into After Effects as a layer).
Why it earned its place
Lets us use the studio library as an overlay generator (lower thirds, stingers, titles) over live footage, a use the repo does not document.
Evidence claimed by two sources; neither verified by watching.
What landed, and what did not
Would be a delivery.md section. Flags untested; the doc says run one test render before relying on it.
Credit www.youtube.com/watch?v=kXmY6yQa5q4 (channel inferred as Pouya Eti, via videohighlight summary); rapideye-seo-tools.pages.dev/blog/building-our-launch-video-with-claude/ (Samuel Parks)
Open in the research findings
F-C9Additions to our scene spec from the Animation-Workflow repo
Partly landedShown in a finished filmSmall effort
The technique
The repo (read in full) structures a video as: a spec per video with an overview, a colour-flow table (section, time, dominant colour, mood), per-scene blocks (narration, frame-range visuals, components, notes) and a list of placeholder locations where real footage will replace animation; a style guide with enforced minimum type
More
sizes; a "visual philosophy" file with a density scale (sparse, medium, dense) and named anti-patterns (motion sickness, effect soup, dead air, distraction); and a component registry whose core components enforce the style guide by construction (a text variant cannot be set below its minimum size) with a promote-to-core rule.
Why it earned its place
Evidence shown, because the files exist and are consistent, and the author reports over ten minutes of script-aligned animation in about an hour (a claim, 6 votes). Most of it we already have in stronger form (tokens, DESIGN_SYSTEM.md, safe areas tuned for 9:16, storyboard template with hits table, prompt 31). The registry's rule "check the registry before building; core components enforce the style guide" is already how remotion-studio is written.
What landed, and what did not
Templates/storyboard.md and DESIGN_SYSTEM.md are not owned here. Anti-pattern review flags belong to motion-review; clamp inside text components is a note for the studio code owner. Source's fixed sizes and colour-psychology table not adopted.
Credit u/VanCliefMedia (repo RinDig/Animation-Workflow), www.reddit.com/r/ClaudeAI/comments/1qyseq3/ and github.com/RinDig/Animation-Workflow (read via gh api, not run).
Open in the research findings
QA and review 7
Judging the render, with a reviewer who did not build it.
F-A1Pixel forensics on the rendered MP4 (frozen time, pops, ghosts, judder, banding, loop seam), with declared intent
LandedDocumented methodMedium effort
The technique
A script reads the encoded video and the cue list and flags frame-level defects that contact sheets hide: stretches where nothing changes, one-frame pops (a value jumps in a single frame), ghost frames next to cuts, judder, banding, and a loop that does not close.
More
The author declares designed moments (a flash cut, a planned freeze) in a small qa.json with a reason each, so thresholds stay strict for everything else. A simpler cousin measures the longest "dead" stretch per shot and the settle time before an exit (mean grey change on a 320x180 copy; under about 0.35 counts as still).
Why it earned its place
Three independent repos converged on it. The critic-loop kit reports that about 10 of 36 seconds of one film were effectively frozen and none of the builder's own checks flagged it; the explainer kit reports beat-timing and dead-stretch defects that only measurement found. Our QA is look-at-stills plus loudness; a 2 s freeze between two good stills passes it.
Evidence doc-level, with reported real defects; I did not run the scripts.
What landed
forensics implements still holds, pops, one-frame flashes, ghost frames, judder (repeats + irregular pts), banding, loop seam, hard-cut shot lengths, declared-intent qa.json, flagged contact strip. Self-test on B and C drafts found real still holds and a slow open; banding is a heuristic score, judder near-stalls are pointers only. Tooling (forensics.mjs, qa.json) belongs to other integrators. Skill docs reference inspect.mjs forensics and declared designed moments; the tool itself belongs to the motion-review integrator.
Credit Leonxlnx/cinetic, skills/cinetic/references/review-loop.md (github.com/Leonxlnx/cinetic); echris6/motion-video-kit, quality-bar.md and gauntlet.md (github.com/echris6/motion-video-kit); Vincentwei1021/anything2explainer, template/scripts/motion_check.py and reference/agent-qc-rules.md (github.com/Vincentwei1021/anything2explainer).
Open in the research findings
F-A10Verification critic and a ledger (fresh judge per round, FIXED / PARTLY / STILL PRESENT)
LandedShown in a finished filmSmall effort
The technique
Each review round uses a new critic that gets only the artifact, the brief, references and (in verification rounds) the previous report, never the builder's reasoning or a list of what was fixed.
More
The verification critic marks each earlier item FIXED, PARTLY or STILL PRESENT, hunts for regressions, and ends with SHIP or ONE MORE PASS (at most 3 fixes). Critics also look at dense windows (every 1/30 s) around each transition. A one-table ledger (round, artifact, top findings, change, measured result) is kept. Companion limits: one round after the machine gates pass, then ask before a second, hard stop around 3 to 5 rounds.
Why it earned its place
We already use a fresh reviewer; the delta is the verification-round template, the regression hunt (the repo lists real examples: a covered element losing its z-order, a moved object crossing a headline) and the stop rule.
Evidence documented with listed defects the critic caught; sample films exist but I did not see them.
What landed
Verification rounds (FIXED/PARTLY/STILL PRESENT, at most 3 fixes, dense windows), ledger table in review.md, one-round-after-gates then ask, hard stop at 6. Builder passes only the previous defect list. 13 not edited; agent.md owned elsewhere. Owned by integrator 1; stop rule already in review.md.
Credit echris6/motion-video-kit, references/gauntlet.md, critic-prompts.md (adapted there from a public "Gauntlet loop" idea I did not open); Leonxlnx/cinetic review-loop.md; Vincentwei1021/video-talkcraft changelog (one round then ask, 2026-09-11).
Open in the research findings
F-A14Off-by-one traps checklist for frame-driven animation
LandedEvidence not ratedSmall effort
The technique
Bugs with root causes from real rework, almost all frame arithmetic: fadeIn(0) returns 0 so the first frame of a shot is empty (start soft at 25 to 57 percent); a faded exit that leaves 40 to 57 percent opacity on its last frame pops at a hard cut (use 1 - (n/N)^1.5); first elements of a shot should start on the shot's first
More
frame, not wait for the caption start (otherwise an empty beat at group boundaries); an element rendered twice (one steady, one glitching) hides the effect; do not wrap an already-ramping component in a second fade; keyframe tables must start with an off-screen value at shot start or the element parks on screen early; slide-ins from below travelling more than about 120 px cross the caption band; do not change words after frame numbers are hard-coded; check how many frames the last beat has left before giving it a long animation.
Why it earned its place
Each item causes a visible defect that stills at the wrong frame miss, and all apply to Remotion directly.
What landed
Skills integrator. Comments in motion.ts belong to integrator 3. Written as a header comment plus softFade and exitOpacity helpers; the skill-side determinism.md part belongs to another owner.
Credit Vincentwei1021/anything2explainer, reference/lessons.md and agent-build-rules.md (github.com/Vincentwei1021/anything2explainer).
Open in the research findings
F-B5Measure, do not guess: velocity-over-time plot as the first debugging step for motion bugs
LandedShown in a finished filmSmall effort
The technique
A real production write-up: five plausible fixes for a card that stalled and snapped on exit all failed; plotting position and velocity against time showed velocity hitting zero for about 16 percent of the duration, because a bob wave only covered the rise phase, not the element's whole lifetime.
More
Fix: scope the wave to the full lifetime; the curve became continuous.
Why it earned its place
We review by stills, which cannot see a velocity dip. A tiny debug overlay or script that samples a scene's animated values per frame and plots them catches stalls, kinks and false overshoots in seconds.
Evidence one author's account of a real 13-scene, 20-render project; the 30 s versus 1 h comparison is self-reported.
What landed
plot takes JSON/CSV in several shapes, --deriv adds velocity and flags zero-velocity stretches mid-curve. Studio-side exporter helper and prompt 15 step belong to the studio/prompts owners. Same pattern as F-A3. Merged with F-A3. prompts/15 is the prompts integrator's. Covers code-side sampling only; scenes with several animated values need their own sampleCurve call.
Credit rapideye-seo-tools.pages.dev/blog/building-our-launch-video-with-claude/ (Samuel Parks, RapidEye)
Open in the research findings
F-B13A catalogue of render and layout gotchas worth encoding as checks
LandedShown in a finished filmSmall effort
The technique
Concrete, tested-by-failure lessons from the prompts: will-change on anything scaled by the camera makes text blurry; a child with visibility: visible shows through a hidden parent (use inherit); a flood needs about 0.3 to 0.35 s and must overscale past all corners or half the screen changes in one frame; set z-index on
More
every layer so cards do not float above a flood; keep typed text on fixed lines so the camera never follows a wrapping cursor; text that swaps inside a morphing shape needs its own mask and its own enter/exit timing; a 0.05 s fade reads as a pop (fades at least 0.3 s unless intentional); a highlight box behind a word reads as a Windows text selection; if the camera resets to 1.0 at a hand-off the zoom snaps (start the next scene at the zoom the last ended on); looped footage should be re-encoded all-intra (-g 1) and seeked by blob URL because simple static servers cannot range-seek; fading cards out through transparency shows what is behind them, so fade into the haze colour first.
Why it earned its place
Each item is a defect we either already hit (flood overscale, camera reset) or will. Several are new for us: will-change blur, visibility inherit, the highlight-box tell, minimum fade length, all-intra footage.
Evidence failure-derived, from finished films; the two already in learnings corroborate their credibility.
What landed
will-change and visibility items are code gotchas for qa.md. Rubric lines belong to motion-review.
Credit prompt-motion.com/twoclipping-221cab, prompt-motion.com/rossaxbt-3085b7, prompt-motion.com/twoclipping-d89be5
Open in the research findings
F-C4QA loop that compares the render with a reference clip
LandedOnly claimedSmall effort
The technique
Before delivery the pipeline compares its output with a reference clip and fixes the gaps it finds. The author says this reference-clip check was the biggest quality improvement; frames are sampled at a fixed rate and given to Claude together with the timestamped transcript so it can tell what happens when.
Why it earned its place
The post had about 34 to 52 votes and two commenters picked the QA loop out as the part that matters; one adds that an agent which rejects its own bad output stabilised their quality (that comment links to the commenter's own product, so discount it).
Evidence described, not demonstrated; the demo link may be dead per a commenter.
What landed
compare accepts an image, a contact sheet (--cols/--rows) or a video, matched times, reference row over ours, per-pair palette/luma hint; rubric asks for one gap line per pair and forbids copying the reference look. motion-review input change is skills side. Docs mention inspect.mjs compare against the golden scene; motion-review input spec belongs to integrator 1.
Credit u/cowanscorp, www.reddit.com/r/SideProject/comments/1t6wzy5/ .
Open in the research findings
F-C7Plan critic as a gate before the expensive step, and "explain the plan before coding"
LandedOnly claimedSmall effort
The technique
A separate critic agent reviews the editorial plan before anything renders ("most bad renders come from bad plans, not bad execution"); the launch-film author adds a step where Claude explains its plan in words before writing code.
Why it earned its place
The idea of reviewing a plan before spending render time is sound and was reached independently by two posters.
Evidence only claimed; no numbers.
What landed
No reviewer change; the optional fresh critic can reuse agent.md's spawn pattern. Belongs in prompts/12 and 14 and phases.md. Director Round 0 already covers the storyboard. Complements the existing Round 0 review.
Credit u/FerretVirtual8466, www.reddit.com/r/ClaudeAI/comments/1ry69qi/ ; u/TheHol1day, www.reddit.com/r/ClaudeAI/comments/1tbcoft/ .
Open in the research findings
Prompting 6
How to ask so the first draft is already close.
F-B1The tagged brief skeleton with an ask-first <inputs> block and a <start> gate
LandedShown in a finished filmSmall effort
The technique
Every strong @twoclipping, @ultimaxbt and @rossaxbt prompt is split into fixed tags: inputs (what to ask the user for, with defaults if skipped), direction (look plus a Banned list), structure (beat map or timed scenes), build (numbered engineering rules), gotchas (known failure modes), start (what to show before any code).
More
The last tag is the gate: show the beat map and 4 to 8 named stills first, then build.
Why it earned its place
It turns "a film" into a contract the model cannot quietly reinterpret, and it puts the approval stop where it is cheapest (before code). The gotchas tag front-loads defects that otherwise cost a render round each.
Evidence the same skeleton recurs in five independent finished films by two authors; strong pattern evidence, quality of results not independently checked.
What landed
Skills-side brief template and workflow.md paragraph belong to the skills integrator. Prompts 40 and 12 are the prompts integrator's.
Credit prompt-motion.com/twoclipping-221cab and prompt-motion.com/ultimaxbt-bbebf5 (zero @twoclipping, ultima @ultimaxbt)
Open in the research findings
F-C1Reference scene as a working example, not a description
LandedOnly claimedSmall effort
The technique
Instead of describing a scene in words, paste one finished, well-built scene (real code, with its beat mapping, staggered delays, perspective flips and string-slice typewriter) into the prompt and ask for the new scene "in the same structure".
More
The author's own gloss: show Claude a working component and it follows the pattern instead of inventing one.
Why it earned its place
The poster saw text-only prompts produce generic fades, slide-ups and scales, and the reference-scene version produce beat-synced timing, 3D flips and cleaner easing. A separate high-engagement post (about 275 votes, but flagged by commenters as a vendor pitch) reaches the same conclusion for scripts: three hand-written examples beat describing the tone. A reader of the thread had to ask what a "reference scene" was, which suggests the idea is not widely practised.
Evidence only claimed (0 votes, no video, 4 comments), but it is the standard few-shot principle and costs almost nothing to test.
What landed
Golden scenes list in DESIGN_SYSTEM.md is a studio-side edit. DESIGN_SYSTEM.md golden-scenes list and prompt 14 are others'.
Credit u/Sangkwun, www.reddit.com/r/ClaudeAI/comments/1sbbwwu/ ; tone variant: u/Mullikaparatha, www.reddit.com/r/ClaudeAI/comments/1stutgf/ (treat claims with caution).
Open in the research findings
F-C6Measurable acceptance criteria, and a project glossary for vague words
LandedOnly claimedSmall effort
The technique
Two linked rules. First, state outcomes and thresholds ("keep headroom under 20 percent") instead of CSS values, because exact values were misread and broke things.
More
Second, never ask for "punchier" or "make it better" without first defining the word in motion terms for this video (frames, px, curve), because the model knows React but not what "punchy" means.
Why it earned its place
Two independent posters hit the same wall (the edited-footage pipeline and the 50-second launch film), and both list "make it better" as the thing that did not work.
Evidence only claimed, but consistent.
What landed
Reviewer now checks glossary/acceptance criteria by number and flags undefined vague words. Brief template glossary block and revision prompt output owned by others. 13 not edited. Prompts 16 and 40 are the prompts integrator's.
Credit u/FerretVirtual8466, www.reddit.com/r/ClaudeAI/comments/1ry69qi/ ; u/TheHol1day, www.reddit.com/r/ClaudeAI/comments/1tbcoft/ .
Open in the research findings
F-C10"A story with a breaking point" for explainers and data visuals
LandedOnly claimedSmall effort
The technique
Ask for a small physical story where something builds up and then fails visibly ("five glasses fill with risk, the last overflows"), and describe it as steps with a state change at each step: start calm, increase one thing over N steps, then a sudden failure with a clear visual change.
More
Add constraints that stop over-building: a single screen, no scrolling, loopable, minimal interface, and input to visible transformation to output.
Why it earned its place
The thread's author and one commenter, working independently, both found this the one pattern that reliably gave interesting output.
Evidence only claimed (3 votes), no sample shown, but it fits a hook-first approach and our existing "felt human moment as hook" lesson.
What landed
62 not edited; mention could be added there later. Prompts 62 and 63 are the prompts integrator's.
Credit u/SadNose6889 and commenter u/AmberMonsoon_, www.reddit.com/r/ClaudeAI/comments/1t4ffsu/ .
Open in the research findings
F-A17Shot-card library as vocabulary, and a random draw to avoid repeating yourself
Partly landedOnly claimedMedium effort
The technique
Two libraries organise motion moves as named cards with intent, core motion, a parameter table with "what happens if you go wrong", known pitfalls and a reference implementation (124 cards in 10 categories in one; 273 techniques in 14 in the other).
More
One also draws techniques with a script, weighted by format and energy (about one per 3.5 s), so two films do not share the same fade-up, push-in and end card; each technique has a variant that respects the ban list.
Why it earned its place
Named cards give precise prompts ("crash zoom with impact stop on the key card") and the draw counters the model's habit of picking the familiar option.
Evidence card quality is high where I read it (failure thresholds in the parameters); the draw's effect on final taste is only claimed. The 14k stars figure is from the gallery data, not checked.
What landed, and what did not
Maybe later. Skills only point to skills/shot-library, which another agent owns; the draw helper is deferred.
Credit Vincentwei1021/video-shotcraft (github.com/Vincentwei1021/video-shotcraft); Leonxlnx/cinetic scripts/pick.py as described in its README.
Open in the research findings
F-B18Reference video to brief, with a "take techniques, change the design" rule
Partly landedShown in a finished filmSmall effort
The technique
The engraving-style ad prompt attaches a reference video and asks the model to study smoothness, timing, shot durations, fonts and elements, borrow techniques, but change the overall design so it looks done from its own taste; research brand assets first; bans "beige artsy" and eyebrow labels.
More
A YouTube summary adds a similar idea (turn a reference video into a reusable skill).
Why it earned its place
The split "techniques yes, design no" is a clean wording for prompts/20-reference-analysis.md, which already says no copying. The "no eyebrow labels" ban matches our taste.
Evidence the prompt is a short checklist, the film posted; the skill-from-reference claim is second-hand.
What landed, and what did not
A one-line edit to 20 remains possible. Mostly covered by reference analysis; prompt 20 belongs to the prompts integrator.
Credit prompt-motion.com/lexnlin-038035 (Leon Lin @LexnLin); www.youtube.com/watch?v=7jHXoPGnA4c (Nate Herk, unverified)
Open in the research findings
Process 5
Staging the work so it does not drift or regress.
F-A4Parallel build protocol for long pieces (guide for subagents, pure functions of time, file ownership, pilot first)
LandedShown in a finished filmMedium effort
The technique
For a long film the lead writes one animation guide (canvas size, safe zones, helper API, a style section, a self-check command) and a storyboard, then runs one subagent per chapter in parallel.
More
Rules that made it work: every shot is a pure function of t so frames render out of order; each agent edits only its own chapter file and reports shared-file bugs instead of editing them; a pilot group is built first and judged before the rest; one heavy job per agent; a QC agent per chapter appends findings to a table (severity, shot, frame, phenomenon, criterion, suggested fix) and may not edit source. Recorded losses: agents that had read many images died on the next heavy task about 30 percent of the time.
Why it earned its place
It is the only documented way in this set to get 2.5 to 5 minute pieces (a 156 s painted music video, a 5 min narrated explainer with 44 shots) out of agents without style drift. The music-video repo says the whole repo, including the guide, was written by the model.
Evidence shown (finished videos linked) plus the written protocols; I did not play them.
What landed
Prompt is 18, not the 17 the finding suggested, because 17 is reserved. The existing parallel scene-builder rule in remotion-studio already covers file ownership; pilot-first is covered by scene-1 gate.
Credit JohnHeibel/PDoomVideo, ANIMATION_GUIDE.md, STORYBOARD.md (github.com/JohnHeibel/PDoomVideo); Vincentwei1021/anything2explainer, reference/agent-build-rules.md, agent-qc-rules.md, lessons.md.
Open in the research findings
F-B14Tell the user up front what can only be previewed vs rendered (capability honesty clause)
LandedOnly claimedSmall effort
The technique
The fly-over prompt includes an instruction for the case where the agent cannot run code on the user's machine: say immediately that only a live preview is possible and that the MP4 needs Claude Code. The <start> tags likewise require stills before render.
Why it earned its place
It matches our "if you could not look, say so" rule and extends it to render capability. Cheap and prevents a false "done".
Evidence only claimed in a prompt; not observed.
What landed
Skill golden-rule line is on the skills side; 00 not edited. prompts/00 is the prompts integrator's.
Credit prompt-motion.com/twoclipping-d89be5
Open in the research findings
F-C2Regression guard per iteration (commit, diff, before/after stills) plus a decision log
LandedShown in a finished filmSmall effort
The technique
After every change request on a scene, commit it and read the diff, because an "improvement" sometimes removes something that was already right.
More
The same author lists the failure modes that make this necessary: a scene rebuilt from scratch on day two, a few broken builds that had to be rolled back, and not trusting the model to keep context across 50+ scene changes.
Why it earned its place
It is the most honest process write-up in the set ("about 100 prompts, not 1", a creative-direction doc of roughly 30 iterations before any code). Replies from other builders confirm the same pattern (a 3-day product-demo build where removing one scene shifted all later timing).
Evidence shown as experience, not as a measured result. Votes were low (0), so reception is not a signal.
What landed
CLAUDE.md rule 6 wording untouched (not owned). Local commits only, never push. Prompts 15 and 16 are the prompts integrator's.
Credit u/TheHol1day, www.reddit.com/r/ClaudeAI/comments/1tbcoft/ ; u/darrirl comment on www.reddit.com/r/ClaudeAI/comments/1stutgf/ .
Open in the research findings
F-C8Audit the studio by tracing a different kind of video through it
LandedOnly claimedMedium effort
The technique
To test the whole system, describe a completely different type of video than any made so far and trace what the setup would actually do, step by step. The author found half of what they thought was built existed only in documents, and that the system would have produced a cyberpunk-styled yoga tutorial.
Why it earned its place
It tests the failure our own repo risks most: many skills, prompts and learnings that promise things, and one house style that may bleed into every job.
Evidence only claimed (2 votes), but the method is cheap and the result is a concrete list.
What landed
Run it once soon; results into research/findings. Skill docs unchanged.
Credit u/FerretVirtual8466, www.reddit.com/r/ClaudeAI/comments/1ry69qi/ .
Open in the research findings
F-B15Staged asset pipeline for long explainers (foundations, art direction file, storyboard file, asset spec, batch assets, motion primitives, then scenes)
Partly landedOnly claimedSmall effort
The technique
A nine-phase Remotion explainer workflow: write ground rules to a markdown file; define art direction vocabulary ("what does clean mean") in a file; approved timeline becomes a storyboard file; inventory assets before generating; generate assets by category; define reusable motion primitives first; assemble; then generate scene
More
code one scene at a time on larger projects.
Why it earned its place
Matches our flow, with two additions: an asset specification step before any asset exists, and motion primitives defined before scenes (our studio/src/lib plus learnings.md already cover primitives, but per-film "primitives" are not an explicit stage).
Evidence AI summary of a YouTube video I did not watch, channel inferred; low confidence.
What landed, and what did not
Maybe add to 00 later. Low confidence (second-hand summary), kept as a maybe-level item.
Credit www.youtube.com/watch?v=xAUifztpib8 (channel inferred as AndyNocode, via videohighlight.com/v/xAUifztpib8 summary)
Open in the research findings
Considered and rejected, and why
Taste is what you leave out. These were read carefully and turned down, each with the reason.
F-B17Liquid glass by cloning the scene behind each glass element and displacing it (not backdrop-filter)
Rejected
What it was
Each glass control holds its own clone of the scene behind it, filtered with an SVG displacement map derived from a rounded-rect distance field, run through three displacement filters at slightly different scales for chromatic edges, plus a rim light; goo ...
Why it stays out
Liquid glass adds gradients and glow against the flat one-accent taste. Cloned-scene glass adds gradients, glow and per-element cost that clash with flat one-accent taste.
Credit prompt-motion.com/twoclipping-221cab (zero @twoclipping)
Open in the research findings
PP-A1Fixed-output style brief
Rejected
What it was
(from the 15-styles repo, one prompt per film). Sections in order: role (director, designer, engineer and sound designer of one piece); bar (award-shortlist quality, a plain templated result is a fail, named benchmark studios); style; fixed output (size, fps, ...
Why it stays out
Fixed-output style brief with named benchmark studios duplicates 40 plus 10; the latitude clause adds little.
Credit Vincentwei1021, mg-styles-15 prompts/05-cel-boil.md.
Open in the research findings
PP-A3Constrain the medium, free the content
Rejected
What it was
"Only [JavaScript-drawn brush strokes / vanilla Canvas at 160x90 with a 32-colour palette / one HTML file], no video model, no source images; you choose the milestones and the symbolism." State the banned list explicitly (gradients, rotation, blur, ...
Why it stays out
Constrain-the-medium prompts suit showcase experiments, not our default flow.
Credit gallery prompts as summarised in opusvideo/awesome-claude-video guides (Pixel Wizard, Rainbow Road, Life of Opus).
Open in the research findings
PP-A5Reference-lock for a character
Rejected
What it was
Study the sheet, write a character bible, extract the palette by script, lock silhouette features across every style, pass a turnaround and expression lineup before continuing; score every shot on identity, emotion, joke, composition, scale, depth, lighting, ...
Why it stays out
Character reference-lock is for a character piece we do not make.
Credit @pradeepXkapoor via the same guide (Pip case).
Open in the research findings
PP-A7Constraint-for-sync brief for talking-head to B-roll
Rejected
What it was
Keep original audio, subtitles and duration unchanged; shrink the speaker to a corner overlay that does not cover captions; replace the main picture with line-art B-roll per spoken concept, cut at subtitle boundaries; verify every boundary, overlay position, ...
Why it stays out
Talking-head to B-roll brief solves raw-footage editing, which we do not do.
Credit @AxtonLiu via opusvideo guides.
Open in the research findings
Rejected
What it was
"Here are three scripts I wrote. Write the new script so it matches their voice, sentence length and level of hype." Credit: u/Mullikaparatha (1stutgf); use with caution, the thread was suspected of being promotional.
Why it stays out
Few-shot voice for scripts: we write scripts ourselves and the source thread was suspected promotional.
Credit u/Mullikaparatha (1stutgf); use with caution, the thread was suspected of being promotional.
Open in the research findings
Sources set aside
Whole sources, patterns and house styles that were read and left out.
- opusvideo/awesome-claude-video, main README listings Most cases are a link plus one line ("go all out", "modern slick punchy"); only the IMPLEMENTATION_GUIDES cases carry usable method. Mined for patterns 3, 4, 5, 7; the rest is a showcase.
- OfficeChai roundup (web) In my fetch only about half of the ten items state any method; timings are self-reported and unverified; a hype index, not a source.
- MindStudio "Claude Motion" article (web) Describes a product workflow (palette from a screenshot, comment on an element) in the author's words; no prompts or code; I could not verify its claims about model, plan or a gallery. Weak.
- Remotion "Claude Code getting started" (web) Setup steps only (
npx remotion skills add); no technique. We already have it. - video-talkcraft and video-shotcraft workbench, JianYing export, social publishing A CapCut-style editor and China-market export; not our workflow. Only the one-round-then-ask review rule and the contact-sheet token saving were kept.
- video-shotcraft "Ink Press" template mode A fixed product-promo template; templated looks are what we avoid. The recipe cards are useful, the template is not.
- motionmaxxing (Tejashmakwana) Per the gallery data its samples were generated with GPT, not Claude; not opened. Out of scope.
- Remotion trailer (remotion-dev) Human-made, pre-Claude; polish reference only, no method.
- iart-ai/motion-skills A catalogue of 19 packs for an outside product; the README's deliver-and-verify loop is something we already do; I did not open individual packs.
- Not read in depth in this pass Barty-Bart/motion-graphics, digitalsamba/claude-code-video-toolkit, naveen-annam brand film, meetmati-ai MATI-teaser, latent-spaces/brag (already vendored under
third_party/), heygen-com/hyperframes core. I have no evidence from them. The brand-film and toolkit repos may be worth a source read for transition and voice-over code. - cinetic's hard bans taken literally (no serif, no italic, no cream, no orange, no purple). The author's house style; we need the mechanism (lint plus reviewer), not these bans.
- Unverified claims in this report "14k stars" and "124 cards" come from the gallery data and README; "28 professional films", "eight films" and all pacing numbers are the authors' own measurements of films I cannot see; the evaluation tables in cinetic are self-run. Hyperframes viewer links and all videos were not opened.
- Viral one-line showreel prompts (shneural, himanshutwtxs, stephanlivera, ajith_io, lukasersil, leonabboud): quality came from model and effort; the words give no technique. Only use: lukasersil's phrase about a reel being "meticulously art-directed" as a reminder of the failure mode, already in our inspiration notes.
- @donaldjewkes 12-hour music video, @IterIntellectus, @kimmonismus, @achxvi, @joshaeeee, @prathoshap: only second-hand article blurbs, no prompts available; speed and duration claims unverified. The one transferable idea (style snippet of the creator's own footage as reference) is in F-B18.
- Gradient-emphasis word with glow, Apple-Intelligence-style iridescent conic glow, liquid glass as default (rossaxbt, ultimaxbt, twoclipping): violate one accent, no glows, no gradients; see F-B17.
- Downloaded Mixkit SFX instead of synthesised: licensing and consistency trade-off; our synthesised cues from the hits table are fine, only the placement-by-peak rule transfers.
- ElevenLabs voice with emotion tags: needs API keys, cloud; we use local Kokoro. The note that a "warmly" opener can sound whispered and "excited" can sound fake is only relevant if we change TTS.
- Negroni recipe (Ror_Fly): the prompt is two sentences; the idea (ingredients and measures appear as they go in) is a normal explainer pattern we already cover. No new technique.
- Nate Herk "free skills" and the 105 GB sizzle reel: footage-editing workflow, unverified, outside our motion-graphics scope.
- Remotion docs page and the official beginner video: setup only, we already have it.
- "Something happens on every beat" as a universal rule: valid only for music-led loops; for product films it contradicts our restraint rule.
- Claude Motion coverage (MindStudio), OfficeChai roundup: indexes, no technique.
- "Crossfade every cut" and "one easing curve everywhere" as laws (u/Top_Commission_8567, 1tik0qe). The thread's own critics say this yields even, bouncy, tensionless motion; our
learnings.md already says a single entrance curve becomes a template. Kept only as defaults, see F-C5. - Reusable lower thirds and intros for a channel (u/Silver-Range-8108, 1tn9tyy, 97 votes). The top comments (58, 19, 15, 12 votes) call it generic, likely to look dated within months, and note the video itself had problems unrelated to the graphics. The reusable-component idea is already how the studio works; the look is what not to copy. The useful part is the criticism: shared components keep consistency only if the visual language is distinctive in the first place.
- Tutorial-video factory with face swap and AI narration (u/Mullikaparatha, 1stutgf, 266 votes). Top comments call the author a shill for the vendor, and viewers say they dislike AI narration. Cost claims ($2 to 4 a video) are unverified. Only the few-shot tone tip is kept (F-C1).
- Claude Design explainer for under a dollar (u/gnurpreet_, 1tfiv70). The audio-first method (script, TTS, speech-to-text timestamps, then animation) is exactly what
motion-studio already does with Kokoro and Whisper, so it is not new. The thread's critics say the output has a recognisable "Claude Design" look (italic serif everywhere) and one asks about sourcing. Not adopted. - HyperFrames announcement (u/Miguel07Alm, 1snkiti; author works at the vendor). The engine claim that plain HTML is easier for an agent than a React tree is the vendor's view. Comments report mixed results (a Sonnet attempt failed, an Opus attempt did not match a competing JSON renderer). We already have our own HTML engine in
motion-studio and the pinned third-party brag. No change. - R/webdev GSAP replacement of a 3.4 MB video (u/LordVein05, 160 votes). Not found in the archive, so unread; Claude involvement was already unconfirmed in the gallery. It is about web page embedding, not video output. Skipped.
- Plain "first AI video in 10 minutes" posts (1t6cvgv, 1t51k8s). Useful only for the safe-zone and typewriter points above; the "10 minutes" framing is the genre the 100-prompts post argues is mostly fiction.
- Talking-head editing pipeline details (silence detection plus LLM cut choice, ButterCut). Interesting but it solves a problem we do not have (we generate, we do not cut raw footage).
- All TikTok and Instagram items None could be opened; every description is a caption or search snippet, three have no URL, and the two Instagram mindset accounts are format references with no claim of Claude authorship. The reach numbers (about 23.9K and 9.5K likes) say the hook "a skill replaces your editor" travels; they say nothing about quality. Leads only, worth testing only if wanted, each as a one-day experiment: - A brand-token file (
MOTION.md) that CLAUDE.md points to: we already have studio/DESIGN_SYSTEM.md and tokens.ts doing this; no gain expected. - Beat-synced cuts from the music: already covered in learnings.md (scenes as whole beats, hits table) and by motion-studio. - After Effects through an MCP: the studio rule is to say so and use After Effects only when a shot needs compositing; an MCP is untested here and would be a separate evaluation. - A free browser converter from HyperFrames HTML to MP4: irrelevant, since our engines render to MP4 themselves.
Not yet
Good ideas that wait for the right film or enough effort. They are queued, not forgotten.
- F-A18 Build the world from real data (long-form cinematic piece)
Real-data WebGL world is heavy and out of scope for product films. - F-B7 Webpage to 3D fly-over pipeline: capture the live page as separate layers, rebuild as textured quads
Full 3D fly-over conflicts with the studio's rejection of faux-3D UI; at most a later recipe.
Everything here also appears in the research findings viewer, including the ideas not yet decided. The raw notes are in research/findings.