CreatorMotion · Comment Emphasis

Prepare document, commentAuthor and one concise comment. Define highlightRanges as nonoverlapping [start,end] string offsets within that comment, with the end excluded. Check indices after every text change; the implementation sorts ranges for markup but does not infer the phrases or validate editorial meaning.

Set anchor as normalized [x,y] on the document plane and inspect the selected source-line marker beside the comment. It is a coordinate overlay, not text detection. Account for image fit and any blank margins when replacing the source document.

Reuse the bundled document/avatar or replace their named slots through --images MAP.json, with relative paths resolved beside the map. Although an older guide calls the screenshot optional, this effect requires both document and comment-avatar images; there is no active wireframe fallback. Follow the image policy. No presenter or matte is used.

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. Check exact highlighted words, range boundaries, source-line position, comment-author identity and final crop in actual MP4 frames. Keep the comment and source stable after the reveals, preserve at least 1.2 seconds of final reading when editing and avoid adding more ranges than the schedule can accommodate.