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.

docs: a covering overlay decides how the base is framed

rpone2fa40a898295
diff --git a/.agents/skills/hypit/references/playbooks/craft/image-prompt-style.md b/.agents/skills/hypit/references/playbooks/craft/image-prompt-style.md
index c01bd290..529c9b0a 100644
--- a/.agents/skills/hypit/references/playbooks/craft/image-prompt-style.md
+++ b/.agents/skills/hypit/references/playbooks/craft/image-prompt-style.md
@@ -48,6 +48,9 @@ into separate prompts.
third-party camera owns the shot, do not call it a selfie.
- Make shot size agree with the story. Do not place essential feet, table-under actions, or lower-body
props outside a close or waist-up frame.
+- Make shot size agree with the overlays too. A board, band or sheet that covers part of the frame for
+ most of the video decides where the subject can be, so frame for the region that is left rather than
+ for the whole picture; `overlays.md` states the rule and how to write it as geometry.
- For reverse views, define both background sectors before writing prompts and apply the hard rule in
`visual-continuity.md`.
- Make before/after states visibly distinguishable through the authored condition, posture, setting,
diff --git a/.agents/skills/hypit/references/playbooks/craft/overlays.md b/.agents/skills/hypit/references/playbooks/craft/overlays.md
index a21a0390..e9b44dc9 100644
--- a/.agents/skills/hypit/references/playbooks/craft/overlays.md
+++ b/.agents/skills/hypit/references/playbooks/craft/overlays.md
@@ -16,6 +16,28 @@ stack order.
- Keep base-generation prompts free of editorial captions, arrows, cards, floating logos, and UI
callouts. Author those elements separately.
+## A covering overlay decides how the base is framed
+
+An overlay that holds a fixed region of the frame for a long stretch — a tier board across the bottom
+half, a leaderboard band, a scoreboard, a full-width lower third, a screenshot filling the top half —
+takes that region away from the picture underneath. The base has to be generated for the frame that
+is left, not for the whole one.
+
+- Work out which region the overlay covers before writing the base prompt, and frame the subject
+ clear of it: a strip owning everything below 51% of the height means the speaker's head, face and
+ shoulders sit **above** the midline, not centred in the whole frame.
+- Say it as positive geometry in the prompt — where the eyes fall, where the shoulders end, what is
+ in the part the overlay will cover. Never name the overlay itself; a generator told about a graphic
+ draws one.
+- The same applies to a persistent overlay at the top: a sheet covering the upper half pushes the
+ subject down, and a base framed for it looks wrong the moment the overlay leaves. If one shot is
+ covered at the top and another at the bottom, those are different framings and therefore different
+ images, not one image used twice.
+- A face, a mouth or a gesturing hand behind an opaque overlay is the failure this prevents, and it
+ survives every structural check: the Source is legal, both tracks build, and the speaker is
+ headless. Check it at the image gate in `production-gates.md`, where overlay clearance is already
+ on the list.
+
## Choose the native overlay surface
Use `typo:Track` for editable typography: