Communitygithub.com

voynann-motion

Shows an agent how to plan, build, or cut "voynann motion" so the concrete output is a Remotion scene the agent can render. The procedure moves through VOYNANN Motion — Master Director, Begin with a guided conversation, Style selection. Use it when a new assignment calls for this craft.

What is voynann-motion?

voynann-motion is a Claude Code agent skill that shows an agent how to plan, build, or cut "voynann motion" so the concrete output is a Remotion scene the agent can render. The procedure moves through VOYNANN Motion — Master Director, Begin with a guided conversation, Style selection. Use it when a new assignment calls for this craft.

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/vianaforwork/video-animarion/tree/HEAD/.claude/skills/voynann-motion

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

VOYNANN Motion — Master Director

Version: 1.12.0. Nineteen signature styles (01 PIXELSTORY, 02 VOXELVERSE, 03 PRECISION, 04 PAPERWORLD, 05 INNERWORKS, 06 WORLDFORGE, 07 TIMEFORGE, 08 BUILDFORGE, 09 CINÉSTORY 3D, 10 CHARACTER FLOW, 11 PANELVERSE, 12 STORYBOOK, 13 CHRONICLE, 14 BEDAH, 15 CERDIK, 16 NEGERI, 17 TIPIKAL, 18 NEKAT, 19 BONGKAR). The skill ships a production kit: a Remotion + React Three Fiber project starter with a shared core library and render/QA scripts (starter/), plus reusable style engines, each with a technical example and a KIT.md, for PIXELSTORY, VOXELVERSE, PAPERWORLD, WORLDFORGE, TIMEFORGE, BUILDFORGE, CHARACTER FLOW and PANELVERSE (kits/<style>/; CHARACTER FLOW adds an automatic story director, PANELVERSE a comic engine directed per script), and nine styles as complete projects of their own — CINÉSTORY 3D (kits/cinestory/project/: automatic director, world and object builder), STORYBOOK (kits/storybook/project/: picture-book director, paper engine, cast and page library) CHRONICLE (kits/chronicle/project/: history-script director, silhouette cast, sets, 3D relief maps) and BEDAH (kits/bedah/project/: story director, realistic building site with the ground cut open, worker, parts for roofs and foundations, a pattern for adding parts) and CERDIK (kits/cerdik/project/: story director with an automatic line-of-sight camera, round-head cast library, five worlds, props, effects, crowds, a pattern for adding props and worlds), NEGERI (kits/negeri/project/: daily-series director with a country remembered between episodes, chibi host + citizens, 19 buildings rising in stages and a parts language for new ones, counter and comment cards), TIPIKAL (kits/tipikal/project/: "tipe-tipe" sketch director, toon cast with real hands, six Indonesian sets, driving vehicles, type cards and reaction pops) and NEKAT (kits/nekat/project/: escalating-challenge director, toy-clay duo, multiplying animal crowds, 13 tools, counter and PART series), BONGKAR (kits/bongkar/project/: teardown director that works out from an object.json how the object comes apart, mesh-checked exploded view, push-in to the core, reassembly loop, narration in disassembly order); PRECISION and INNERWORKS are built on the core (whose studio and post chain come from PRECISION) following their references. Recommended hardware: a Mac with Apple Silicon or a PC with a GPU. On every new machine run npm run check-env and npm run smoke before promising renders; without a usable GPU the render scripts switch to software rendering automatically (.gl-mode = swangle, very slow), so tell the buyer once that renders on this computer will take much longer. Treat references as art direction plus proven technique, never as a guarantee of a specific result. (Internal status — do not recite to buyers; see "Begin with a guided conversation".) Buyer-facing guides live next to this file: START_HERE.md, INSTALLATION_GUIDE.md, USER_GUIDE.md, EXAMPLE_PROMPTS.md, TROUBLESHOOTING.md, LICENSE_AND_REQUIREMENTS.md — read TROUBLESHOOTING.md when the buyer reports a problem.

Begin with a guided conversation

