Skip to content

armgit / hypit

Public Imported from GitHub
0

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

fix: separate whether a frame moves from whether its contents do (#61)

rponeawa753e433dcc9d
diff --git a/.agents/skills/hypit/references/playbooks/craft/generated-dependencies.md b/.agents/skills/hypit/references/playbooks/craft/generated-dependencies.md
index ddb9d3ba..e6f9a175 100644
--- a/.agents/skills/hypit/references/playbooks/craft/generated-dependencies.md
+++ b/.agents/skills/hypit/references/playbooks/craft/generated-dependencies.md
@@ -295,6 +295,10 @@ observation says about the picture:
- **It is still** — a screenshot, a card, a poster, a held photograph — author stills placed on a
Media Track and cut at the observed boundaries. More faithful than asking a video model to hold
something still, fully controlled, and far cheaper.
+- **Only its contents move** — a phone screen being scrolled, a browser page running past, a document
+ paged through. The frame is fixed and a still of the page goes inside it, which is the previous case
+ with the movement accounted for. `graphic-compositions.md` holds the reading and the evidence that
+ settles it; the trap is authoring the frame as the thing that travels.
Never pad a take to reach the floor. If the beat is two seconds long, it is two seconds of a longer
take or it is a still; it is not a four-second generation trimmed by two.
diff --git a/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md b/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md
index d607254b..fe4f8679 100644
--- a/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md
+++ b/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md
@@ -60,6 +60,30 @@ Never bake drawn structure into generated material. A generated picture of text
re-read or corrected, and its wording drifts. A card, inset, phone, browser or screenshot element is
not one picture: its inner picture is material, its frame and entry are structure.
+### A page scrolling inside a frame is a frame that does not move
+
+The frame and its inner picture are two things, so they move independently, and the one that is moving
+has to be named. A screen recording — a phone app being scrolled, a browser page running past, a
+document paged through — is **a frame sitting still while its contents travel**. The device stays
+exactly where it is: same position, same size, same corner radius, same edge, frame after frame.
+
+Read the wrong way round, this becomes an element that slides up and down the canvas, and that is the
+misreading to watch for: nothing in the reference translated, and the reconstruction has a phone
+sliding about the screen. The evidence separating them is the frame's own edge. Track the border,
+the corners and the outer rectangle across the stretch: if they hold their position, the frame is
+fixed and everything that moved was inside it.
+
+Author it that way. The frame is a fixed `space:Frame` at the position and size the reference holds it
+at, and the inner picture is **one still image** of the page, placed inside it. Do not generate a video
+of a scrolling page and do not animate the inner picture past the frame: a still of the page at the
+moment the reference dwells on is what the viewer reads, it is fully controlled, and it costs one
+image. `generated-dependencies.md` says the same thing from the take side — a stretch whose picture
+does not move is authored as a still rather than asked of a video model.
+
+What is worth reproducing is any state the reference shows and the still cannot: a selected row, a
+badge, a check mark. Those are drawn structure over the still, on the words where the reference shows
+them, rather than a reason to make the whole thing move.
+
## A component's own surface belongs to the component
Depicted material divides again, and getting this wrong produces a component that cannot draw
diff --git a/packages/reference-video-tools/src/tools.ts b/packages/reference-video-tools/src/tools.ts
index 8550fb41..13c31bd0 100644
--- a/packages/reference-video-tools/src/tools.ts
+++ b/packages/reference-video-tools/src/tools.ts
@@ -949,7 +949,7 @@ export function createReferenceVideoTools(options: ToolOptions = {}): ReferenceV
const previous = state.shots.find((candidate) => candidate.index === shot.index - 1);
return { key: `visual:${shot.shot_id}`, request: {
media: [shot.clip_ref, shot.representative_frame_ref, ...(previous === undefined ? [] : [previous.tail_frame_ref])],
- prompt: `${globalContext}\n\nObserve shot ${shot.index}. Describe the current base picture, any covering or non-covering visual content, and whether visible content continues from the preceding shot. A full-screen insert is still only a picture observation. Covering content is whatever changes what reaches the eye, not only things that sit on top with an edge: a wash, darkening, gradient or semi-transparent layer laid over the whole frame or a region of it is covering content and must be reported as such, including what the base shows through it.\n\nAlso answer these two questions explicitly.\n\nFirst: is the whole frame a depicted scene that has its own camera space, lighting, depth and lens behaviour, or is it a flat designed field whose purpose is to carry drawn elements such as words, rows, panels or cards? Live action and animation are both depicted scenes; a paper sheet, ruled or gridded surface, flat or gradient colour, blurred wallpaper, board or slide backdrop filling the frame is a designed field. State which one it is and the visible evidence for it.\n\nThen, whichever it is, say whether any *region* of the frame is itself a flat designed field carrying drawn content — a list, a ranking, a leaderboard, a scoreboard, a chart, a panel, a slab of colour holding rows or labels — even when the rest of the frame is a depicted scene, and even when the region has no visible border, card edge or drop shadow around it. Report each such region separately from the scene behind it: roughly where it sits and how much of the frame it covers, given as fractions of the frame width and height; what its own surface is; and what is drawn on it. A designed field occupying half the frame, one side of it, or a band across it is easy to describe as "text over the picture" and is not that: the field itself is the thing to report.\n\nSecond: for every framed element inside the picture, such as a card, phone, browser window, screenshot or inset, describe the picture inside the frame and the frame itself separately. For the inside, describe what it depicts and whether it moves. For the frame, describe its border, corner radius, outline, shadow, size, position and how it enters and leaves.\n\nThird: does this picture move at all, and how? Separate three things: whether the camera moves, and how; whether anything in the picture moves, and what; and whether the picture is completely still. A held photograph, screenshot or card that only appears and disappears is still, however long it is on screen.\n\nReturn natural language evidence only.`,
+ prompt: `${globalContext}\n\nObserve shot ${shot.index}. Describe the current base picture, any covering or non-covering visual content, and whether visible content continues from the preceding shot. A full-screen insert is still only a picture observation. Covering content is whatever changes what reaches the eye, not only things that sit on top with an edge: a wash, darkening, gradient or semi-transparent layer laid over the whole frame or a region of it is covering content and must be reported as such, including what the base shows through it.\n\nAlso answer these two questions explicitly.\n\nFirst: is the whole frame a depicted scene that has its own camera space, lighting, depth and lens behaviour, or is it a flat designed field whose purpose is to carry drawn elements such as words, rows, panels or cards? Live action and animation are both depicted scenes; a paper sheet, ruled or gridded surface, flat or gradient colour, blurred wallpaper, board or slide backdrop filling the frame is a designed field. State which one it is and the visible evidence for it.\n\nThen, whichever it is, say whether any *region* of the frame is itself a flat designed field carrying drawn content — a list, a ranking, a leaderboard, a scoreboard, a chart, a panel, a slab of colour holding rows or labels — even when the rest of the frame is a depicted scene, and even when the region has no visible border, card edge or drop shadow around it. Report each such region separately from the scene behind it: roughly where it sits and how much of the frame it covers, given as fractions of the frame width and height; what its own surface is; and what is drawn on it. A designed field occupying half the frame, one side of it, or a band across it is easy to describe as "text over the picture" and is not that: the field itself is the thing to report.\n\nSecond: for every framed element inside the picture, such as a card, phone, browser window, screenshot or inset, describe the picture inside the frame and the frame itself separately, and say separately whether each one moves. For the inside, describe what it depicts and whether its content moves — scrolling, paging, playing, changing. For the frame, describe its border, corner radius, outline, shadow, size and position, whether that rectangle stays in the same place and at the same size across the whole shot or travels, and how it enters and leaves. These two are independent and are routinely confused: a screen recording of a page being scrolled is a frame that does not move at all while its contents travel inside it. Decide it from the frame's own edge — track the border and corners across the stretch and say whether that rectangle held still.\n\nThird: does this picture move at all, and how? Separate three things: whether the camera moves, and how; whether anything in the picture moves, and what; and whether the picture is completely still. A held photograph, screenshot or card that only appears and disappears is still, however long it is on screen. Where the only movement is inside a framed element, say so in those words rather than reporting the picture as moving.\n\nReturn natural language evidence only.`,
instruction: "Observe picture only. Do not choose SVML components, do not write markup, and do not decide final source syntax.",
} };
});