Operating sequence
Write bounded shot-extension prompts that preserve action, camera movement, scene state, and an editable ending while keeping claims evidence-safe.
- 01
Describe the boundary state
Begin with observable facts at the final source frame: subject position and facing, limb phase, prop state, foreground and background layout, light direction, camera movement, focus, and the action already underway. Name the source asset and timecode outside the creative prose so the operator can reproduce the setup. Avoid unsupported phrases such as “perfectly preserve” or “use the Extend button.” A useful boundary clause sounds like a continuation from a known frame, not a fresh scene description. It gives the authorized system enough temporal context while giving the reviewer concrete anchors.
- 02
Write motion as timed beats
Break the added duration into a small sequence: the action completes, the camera settles or continues on a stated vector, the environment responds, and the subject reaches an editable pose. Specify which elements remain invariant and which may change. Include collision rules, gaze direction, prop ownership, screen direction, and pace when they matter. Prefer measurable language such as “continue the leftward dolly at the same apparent speed for the first beat” over mood-only instructions. The prompt should not assert a duration ceiling, model behavior, or control that has not been confirmed in the current interface.
- 03
Ask for an editable terminal frame
Define the desired ending for the next cut: clean silhouette, stable face, settled prop, held composition, or continued motion with known screen direction. Add negative constraints for duplicated limbs, texture crawling, disappearing objects, camera reversals, and new text. Request separate variants when testing distinct endings rather than packing mutually exclusive outcomes into one instruction. Preserve prompt versions alongside outputs and review each join against the same rubric. These prompts are planning language only; actual input syntax, reference support, extension access, and result quality must be verified in the authorized tool.