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.
TypeScript agentic-aiaiai-agentsai-videocompilerdslffmpeggenerative-aillmmarkup-languagemonorepoplugin-systemprogramming-languagetext-to-videotypescriptvideovideo-automationvideo-clonevideo-editingvideo-generation
fix: content is declared, and a designed field can cover part of the frame
rpone79ab1e0847c6
diff --git a/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md b/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.mdindex 05ad321d..31145e2a 100644--- a/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md+++ b/.agents/skills/hypit/references/playbooks/craft/graphic-compositions.md@@ -29,6 +29,13 @@ original authoring and to reconstruction equally.- Text drawn over a depicted scene stays an overlay on that scene. Only a picture whose entire fieldis designed becomes a composition of its own. A framed graphic occupying part of a scene is aninserted element, and the same ownership rule applies inside its frame.+- **A designed field is still one composition when it covers only part of the frame.** A ranking+ down the left third, a leaderboard across the bottom half, a scoreboard band over a live shot —+ each is a designed field carrying authored content, and each is one component that owns its own+ surface, its rows and its reveal, sitting on a Frame that is not the whole Canvas. It does not+ become an overlay because it is small, and it does not need a visible border or card edge to be a+ field: a slab of colour holding rows is a surface. The question is never how much of the frame it+ covers, but whether what it covers is designed or depicted.- If no installed package owns the composition, that is a real vocabulary gap. Read`../../local-author-package.md` and build the package. Do not approximate it with tags that own adifferent role.@@ -64,6 +71,15 @@ The test is one question: **would two different videos using this component showthere?** If yes, it belongs to the package. If they would show different pictures, it is an edge thesource supplies.+The two are also *obtained* differently, and this is where the line is most often crossed. The+component's surface is generated once while the package is authored, with `hypit image`, and+committed inside the package — it is authoring input. Source-supplied material is **declared in the+Source as a generation** — `<gpt:Image prompt={…}/>` fed by a `copy:Value` that holds its+description — so the picture and the words that produce it live together and can be reread,+corrected and rebuilt. Generating that material yourself and pointing `media:Image src=` at the file+throws the description away and leaves a picture nobody can regenerate; `media:Image` is for material+the author already had.+Never make a component's own surface a required input. A component whose chrome arrives from thegraph cannot render on its own, cannot produce the preview image its Surface owes, and forces everyproject that installs it to obtain a picture that was never theirs to choose. If you find yourselfdiff --git a/.agents/skills/hypit/references/reference-video/index.md b/.agents/skills/hypit/references/reference-video/index.mdindex 50455e6b..87b43761 100644--- a/.agents/skills/hypit/references/reference-video/index.md+++ b/.agents/skills/hypit/references/reference-video/index.md@@ -20,6 +20,23 @@ elements are drawn on, whatever that is — is produced while the package is aut`hypit image`, and committed inside the package. `../playbooks/craft/generated-dependencies.md` drawsthat line.+**That exception covers the component's surface and nothing else.** Every other picture the video+shows — the inner picture of a card, an inserted screenshot, a thumbnail, a product shot, a logo+wall, a phone or monitor's content — is the video's content, and content is **declared in+`main.svml` as a generation**, never produced with `hypit image` into an assets directory and+referenced as a file:++```svml+<copy:Value id="meme-look">A screenshot of a vertical social-media post…</copy:Value>+<gpt:Image id="meme-shot" prompt={meme-look} aspect-ratio="4:5" resolution="2K"/>+```++Writing `<media:Image src="./assets/meme.png"/>` instead spends money this route is not supposed to+spend, and loses the thing that mattered: the prompt. A declared generation carries its own+description in the Source, so it can be reread, corrected and rebuilt; a PNG on disk carries nothing,+and the next person has to invent the prompt again. `media:Image` is for material the author+supplied, not for material you generated a moment ago.+Reference observation is part of the work and is expected to cost what it costs.## A video path is the whole requestdiff --git a/packages/reference-video-tools/src/tools.ts b/packages/reference-video-tools/src/tools.tsindex 49c481e3..fe5dd833 100644--- a/packages/reference-video-tools/src/tools.ts+++ b/packages/reference-video-tools/src/tools.ts@@ -432,7 +432,7 @@ export function createReferenceVideoTools(options: ToolOptions = {}): ReferenceVconst previous = state.shots.find((candidate) => candidate.index === shot.index - 1);const parts: Part[] = [await mediaPart(shot.clip_ref), await mediaPart(shot.representative_frame_ref)];if (previous !== undefined) parts.push(await mediaPart(previous.tail_frame_ref));- parts.push({ text: `${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.\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\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.` });+ parts.push({ text: `${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.\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.` });return await callSafely(retryDelayMs, generate, parts, "Observe picture only. Do not choose SVML components, do not write markup, and do not decide final source syntax.");}}));const typeTasks: ObservationTask[] = selected.map((shot) => ({ key: `type:${shot.shot_id}`, run: async () => {