Make the default experience feel like a helpful creative assistant speaking to a buyer, never a developer-facing QA report. Read references/guided-brief.md when a user starts with an incomplete request (for example, "Aku mau bikin animasi") or asks for help choosing a style.

  • Use friendly Indonesian by default, even when the user's short prompt is in English. Switch only when the user explicitly asks. No jargon, prompt templates or command-line details in conversational replies.
  • Ask one useful question at a time and skip questions already answered. When a style obviously fits, select it quietly and move to the VO question. Ask about style only when genuinely different directions fit or the user wants options. Use defaults for duration, format and mood.
  • Keep internal development notes internal. Never volunteer registry entries, demo approvals, release gates, test results, version numbers or file names in normal onboarding. Answer honestly when asked about reliability or a missing capability; never guarantee results. Explain concrete blockers before committing time/resources.
  • Resolve the voice-over checkpoint before storyboard, look development or animation: supplied VO, or music/SFX-only. If VO is chosen, get and measure the real file before locking shot lengths (guided brief › VO flow).
  • If the user asks to see all styles, describe all nineteen briefly (all have a demo; none is promised as one-click).
  • CINÉSTORY 3D exception: a voice-over plus a request for a CINÉSTORY / cinematic story film (e.g. "Buatkan video CINÉSTORY 3D dari VO ini: …") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/cinestory.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, build the location, direct, check, render the final and deliver, then offer revisions. Without a VO, offer a narration + offline TTS and make it only after approval.
  • CHARACTER FLOW exception: a voice-over plus a request for a character video (e.g. "Buatkan video CHARACTER FLOW dari VO ini: …") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/characterflow.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, direct, check, render the final and deliver, then offer revisions. Without a VO, offer a narration + offline TTS and make it only after approval.
  • PANELVERSE exception: a voice-over plus a request for a comic video (e.g. "Buatkan video PANELVERSE dari VO ini: …", "video komik pop dari VO ini") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/panelverse.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, direct a film designed for this script (beat sheet, cast, sets, devices and at least one element of its own), check, render the final and deliver, then offer revisions. Without a VO, offer a narration + offline TTS and make it only after approval.
  • STORYBOOK exception: a picture-book script and/or narration plus a request for a storybook (e.g. "Buatkan video STORYBOOK dari naskah ini: …", "jadikan buku cerita anak / dongeng bergambar") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/storybook.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, write the naskah (pages, cast, what each page shows), check stills, render the final and deliver, then offer revisions. Without a narration, offer a voice text or offline TTS and make it only after approval.
  • CHRONICLE exception: a history script and/or voice-over plus a request for a history documentary (e.g. "Buatkan video CHRONICLE dari VO ini: …", "video sejarah siluet tentang …") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/chronicle.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, write the naskah (scenes, maps, cast, dates, sources), check stills, render the final and deliver, then offer revisions. With only a topic, research it, show the naskah with its sources first, and make a narration only after approval. Never invent facts.
  • BEDAH exception: a script and/or voice-over plus a request for a "how it's built" explainer (e.g. "Buatkan video BEDAH dari VO ini: …", "video bedah tentang pondasi rumah", a script in the "Kalau kamu… Tapi… Jadi…" pattern) is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/bedah.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, write the parts the topic needs and the story, check stills, render the final, read the flicker map and deliver, then offer revisions. With only a topic, show the script first and build without a narrator until the buyer brings a voice.
  • CERDIK exception: a script and/or voice-over plus a request for a clever-trick story short (e.g. "Buatkan video CERDIK dari VO ini: …", "video tokoh kepala bulat tentang …", "cerita 'diketawain dulu, terbukti benar' tentang …") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/cerdik.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, pick the world (or write one), write the story, check stills, run the preview QA, render the final and deliver, then offer revisions. With only a topic, show the script first and build without a narrator until the buyer brings a voice. Buyers can choose, change and save the characters (kartu tokoh, tokoh-*.json) — cerdik.md › Tokoh.
  • NEGERI exception: today's inputs (day, follower count, top comments, what wins) and/or a voice-over plus a request for the participatory country series (e.g. "Buatkan video NEGERI hari 4: follower 31.200, komen teratas …", "lanjut negara netizen hari berikutnya", "video bikin negara dari nol dari VO ini") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/negeri.md: no recap, no confirmation, no setup-permission or preview-approval stop; continue the series' world, map the winning comment to a building (or design one), write the episode, check stills, run the preview QA, render the final (it writes the day into the series) and deliver with tomorrow's hook. With only inputs, show the script and the cast card first and build after the OK. The leader is saved for the series (kartu tokoh, tokoh-*.json) — negeri.md › Tokoh.
  • TIPIKAL exception: a request for a "tipe-tipe …" comedy short (e.g. "Buatkan video TIPIKAL tentang tipe-tipe pengendara motor", "video tipe-tipe orang di kondangan", with or without the buyer's own types or VO) is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/tipikal.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, write the types (topic only), pick the set (or write one), cast, write the story, check stills, run the preview QA, render the final and deliver, then offer revisions. Wordless by default — never add a synthetic narrator. Buyers can choose, change and save the characters (kartu tokoh, tokoh-*.json) — tipikal.md › Tokoh.
  • NEKAT exception: a premise and/or voice-over plus a request for an escalating-challenge short (e.g. "Buatkan video NEKAT: Bisa gak Pak Darto ngusir Si Oren? Tiap diusir kucingnya nambah.", "video tantangan bersambung …", "bikin part 2-nya") is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/nekat.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, write the title question, levels and ending, cast the duo, check stills, run the preview QA, render the final and deliver. A premise alone is enough: build straight away (no script stop). Wordless by default (captions, music, SFX); a buyer VO is used as given. The duo can be chosen, changed and saved (kartu tokoh, tokoh-*.json); a later part continues the counter — nekat.md › Tokoh.
  • BONGKAR exception: a request to take an object apart (e.g. "Buatkan video BONGKAR rice cooker", "video bongkar kipas angin, isinya ada berapa part?", "exploded view setrika"), with or without a VO, is a complete brief and the go-ahead. Follow the zero-prompt workflow in references/bongkar.md: no recap, no confirmation, no setup-permission or preview-approval stop; set up, model the object's parts (four-side look check), plan the disassembly until the tembus check passes, check stills, run the preview QA, render the final and deliver. Wordless by default; offer the generated narration at delivery, and lock a buyer's VO to the part names.
  • Before substantial work, recap the brief in 3–5 short lines and ask one confirmation. Do not install software or change files because of initial interest alone.
  • A complete brief goes straight to the production contract; continue through preview and revisions in chat.

Style selection

Read references/style-registry.md first, then only the selected style reference plus references/quality-gates.md, to avoid blending aesthetics.

StyleReferenceKit in this skill
PIXELSTORYpixelstory.mdkits/pixelstory (+ fonts in public/)
VOXELVERSEvoxelverse.mdkits/voxelverse
PRECISIONprecision.mdcore (studio, post, slab, materials were extracted from PRECISION)
PAPERWORLDpaperworld.mdkits/paperworld
INNERWORKSinnerworks.mdcore only
WORLDFORGEworldforge.mdkits/worldforge
TIMEFORGEtimeforge.mdkits/timeforge
BUILDFORGEbuildforge.mdkits/buildforge (+ scripts/buildforge-check.ts)
CINÉSTORY 3D (09)cinestory.md (+ cinestory/)kits/cinestory (a project of its own: --kit=cinestory)
CHARACTER FLOW (10)characterflow.md (+ characterflow/)kits/characterflow (+ automatic director, scripts/make.mjs)
PANELVERSE (11)panelverse.md (+ panelverse/)kits/panelverse (+ story kit, lint, scripts/pv-make.mjs)
STORYBOOK (12)storybook.md (+ storybook/)kits/storybook (a project of its own: --kit=storybook, scripts/book-make.mjs)
CHRONICLE (13)chronicle.md (+ chronicle/)kits/chronicle (a project of its own: --kit=chronicle, scripts/make.mjs)
BEDAH (14)bedah.mdkits/bedah (a project of its own: --kit=bedah, scripts/make.mjs)
CERDIK (15)cerdik.mdkits/cerdik (a project of its own: --kit=cerdik, scripts/make.mjs)
NEGERI (16)negeri.mdkits/negeri (a project of its own: --kit=negeri, scripts/make.mjs, series/<name>/world.json)
TIPIKAL (17)tipikal.mdkits/tipikal (a project of its own: --kit=tipikal, scripts/make.mjs)
NEKAT (18)nekat.mdkits/nekat (a project of its own: --kit=nekat, scripts/make.mjs, series/<name>/state.json)
BONGKAR (19)bongkar.mdkits/bongkar (a project of its own: --kit=bongkar, scripts/make.ts, stories/<id>/object.json)

Infer the style from the idea and describe the look in one sentence; do not make the buyer learn style names. PIXELSTORY = 2.5D pixel-art characters; VOXELVERSE = voxel miniature worlds; PRECISION = one product's premium CGI/exploded view; PAPERWORLD = handcrafted paper diorama stories; INNERWORKS = opening a machine to show how it works; WORLDFORGE = exploring a whole 3D environment/world; TIMEFORGE = one object physically evolving through dated eras; BUILDFORGE = a structure assembled piece by piece; CINÉSTORY 3D = a voice-over told as a cinematic 3D short film: people acting in a place built for the story (an office at night, a shop, a street, a coast), film-like cameras, mood light, captions; CHARACTER FLOW = expressive 3D characters acting out a relatable voice-over (everyday life, psychology, school, work, friends, family, habits, night thoughts, "what if" situations) in a campus walkway, a bedroom, a classroom, an office, a café or a living room — several of them in one video — with 1–2 people per place; PANELVERSE = a voice-over told as a living retro pop-art comic: thick ink, halftone dots, flat pop colours, panels that slam, split, expand into 3D scenes and shatter, comic lettering and sound effects — for relatable stories, twists and jokes told in beats ("pernah ga…", overthinking, ekspektasi vs realita, "padahal…"); STORYBOOK = a children's story told as a real paper picture book on a table under a reading lamp: cover, page turns, painted cut-paper pictures with paper puppets and animals, the text printed under each picture — for dongeng, bedtime stories, fables, moral tales; CHRONICLE = a history told as a 3D silhouette documentary: warm 3D places lit from behind, people as black silhouettes with coloured contours for the named roles, a 3D relief map with routes and pins, big dates, counters and sources — for historical figures, kingdoms, wars, exiles, disasters, origins of places; BEDAH = an everyday built thing explained as a chain of problems and fixes ("Kalau kamu… Tapi… Jadi kamu…"): a real-looking sunny building site in a village, the ground cut open so the soil and foundations show in section, a worker in a caping doing the job, each new part arriving on its sentence and named with a pinned label, white marker arrows — for roofs, foundations, walls, floors, wells, roads; CERDIK = a clever trick or a hidden reason told as a quick little story in the 'laughed at, then proven right' pattern: big round white heads with drawn faces and thin stick limbs, in saturated detailed 3D worlds (a stilt-house village, a market, a fishing beach, a home, a palace), one fast narrator, a cut every ~2 s, one-word captions, a glow on the thing that matters, cutaways inside objects — for science and engineering tricks, folk wisdom, inventions, history anecdotes with a twist; NEGERI = "bikin negara dari nol": a daily numbered series where followers become citizens and the top comment becomes the next building — a chibi leader (president, queen, village head…) in a clean low-poly game world, a population counter rolling while tents and houses spread, comment cards read out, the requested building rising stage by stage, commenters' names on new houses, a small comic drama with the citizens, "Besok bangun apa? Komen!"; the country is remembered between episodes; TIPIKAL = "tipe-tipe orang …" relatable comedy sketches: a topic everyone knows (riding a motorbike, an exam, a wedding, the office, breaking the fast) split into 3–5 numbered types, each a 3–6 s vignette with a visual punchline — chunky toon people with drawn faces in detailed Indonesian 3D sets (street + traffic light, kampung alley + warung, classroom, office, wedding tent, living room), scooters, bikes and cars, reaction faces, "?" / "!" pops, comic sound words, a persistent header and themed type cards, ending on "Kamu tipe yang mana?" — wordless by default; NEKAT = a recurring duo vs. an animal that multiplies every try: one absurd challenge that escalates level by level ("Bisa gak Pak Darto ngusir Si Oren? Tiap diusir… kucingnya nambah") with an on-screen counter (×N), sillier and sillier tools, a twist ending and PART cliffhangers, in soft toy-clay 3D (alley, garden + coop, school yard), wordless by default, the series' counter carried to the next part; BONGKAR = an everyday object takes itself apart into labelled parts ("bongkar rice cooker, isinya ada berapa part?"): a clean studio, screws spinning out, parts lifting away outer to inner into an exploded view with a rolling "n / N part" counter and label chips, a push-in on the part that makes it work, then everything flies back together and loops — for appliances, tools, gadgets, toys. Prefer BONGKAR over INNERWORKS when the point is what the object is made of (parts, count, exploded view) rather than how it works while running, and over PRECISION when it is an everyday object taken apart rather than a premium product ad. Prefer BEDAH over BUILDFORGE when the script explains why each step exists (BUILDFORGE assembles a whole building in sequence), and over INNERWORKS when the subject is built on a site rather than a machine opened up. Prefer CERDIK over CHARACTER FLOW when the story is a trick with a twist (mocked, then proven right) rather than relatable feelings, and over BEDAH when it is told as a story with characters rather than as building steps. Prefer NEGERI over WORLDFORGE / BUILDFORGE when the audience decides what gets built and the video is one day of a numbered series (counter, comment cards, host). Prefer TIPIKAL over CHARACTER FLOW when the idea is a list of recognisable types ("tipe-tipe …", "jenis-jenis …", "kamu tipe yang mana") rather than one voice-over about a feeling, and over PANELVERSE when the joke is a set of types shown as little 3D scenes. Prefer NEKAT over CERDIK when the joke is a rule that gets worse every try ("tiap diusir malah nambah") with a counter, levels or PART n rather than a clever trick proven right. Prefer STORYBOOK over PAPERWORLD when the buyer wants a book read aloud (pages, printed text) rather than a standing pop-up world, and CHRONICLE over CINÉSTORY when the story is real history moving between dated events and places. Prefer CINÉSTORY when the VO tells a story or an event in a specific place (mystery, horror night, a "what if" through someone's day) and CHARACTER FLOW for relatable character acting in those everyday places (it needs no world to be built). Prefer TIMEFORGE over PRECISION when changes between historical designs are the story; WORLDFORGE for inhabited environments; BUILDFORGE when construction itself is the subject; INNERWORKS for how a finished machine works inside.

Outside the product's scope: flat 2D explainers, infographics/data charts, kinetic-typography-only videos, slideshow edits of photos, live-action editing, talking heads. Say kindly that VOYNANN Motion makes cinematic 3D/stylized scenes; offer the closest style if one genuinely fits (e.g. an explainer about a machine → INNERWORKS), otherwise say it is not the right tool rather than forcing a style.

Preview rounds (the one expectation you do set). CHARACTER FLOW, CINÉSTORY, PANELVERSE, STORYBOOK, CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL, NEKAT and BONGKAR are the exception: their directors check stills themselves and deliver the final directly; revisions come after. For the other styles: every new idea is an original film, so say once, in one plain Indonesian sentence, that the first preview usually gets one or two rounds of refinement before the final (buyers see the same in START_HERE.md); for PRECISION and INNERWORKS, which have no dedicated engine, plan for the second round from the start. Do not repeat it or turn it into a technical report.

Never promise features a reference lists as unsupported (e.g. WORLDFORGE has no water/forest/animal/crowd systems; BUILDFORGE rules fit simple orthogonal buildings; construction animation is not engineering instruction; future designs are speculative).

Setup and the production kit

Read references/production-kit.md before writing code and references/setup.md before the first render on a machine. In short:

  1. Inspect the current folder. If there is no suitable VOYNANN project, ask permission (CHARACTER FLOW, CINÉSTORY, PANELVERSE, STORYBOOK, CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL, NEKAT, BONGKAR: no question, see their references), then node SKILL_DIR/new-project.mjs <folder> --kit=<style> — it copies SKILL_DIR/starter/ plus the style's kit (kits/<style>/src/ into src/, scripts/ into scripts/, public/ into public/) with Node only, so no shell copy permissions are needed. The starter's and kits' source ships packed (PACKED_SOURCE*.txt, to stay under the app's 200-file skill upload limit): never copy those folders by hand. PRECISION and INNERWORKS have no kit folder: --kit=precision / --kit=innerworks set up the starter alone (their films are built on src/core). CINÉSTORY, STORYBOOK, CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL, NEKAT and BONGKAR are different: --kit=cinestory|storybook|chronicle|bedah|cerdik|negeri|tipikal|nekat|bongkar copies kits/<style>/project/ instead of the starter (marked with voynann-kit.json), and such a project never takes another style's kit (use a new folder per style). Read that kit's KIT.md; on the first project on a machine, register the kit's example as a composition and check its stills once before building the buyer's film. SKILL_DIR is the folder containing this file.
  2. npm ci, npm run check-env, then npm run smoke and look at out/smoke/_sheet.jpg. Do not plan or promise renders until the smoke stills are correct. First setup downloads ≈370 MB of packages and ≈170 MB headless Chrome (≈1.2 GB on disk per project after the first render, plus a bundler cache in node_modules/.cache that can grow past 1 GB and is safe to delete) — tell the buyer once, in plain words, and ask.
  3. Build the film on src/core (camera tracks, rig, post chain, studio or outdoor stage, materials, slab/lathe geometry, overlay + projector, VO). Reuse kit engines; never copy a demo's story, cast, product or geometry.
  4. Use npm run vo -- <audio> for real VO timing; write cut keys in VO seconds. (CHARACTER FLOW and CINÉSTORY: node scripts/transcribe.mjs <audio> --id=<id> + scripts/make.mjs; PANELVERSE: pv-align.mjs … --out=src/pv-stories/<id>/words.json + scripts/pv-make.mjs; STORYBOOK: scripts/book-make.mjs <id> and CHRONICLE: scripts/make.mjs <id> read stories/<id>/naskah.txt + vo.*; BEDAH, CERDIK, NEGERI, TIPIKAL and NEKAT: scripts/make.mjs <id> reads stories/<id>/story.json + vo.*; BONGKAR: node scripts/make.ts <id> reads stories/<id>/object.json + naskah.txt + vo.* — see their KIT.md.)
  5. Previews: npx remotion render <Preview> …; finals: npm run render:final -- --comp=<Final> --out=… --vo=… --offset=… --cuts=<planned cut seconds> (segmented, restartable, −14 LUFS master; it runs the QA gate first — see below).

Production contract

CHARACTER FLOW, CINÉSTORY, PANELVERSE, STORYBOOK, CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL, NEKAT and BONGKAR follow their own zero-prompt contracts in references/characterflow.md, references/cinestory.md, references/panelverse.md, references/storybook.md, references/chronicle.md, references/bedah.md, references/cerdik.md, references/negeri.md, references/tipikal.md, references/nekat.md and references/bongkar.md (story data, direction, stills QA, final, automated + visual QA); the steps below apply to the other styles.

  1. Inspect the project and inputs; preserve unrelated files. Scaffold from the starter only with permission.
  2. Brief: message, audience, duration, style, one visual idea. Defaults: 9:16; preview 540×960 @ 30 FPS; final 1080×1920 @ 60 FPS; bright, readable art direction. Landscape only on request (see Format below).
  3. VO decision (required): (a) VO chosen and a readable file received, or (b) music/SFX-only explicitly chosen. Never add a synthetic narrator by default.
  4. Audio-led timing: use the measured duration, pauses and phrases; choose the VO offset per recording (never reuse a demo's offset). If the desired length conflicts with the audio, explain and ask; never speed up, pitch-shift or trim narration silently.
  5. Direct: concise treatment, object/character sheet, palette, shot list, transitions, strongest final image, cause and effect.
  6. Look development: after confirmation, a 3–5 s render of the highest-risk element. Inspect stills against references/quality-bar/<style>.jpg; iterate until the same quality class.
  7. Preview: the whole film when it is 20 s or shorter, otherwise a representative 15–20 s section (or the full VO length when requested), at 540×960 @ 30. Inspect stills at every important beat and transition midpoint; run the QA gate on the preview composition (tag the solids first) and fix every FAIL before showing it. Ask for approval before the final.
  8. Final: 1080×1920 @ 60 MP4 (landscape on request: 1920×1080 @ 60), VO muxed at its offset, audio −14 LUFS integrated, true peak below −1 dBFS — through render:final with --cuts, so the QA gate runs before and after. Verify with ffprobe, silencedetect sync against the source, and frames extracted from the MP4.
  9. Determinism: everything from useCurrentFrame()/useVideoConfig(); ThreeCanvas from @remotion/three; no independent useFrame animation, wall clocks, unseeded randomness or CSS autoplay.
  10. Report honestly what was verified, what was not, and how to reproduce; never claim a file exists without checking.

QA gate: no tembus, no kedip, no loncat (every style)

Buyers look frame by frame: a hand through a cup, a limb that snaps for one frame, a part that pops, a z-fight that shimmers or a camera that wobbles reads as cheap even in an otherwise good film. Every style runs the same gate (references/quality-gates.md › QA gate, starter/scripts/qa-gate.mjs):

  • Tag what acts with <Solid> (src/core/qa/scene-qa.tsx): every character (kind="body"), everything a hand holds or that moves past a body ("prop", touch={[holderId]}), and furniture people sit on, lean on or walk past ("set", touch={["*"]}). CHARACTER FLOW, CINÉSTORY, CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL and NEKAT tag their people, props and furniture already, BONGKAR every part (STORYBOOK's paper puppets and PANELVERSE's panels move in designed steps: there the clean-frame scan is the check); in the other styles tag them yourself. The probe (<QaProbe />) is mounted by Stage3D; a kit with its own ThreeCanvas mounts it last inside.
  • Before showing a preview and before every final: node scripts/qa-scene.mjs --comp=<Preview> --cuts=<planned cuts> (the auto-directors and render:final run it themselves). It renders the preview without images and checks TEMBUS (tagged solids inside each other where the camera sees it), LONCAT (a part / the camera snapping or flicking for one frame), KEDIP (a solid vanishing for one or two frames), then scans small frames of the 3D alone (captions left out) for blinks, pops and flicker anywhere in the picture.
  • FAIL = fix the cause (grip at the rim, arc around, sit on the seat edge, separate coplanar faces, ease the branch switch) and run again; never show or deliver it. CHECK = open each qa-video_*.jpg strip; an instant change that is designed (a cartoon blink, typewriter letters, a counter, a fast gesture) gets "ok: <why>" in qa-video.review.json, anything else is fixed. Never write "ok" for something you did not look at.
  • After the final render the delivered file gets a hard scan (qa-video.mjs --hard-only): black / white runs, full-frame blinks, cuts that are not in the plan.
  • Tell the buyer only the outcome in plain words ("sudah dicek: tidak ada yang tembus atau berkedip"), never the tool names.

Format: portrait by default, landscape on request

Every style delivers portrait 9:16 (1080×1920 @ 60, preview 540×960 @ 30) unless the buyer asks for another format in their own words. Do not ask which format they want, do not suggest landscape, and never infer it from the topic, the length or the platform you imagine.

  • Landscape 16:9 (1920×1080 @ 60, preview 960×540 @ 30) is made in all nineteen styles when the buyer asks: "landscape", "16:9", "horizontal", "mendatar", "layar lebar", "versi YouTube" / "untuk YouTube" (a "YouTube Short" is still portrait). The request can come with the first message or later ("buatkan juga versi landscape-nya").
  • Landscape is directed for the wide frame: cameras, staging and text are laid out again. Never crop, pad, letterbox, stretch or re-encode a portrait render into 16:9 (or the reverse).
  • How: CINÉSTORY "format": "landscape" in story.json; CHARACTER FLOW scripts/make.mjs … --wide; PANELVERSE scripts/pv-make.mjs … --wide; STORYBOOK scripts/book-make.mjs … --wide; CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL and NEKAT scripts/make.mjs … --wide; BONGKAR scripts/make.ts … --wide — each explained in the style's reference. The other eight styles: a second pair of compositions from PRESETS_WIDE, per references/production-kit.md › Landscape and the note at the end of the style's reference.
  • Both formats ("vertikal dan landscape"): finish portrait first (stills, preview / approval where the style has one, final), then make the landscape film from the same story and voice-over; review its stills separately — a wide frame shows set edges, empty sides and text positions the portrait never showed. Deliver two files (…_1080x1920_60fps.mp4, …_1920x1080_60fps.mp4).
  • Square 1:1 and 4:5 are not offered: say so kindly and offer portrait or landscape.

How users invoke the skill

/voynann-motion followed by an ordinary request, for example:

/voynann-motion Aku mau bikin video evolusi televisi dari TV tabung sampai TV tipis sekarang.

/voynann-motion Aku mau video yang memperlihatkan cara kerja kipas angin, bagian dalamnya kelihatan. Aku punya VO MP3.

/voynann-motion Buat dunia 3D kota pertama di bulan yang bisa dijelajahi kamera. VO-nya menyusul.

/voynann-motion Bikin iklan 3D premium untuk botol minum fiktif, close-up material dan bagian-bagiannya terpisah lalu menyatu lagi.

/voynann-motion Cerita pendek kertas tentang tukang kebun kecil yang mengembalikan warna ke kota kertas. Musik saja.

/voynann-motion Buatkan video CINÉSTORY 3D dari VO ini: /Users/kamu/Downloads/vo.mp3 (naskahnya: /Users/kamu/Downloads/naskah.txt)

/voynann-motion Buatkan video CHARACTER FLOW dari VO ini: /Users/kamu/Downloads/vo.mp3

/voynann-motion Buatkan video PANELVERSE dari VO ini: /Users/kamu/Downloads/vo.mp3

/voynann-motion Buatkan video STORYBOOK dari naskah ini: /Users/kamu/Downloads/naskah-buku.txt (VO: /Users/kamu/Downloads/vo.mp3)

/voynann-motion Buatkan video CHRONICLE tentang kenapa Pangeran Diponegoro dimakamkan di Makassar.

/voynann-motion Buatkan video BEDAH dari VO ini: /Users/kamu/Downloads/vo.mp3 (naskahnya: /Users/kamu/Downloads/naskah.txt)

/voynann-motion Buatkan video CERDIK tentang kenapa kendi tanah liat bikin air tetap dingin.

/voynann-motion Buatkan video NEGERI hari 1: follower 12.480, komen teratas @budi.santuy "bikin pos ronda dong pak pres".

/voynann-motion Buatkan video TIPIKAL tentang tipe-tipe pengendara motor.

/voynann-motion Buatkan video NEKAT: Bisa gak Pak Darto ngusir Si Oren? Tiap diusir kucingnya nambah.

/voynann-motion Buatkan video BONGKAR rice cooker, isinya ada berapa part?

/voynann-motion Buatkan video CHRONICLE tentang letusan Tambora 1815, versi landscape 16:9 untuk YouTube.

Never require the buyer to understand internal files or paste a template prompt. Experience: install once, describe an idea, answer a few simple questions, confirm, approve setup, preview, refine, render.

Brand kit

If the buyer attaches or keeps a voynann-brand.json (format: BRAND_KIT.md), copy it into the project as src/brand.json (and any logo into public/brand/) and use src/core/type/brand.ts: brandName() for title/kicker/end-card text, the handle and CTA in the closing overlay, and brandAccent(background, styleColour) for overlay labels and highlights (it falls back to the style colour when contrast is too low). Keep the 3D world in the style's art direction unless the buyer asks for brand colours in the scene; never extrude or animate a logo in 3D unless asked. Without a kit, stay brand-neutral. If the buyer asks you to create a kit, write voynann-brand.json from their words (hex colours) in the working folder.

Output expectations

  • Original Remotion project source (organised, configurable text/duration/palette where sensible).
  • Preview and final MP4 when rendering succeeds, with their locations.
  • A short note of what was verified, what remains unverified and how to reproduce.
  • No downloads from untrusted URLs; ask permission for installs and large downloads; original or licensed assets only (fonts, music, VO, models).

Never edit the installed skill

Do not modify, add or delete files inside SKILL_DIR during a buyer session: the installed skill may be read-only or synced from the buyer's Claude account, and it must stay identical for every project. Keep project-specific learnings (what worked, failure modes, chosen VO offsets) in the buyer's project folder, for example NOTES.md, never in the style references or the registry.

Where videos can be made

Rendering needs a local Claude Code session (the Code tab of the Claude desktop app, or the claude terminal) on the buyer's own computer with Node.js (≥ 22.18 for CINÉSTORY 3D, STORYBOOK, CHRONICLE, BEDAH, CERDIK, NEGERI, TIPIKAL, NEKAT and BONGKAR, ≥ 22.13 for the other styles; each project's npm run check-env checks its own minimum). A plain claude.ai chat cannot install packages or render these videos; if the buyer is there, explain kindly and point to INSTALLATION_GUIDE.md.

Related Skills