Skip to content

konradre/video-production-skills / skills/video-refs-continuity

video-refs-continuity

Verified

Continuity through consistency for generated video: builds the DERIVED reference set and start image every shot needs, keeps the continuity ledger between shots, and runs the refs gate in code before any generation call. Use when a shot must match the shot before it (room, cast, seats, wardrobe, held props, door swing, a named state), when a character, product or room reference is built or cut from a keeper, when a plate or start image is generated, or when seeds keep drifting between shots. Triggers — "continuity", "refs gate", "reference set", "start image", "continuity ledger", "backfill from accepted", "the door is on the wrong wall", "not the same guy", "the same shape in all videos". Not for the cost line, the GO and the submit itself — use video-gen-cost-gate. Not for the prompt's wording — use video-prompt-dialects. Not for upscale, film look, grain or the delivery encode — use video-finish.

FileKindSize
SKILL.mdskill md31.6 KB
references/ASSET-HYGIENE.mdmarkdown6.1 KB
references/CONTINUITY-AXES.mdmarkdown6.3 KB
references/REFERENCE-CONTRACT.mdmarkdown19.0 KB
references/REPAIR-LADDER.mdmarkdown6.0 KB
references/SCENE-PROXY.mdmarkdown24.5 KB
references/ZOOM-OUT-CHAIN.mdmarkdown4.1 KB
references/refs-required.example.jsonconfig3.1 KB
scripts/air_pieces.pyexecutablescript3.9 KB
scripts/cast_stress.pyexecutablescript17.8 KB
scripts/comfy_preflight.pyscript22.3 KB
scripts/comfy_ready.pyexecutablescript2.7 KB
scripts/comfy_up.shexecutablescript2.6 KB
scripts/knit_letters.pyexecutablescript7.3 KB
scripts/plate_pieces.pyexecutablescript4.9 KB
scripts/ref_dag.pyexecutablescript5.2 KB
scripts/refs_gate.pyexecutablescript41.1 KB
scripts/scene_blockout.pyscript6.4 KB
scripts/scene_proxy.pyscript16.6 KB
scripts/split_sheet.pyexecutablescript1.4 KB
scripts/sprinkle_pieces.pyexecutablescript2.8 KB

references/ZOOM-OUT-CHAIN.md

View on GitHub
# The zoom-out chain — a generated open that lands on real footage

A jump-zoom or drone-style open (far → near) over a place the footage already shows, made from stills, that cuts into the
first live shot without the seam showing. Measured once (an equipment-auction spot, 2026-09-15): four stills, one still
per altitude, $0.20 at the image venue, every still accepted first try, both rasters, the operator's "try it on the
cut-down too" the same evening. The rules below are what made it land; each is the cheap version of a failure the
generated-footage skills already know.

## The rule that decides everything: derive outward from the real frame

The last generated picture must be the first live frame's neighbour, or the cut shows. So the chain starts at the footage,
not at the prompt:

1. **Pick the landing frame** — the first frame of the live shot the open lands on (cut at true display shape, ungraded).
   Both rasters land on the SAME frame; a raster-specific opener (a different wide for the square) is dropped, or the chain
   is generated twice.
2. **Import it into the refs gate as a client-supplied lineage root** (`refs_gate.py --import R-<name> --file … --provenance
   "<clip>, frame at <t>"`), with two or three real wides of the place for the layout (`--import W1…`). Accept each after a
   look (`--accept`).
3. **Generate closest-first.** The first still is the landing frame seen from a little higher and further back (the same
   subjects, the same screen position). Its output becomes reference 1 of the next, wider still; the real frame and the
   wides ride along as references 2–4 so the layout holds. Four steps cover ~7 m → ~30 m → ~100 m → ~300 m.
4. **Keep the subject at one screen position** in every prompt ("the booth truck just above the centre of the frame") so
   the played-back dive reads as one camera; ask for the venue's plain, flat, ungraded colour "exactly like the references"
   so the builder's grade applies to the stills and the footage alike.
5. **Accept each still through the gate before it feeds the next** — the gate records the file's hash, so a re-rolled still
   cannot silently replace an accepted one.

## Cut and sound

- Play the chain far → near as rapid cuts with a small push-in baked on each (a 6–8 % zoom over the hold), accelerating:
  15 / 13 / 12 / 11 frames at 24 fps is 2.125 s. The landing cut IS the first live frame; nothing dissolves.
- Render the stills as 8-bit RGB clips (png codec in a .mov), never 10-bit ProRes: a 10-bit source turned black through an
  ffmpeg `colorlevels` grade and the spot's QC passed it (`video-finish-qc` § near-black).
- The prefix shifts every absolute time in the plan (type cards, the logo, cue edges): derive them from events. A music bed
  that is now too short is re-looped by whole bars so its ending still lands on the card (`video-edit-edl` § 2).
- The voice can enter on the landing cut — the open is music only, the cut lands with the first word.

## Prompt shape (image-to-image, one still per step)

"Zoom out from the first reference photo. The same <subject> and the same <people> now photographed from a drone about
<altitude> up and <distance> behind, tilted down <angle>. <What is visible at that altitude: the rows, the building, the
surroundings.> Keep every element of the first reference in the same place, only seen from higher and further back." plus
a common tail: photorealistic, vertical 9:16, same day and light as the references, flat ungraded colour exactly like the
references, no text, no lettering, no logos, no watermark, nothing invented that does not belong to the place.

The wider the step, the more the venue invents (the surroundings at 300 m are the model's idea of the region); say so in
the delivery note — the client knows what their yard's neighbours look like.

## Failure behavior

- A still that moves the subject or changes the light → re-roll that step only; the accepted steps stay.
- The landing cut visibly jumps → the last still is too far from the real frame: add a closer step, never a dissolve.
- Black or flat frames in the delivered open → the source clip's bit depth against the grade; QC per event (§ near-black).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall