CreatorMotion · Source Quote Evidence

Prepare sourceTitle, sourceLabel and an accurately checked excerpt. Write highlights in the intended reading order, each with exact text and tone accent/support. Keep matches nonoverlapping. The code uses the first occurrence of each substring, so repeated phrases require a deliberate choice or matching revision.

Reuse the bundled article-image only for illustration, or replace that exact slot with relevant source material through --images MAP.json. Relative paths resolve beside the map. The image is mandatory even though the high-level inputs omit its key; the excerpt is supplied separately rather than extracted from it.

Keep the excerpt compact enough for the right-hand reading area and choose a few highlights. Missing phrases are not inserted, and their scheduled selectors may have no target. Check image, title, label and transcription together. No presenter or matte is used; spoken synchronization requires separate real audio/cues.

From the extracted package, prepare Node.js 22+, FFmpeg and HyperFrames CLI 0.8.30. Run node scripts/create.mjs --out PROJECT --data CONTENT.json --style white-yellow, substituting another documented palette if wanted. Read the motion specification and image policy before adapting the scene; use semantic --overrides for deliberate style changes.

Inspect the editable project at entry, each motion handoff and final hold, then render with the command printed by the generator. Check the resulting frames for text collisions, correct numbers and readable contrast. Keep at least 1.2 seconds for the final reading when editing, and compare all four palettes with identical content after structural changes. Narration, music and assembly into a longer film remain separate work. Inspect every marked phrase, support-tone contrast, line wrapping and source/excerpt relationship in actual MP4 frames. Preserve at least 1.2 seconds of final reading after edits and ensure added highlights do not overrun the ten-second schedule.