short-form-video
Skill132 starsChanged 39 days agoMITView on GitHub
Build and iterate short-form vertical (9:16) videos in Hyperframes - TikTok/Reels/Shorts style. Use when the user says "short-form video", "vertical video", "TikTok/Reels/Shorts", "make a short", "talking-head + motion graphics", or when the target is a 1080x1920 composition with face video + synced scene overlays + karaoke captions. Encodes the full May Shorts 19 playbook: face-mode choreography, audio-synced scene timing, karaoke captions, and the 10-rule quality checklist.
16 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- notivn/AIEVv2word for word, first seen Nov 8, 2026
- astDeniss/business-skillstheir own version, first seen Nov 1, 2026
- kpatdev/my-skillstheir own version, first seen Oct 26, 2026
- F0rger123/claude-video-editing-god-modeedited, first seen Oct 25, 2026
- NexumAI-online/skills-ediciontheir own version, first seen Oct 25, 2026
- tony-hoang-ai-automation/mkt-skillsedited, first seen Oct 25, 2026
Used with
Projects with it also use short-form-edit, cut-mistakes and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
antoineblc99Skillshort-form-edit
Turn talking-head footage into a finished reel, YouTube Short, or short advertisement with curiosity-led openings, earned payoffs, story-driven cuts, transcript-synced motion graphics, moving B-roll, captions, subtle music, and synchronized sound effects. Use for short-form editing; use edit-video for long-form videos and cut-silences for pause removal alone.
Also in 4 projects that use this
nateherkaiSkillcut-mistakes
Agent 2 of the video editing pipeline. Finds and removes spoken mistakes — stutters, repeated words, false starts, and retakes (re-recorded lines) — from a talking-head recording. Use after cut-silences, when asked to cut mistakes, remove stutters / repeats / filler restarts, clean up flubs, or keep the best take. Works review-gated: it proposes every cut with context and a reason for approval, then renders only the approved cuts via ffmpeg. Requires a word-level transcript.
Also in 4 projects that use this
nateherkaiSkillcut-silences
Agent 1 of the video editing pipeline. Removes silences and dead air from a talking-head recording. Use when asked to cut silences, trim pauses, remove dead air / gaps, or tighten the pacing of a raw video, given a word-level transcript. Produces an edit list (EDL), a re-timed transcript for downstream agents, and optionally the cut video via ffmpeg. Does NOT cut mistakes, repeats, or false starts — that is the cut-mistakes agent.
Also in 4 projects that use this
Google CloudSkillvideo-storytelling
Cinematic video ad storytelling expertise. Covers 3-act narrative structure, emotional arcs, camera motion, scene transitions, and voiceover pacing for 10-second commercial video ads using Gemini Omni. Load this skill when generating video ads or storylines.
Also in 4 projects that use this
ConardLiSkillmotion-showreel
用代码制作图形、文字或界面动画视频,输出 MP4 和可编辑源码,最长 20 分钟。适用于动效作品集、产品片、UI 动效、动态排版、Logo 片头、生成艺术与讲解视频;支持独立选择 BGM/音效来源、用户口播,以及用用户提供的口播稿通过 TTS 合成语音。不用于实拍制作、写实人物生成或一般视频剪辑。
Also in 4 projects that use this
iart-aiSkilllower-thirds
This skill should be used when the user asks to "make an animated lower third", "add lower thirds", "create a name tag/name lower third", "build broadcast titles", "animate a title/name/role caption", "do a speaker name overlay", or "template lower thirds across a list of names". Covers enter/exit animation (slide/wipe/mask reveal), in/out timing & dwell, safe-area & broadcast conventions, name-vs-role type hierarchy, brand styling, and rendering one design across many names.
Also in 3 projects that use this
- +2 more from nateherkai
Other versions16 projects use a version of this.
Word for word · 1
- notivn/AIEVv2★ 136100% same
Edited · 7
- nateherkai/hyperframes-student-kit★ 2.2k88% same
- nateherkai/herk-edit-kit★ 1.5k88% same
- coltonjosephdean-rgb/Hyperframes-colton.ai.dean★ 1988% same
- assafkip/claude-video-editor★ 1792% same
- tony-hoang-ai-automation/mkt-skills★ 492% same
- F0rger123/claude-video-editing-god-mode★ 188% same
- chriswestt/claude-skills★ 092% same
Wrote their own version · 8
- marcosmodly/marketing-skill★ 141same name
- iart-ai/tiktok-video-skills★ 27same name
- astDeniss/business-skills★ 8same name
- NexumAI-online/skills-edicion★ 4same name
- Jiliac/skills★ 1same name
- willlee1995/skills★ 1same name
- kpatdev/my-skills★ 0same name
- kpatdev/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-illustrationsSkill
- auto-cutSkill
- background-musicSkill
- color-gradingSkill
- gsapSkill
- hyperframes-cliSkill
- hyperframes-registrySkill
- hyperframesSkill
- key-layoutSkill
- make-a-videoSkill
- noti-tiktok-full-textSkill
- noti-tiktok-vnSkill
- noti-youtube-editSkill
- offline-voiceSkill
- remotion-assembleSkill
- skill-authoringSkill
- video-pipelineSkill
- website-to-hyperframesSkill
- webui-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
32 rules. 0 are common, 18 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
If the edit prompt contains a "STYLE DESIGN (BẮT BUỘC TUÂN THỦ 100%)" section: the palette, fonts and tone in that section COMPLETELY …
- Distinctive: line 14
MUST pass the correct styleId in the prompt.
- Distinctive: line 16
If the edit prompt ALSO contains a "PHONG CÁCH DỰNG" (video style) section: that section WINS over this skill for ALL visual and motion …
- Distinctive: line 36
Author scene boundaries in edited-time: - NEVER mix original-time and edited-time anchors in the same file.
- Very specific: line 43
Every short-form vertical has these four sub-compositions under compositions/, loaded on shared tracks:
- Distinctive: line 104
Problem: if audio is edited (retakes/pauses removed), timestamps in the source transcript no longer match the edited video.
- Distinctive: line 106
The rule: ALL timing lives in edited-time.
- Very specific: line 116
If using a shift() function in captions.html to map transcript words, treat that as the source of truth.
- Distinctive: line 133
All GSAP anchors are LOCAL (0-based from scene start)
- Very specific: line 134
Use tl.set({}, {}, <data-duration>) to pad the timeline so GSAP tl.duration() matches data-duration
- Distinctive: line 138
No dead frames: Every 100ms has ≥1 animating element.
- Distinctive: line 140
Motion through full duration: If entrance anims all land by local 2s on a 4s scene, add secondary motion: underline sweeps, checkmark pops, …
- Very specific: line 169
Use a SEEDED offline analyser (pre-compute the audio feature track) so renders are deterministic.
- Distinctive: line 175
Rotate flavors: No two consecutive transitions the same type.
- Very specific: line 206
Call Read on every PNG so the image loads into context.
- Distinctive: line 212
No blank frames, no unintentional overlap, no text-off-canvas
- Distinctive: line 226
Every short-form build. Run this list during authoring, not after.
- Distinctive: line 228
No dead frames: Every 100ms has an animating element.
- Distinctive: line 234
Rotate transition flavors: No two consecutive the same.
- Very specific: line 270
Write the Plan table: every scene data-start, data-duration, every face-mode transition t, any scene whose internal offsets straddle a cut.
- Very specific: line 276
Don't animate <video> element dimensions - freezes frames.
- Very specific: line 277
Don't use repeat: -1 on any timeline - breaks the capture engine.
- Very specific: line 278
Don't use Math.random() or Date.now() - breaks determinism.
- Very specific: line 279
Don't use <br> inside captions - natural wrapping + <br> produces extra unwanted breaks.
- Distinctive: line 280
Don't skip the frame verification gate.
- Distinctive: line 281
Don't author in original-time if the audio is edited.
- Very specific: line 282
Don't leave background: #07121c flat.
- Distinctive: line 283
Don't hard-cut between scenes.
- Distinctive: line 284
Don't polite-caption. Pop them.
- Distinctive: line 285
Don't let the face sit still.
- Very specific: line 303
Always keep HIDDEN's x, y, scale identical to BOTTOM - they only differ in opacity - so the opacity-fade scenes don't drift geometrically …
- Very specific: line 311
Start it 0.25–0.30s before the new scene's data-start (not the default 0.15s)
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Short-Form Vertical Video (Hyperframes)
⚖️ STYLE DESIGN - HIGHEST PRIORITY RULE (read this first)
If the edit prompt contains a "STYLE DESIGN (BẮT BUỘC TUÂN THỦ 100%)" section: the palette, fonts and tone in that section COMPLETELY REPLACE every color/font/branding rule in this skill (including "dark fintech blue", the GĐT hex codes, the default gradients...). Keep only: animation technique, layout, cut rhythm, render workflow, and the bug fixes. Illustrations generated via /api/illustrations MUST pass the correct styleId in the prompt. NO Style Design section -> use this skill's default branding.
If the edit prompt ALSO contains a "PHONG CÁCH DỰNG" (video style) section: that section WINS over this skill for ALL visual and motion language - materials, transitions, camera moves, effects. This skill then keeps only PROCESS: step order, cutting, captions/keys, draft->final, QC. Do not mix the skill's default visuals into the video style - half-and-half is exactly the failure this rule exists to prevent.
Short-form = 1080x1920 vertical, 10–30s, talking-head face + motion-graphic scene overlays + karaoke captions. Everything in this skill is distilled from the May Shorts 19 iteration autopsy (v1 → v4) and should be applied on every new short.
Always invoke /hyperframes first. This skill sits on top of it - it does not replace the framework rules (data-* attributes, window.__timelines, composition structure). Those are non-negotiable regardless of the format.
When this skill fires
- "Make a short-form video", "TikTok post", "Reels", "Shorts", "vertical video"
- Any build starting from a talking-head recording + script/transcript intended for social
- Retiming, recutting, or re-syncing an existing short
- Adding karaoke captions synced to a voiceover
The playbook (high-level)
- Audio is source of truth. Edit audio FIRST (cut retakes, pauses). Save as
<name>-edit.mp4. Measure exact duration withffprobe- this is the composition'sdata-duration. - Transcribe the edited audio with
npx hyperframes transcribe <edit>.mp4 --model small.en --json(English only - for Vietnamese use faster-whisper per the noti skills), or if retiming an existing build with ashift()function in captions, keep the existing captions and just shift scene starts. - Author scene boundaries in edited-time - NEVER mix original-time and edited-time anchors in the same file. See "Audio-sync protocol" below.
- Build the composition scaffold (4 layers: ambient-bg, seam-treatment, captions, face) - see "Composition scaffold" below.
- Author scenes with LOCAL offsets relative to each scene's
data-start. Each scene is its own sub-composition undercompositions/scene<N>-<label>.html. - Lint → draft render → word-exact frame verification → final render. This is the verification gate. Never skip step 3 (frame verification).
Composition scaffold (the 4 always-on layers)
Every short-form vertical has these four sub-compositions under compositions/, loaded on shared tracks:
index.html (root, 1080x1920, data-composition-id="main")
├── ambient-bg.html track-index="3" - radial gradient + drift grid + particles + vignette
├── face-wrapper + <video> track-index="0" - talking head (see face-mode choreography)
├── seam-treatment.html track-index="5" - feathers y=960 edge (bottom-half scenes only)
├── scene1-<label>.html track-index="1" - scene overlays (back-to-back, no gaps)
├── scene2-<label>.html track-index="1"
├── …
└── captions.html track-index="2" - karaoke captions, word-synceddata-durationis identical across root, ambient-bg, seam-treatment, face-video, face-audio, captions. Only scene overlays change over time.<audio>for the face is a SEPARATE element (mixer needs it), never use the video's own audio track.class="clip"goes on timed divs - NEVER on<video>or<audio>.
Face-mode choreography (the signature move of short-form)
The face lives in a wrapper div sized at the source's native landscape (1920x1080). GSAP animates the WRAPPER (never the video element - animating <video> dimensions freezes frames).
Two modes:
const BOTTOM = { x: 0, y: 1136, scale: 0.5625 }; // bottom-half, full landscape visible
const FULLSCREEN = { x: -1166.5, y: 0, scale: 1.7778 }; // cropped-cover, fills 1080x1920
const MODE_DUR = 0.32;BOTTOM renders the 1920x1080 source at 1080x607.5 centered in the bottom 960px. FULLSCREEN crops horizontally to fill the portrait frame.
Transition 0.15s BEFORE the new scene's content lands, using ease: "expo.inOut":
[
{ t: <scene-4-start>, mode: FULLSCREEN },
{ t: <scene-5-start>, mode: BOTTOM },
…
].forEach(({ t, mode }) => {
mainTl.to("#face-wrapper", { ...mode, duration: MODE_DUR, ease: "expo.inOut" }, t - 0.15);
});A face that snaps modes instantly is the single most jarring frame in a vertical video. Always interpolate.
Face grading (every short, no exceptions)
#face-video {
filter: contrast(1.08) saturate(1.08) brightness(0.97);
}Plus a subtle 1.00 → 1.025 Ken Burns zoom over the full duration (ease: "none") and a side-vignette ::after pseudo-element so the face sinks into the surrounding navy instead of butting against a razor edge.
Seam treatment (required for bottom-half scenes)
A navy→transparent gradient band (60–100px) at y=960 plus a 2px accent scan line with soft glow. Draw it AFTER the face so it sits on top; full-screen scenes will cover it when they take over. Razor-sharp y=960 cuts are the #2 tell for AI-edited content (after background flatness).
Audio-sync protocol (DO NOT skip)
Problem: if audio is edited (retakes/pauses removed), timestamps in the source transcript no longer match the edited video. Scene starts authored in original-time will fire late.
The rule: ALL timing lives in edited-time. Never mix.
Verification procedure for any short-form retime:
- Measure both audio files:
Difference = total cut time.ffprobe -v error -show_entries format=duration -of csv=p=0 assets/original.mp4 ffprobe -v error -show_entries format=duration -of csv=p=0 assets/<name>-edit.mp4 - If using a
shift()function incaptions.htmlto map transcript words, treat that as the source of truth. The mapshift(originalTime) = editedTimeapplies to EVERY scenedata-starttoo. - Scene internal offsets (inside
compositions/sceneN.html) are LOCAL relative to the scene'sdata-start. If a scene's parentdata-startis correct in edited-time, internal offsets stay correct WITHOUT modification - UNLESS a scene straddles a cut, in which case both the parent duration AND internal offsets shift. - Face-mode transition array times MUST use edited-time. They are NOT automatically shifted.
Plan format for retimes (use this table structure every time):
| Scene | Current start | Current dur | New start | New dur | Rationale |
| ... | ... | ... | ... | ... | ... |
Then the face-mode array, then any internal-offset changes, then frame-verification list.
Scene authoring
One scene = one sub-composition file. Scenes sit on the same data-track-index back-to-back (no gaps). Inside each scene:
data-durationmatches the parent's slot exactly- All GSAP anchors are LOCAL (0-based from scene start)
- Use
tl.set({}, {}, <data-duration>)to pad the timeline so GSAPtl.duration()matchesdata-duration
Scene pacing rules (from the 10 principles)
- No dead frames. Every 100ms has ≥1 animating element. Offset first entrance 0.1–0.3s, not t=0.
- Payoff ≥ 1s hold. The "big reveal" of the scene (stamp, number lock, punchline) must have ≥1s on screen, ideally 1.5s. Budget scenes by reveal time, not total time.
- Motion through full duration. If entrance anims all land by local 2s on a 4s scene, add secondary motion: underline sweeps, checkmark pops, ambient drift on cards, small oscillating glows on pills. Dead pacing = swipe-away.
- Vary eases. At least 3 different eases per scene across entrances.
- One jaw-dropper per 5s of runtime. Typography slam, glitch/chromatic reveal, whip-pan, audio-sync slam. Without these, the video reads as "labeled talking head" - correct but forgettable.
Captions (karaoke style)
- Montserrat 900, 46–58px (for 1080 width), 100% white base
- Active word: scale-1.08 pop + color change to the brand accent color (from the Style Design)
- Stroke via layered
text-shadow, NEVER-webkit-text-stroke(renders inconsistently in Chromium render) - Drop the rgba background pill - let the stroke hold readability. Captions should feel like graffiti on the frame, not a subtitle track.
- For retimes, use a
shift()function insidecaptions.htmlto map transcript word timestamps → edited-time. This keeps the transcript JSON untouched and makes retimes mechanical.
See references/captions.md under /hyperframes for the full karaoke implementation. TL;DR: per-word <span> elements with data-word-start, GSAP tweens scoped to each span, tight 0.08–0.12s pop durations.
Ambient background (never ship flat navy)
Minimum viable background stack:
- Radial gradient base (center lighter than edges by 15–20%)
- Animated noise/grain overlay at 8–12% opacity
- 4–8 drifting particle dots or grid traces
- Subtle vignette
background: #07121c alone is a placeholder, not a design. For a techy/control-room aesthetic, use a 6-layer stack: HUD grid masked to vignette + circuit traces + pulse nodes + scan beam + telemetry ticker + corner mono labels.
Audio reactivity
- Headlines pulse 3–6% on beat. Backgrounds can go 10–30% on bass.
- Text reactivity kept subtle (3–6%) so captions stay readable; backgrounds can push harder.
- Use a SEEDED offline analyser (pre-compute the audio feature track) so renders are deterministic. Do NOT use
AnalyserNodein the render path -Math.random()and real-time audio nodes break determinism.
Transitions
When the edit prompt has a PHONG CÁCH DỰNG (video style) section, its motion spec overrides these transition/effect rules.
- Rotate flavors. No two consecutive transitions the same type. Six hard cuts in a row is the #1 tell for AI editing.
- Face-mode transitions (
BOTTOM ↔ FULLSCREEN) double as scene transitions when the mode changes between scenes. - For pure overlay scene-to-scene, install from registry:
push-up,flash-through-white,sdf-iris, or the full shader-transitions pack.npx hyperframes catalog --type blockto browse.
The verification gate (mandatory - DO NOT ship without)
Lint passing ≠ design working. Never report a short-form render done until you have extracted frames at word-exact timestamps and READ every PNG.
Step 1 - draft render
cd video-projects/<slug>
npx hyperframes lint
npx hyperframes render --quality draft --output renders/<slug>-vN-draft.mp4Step 2 - word-exact frame extraction
Pick 8–15 timestamps that each correspond to a SPOKEN WORD where a specific visual should be on-screen. Not round numbers. Not mid-scene. The exact word.
mkdir -p renders/frames-vN
for pair in "<t>:<label>" "<t>:<label>" ...; do
t="${pair%%:*}"; label="${pair##*:}"
ffmpeg -y -ss "$t" -i renders/<slug>-vN-draft.mp4 \
-frames:v 1 -q:v 2 "renders/frames-vN/t${t}-${label}.png"
doneStep 3 - Read every PNG
Call Read on every PNG so the image loads into context. Do NOT just list filenames. For each frame confirm:
- The expected visual is on-screen at the expected moment (not 1s late, not early)
- Speaker's face is not cropped in any bottom-half scene
- Full-screen vs bottom-half face mode is correct for that scene
- Captions are on-brand, readable, not overflowing
- No blank frames, no unintentional overlap, no text-off-canvas
Step 4 - if anything fails, fix + re-verify. Never ship broken.
Step 5 - final render
npx hyperframes render --quality standard --output renders/<slug>-vN.mp4Spot-check 3–4 frames from the final render (same timestamps, different folder frames-vN-final/) to confirm the standard-quality encode didn't change anything.
The 10 rules (quality checklist - run BEFORE first draft)
Every short-form build. Run this list during authoring, not after. When a PHONG CÁCH DỰNG (video style) section is present, its motion spec overrides the transition/effect rules below - keep the process, swap the visuals.
- No dead frames. Every 100ms has an animating element.
- Scene payoff ≥ 1s hold. Budget by reveal time, not total time.
- Face is a character. Grade + Ken Burns + side vignette.
- No hard seams. Feather y=960 with gradient + scan line.
- One jaw-dropper per 5s. Typography slam, glitch, whip-pan, audio slam.
- Audio reactivity non-negotiable. 3–6% text, 10–30% background.
- Rotate transition flavors. No two consecutive the same.
- Captions pop, don't politely label. Stroke not pill. Scale + color on active word.
- Motion through full scene duration. Secondary motion if entrances land early.
- Background is a layer, not a color. Radial + noise + particles + vignette minimum.
- Slam/stamp overlays land AFTER target text is fully visible. Reveal logic > word-sync. Stamp
t≥ target-visiblet+ 0.10–0.25s. Otherwise the punchline lands before the setup.
Project structure (every short-form project)
video-projects/<slug>/
├── hyperframes.json
├── meta.json (id, name, dimensions 1080x1920, fps 30)
├── index.html (root composition, the 4-layer scaffold)
├── compositions/
│ ├── ambient-bg.html
│ ├── seam-treatment.html
│ ├── captions.html (with shift() function if retiming)
│ ├── scene1-<label>.html
│ ├── scene2-<label>.html
│ └── ...
├── assets/
│ ├── <name>.mp4 (original recording)
│ ├── <name>-edit.mp4 (edited - cuts removed - this is what the comp uses)
│ ├── transcript.json (whisper output)
│ └── brand assets (logo, brand-tokens.css, background music)
└── renders/
├── <slug>-v1-draft.mp4
├── frames-v1/
├── <slug>-v1.mp4
└── ...Retime protocol (when audio is re-edited or timestamps drift)
- Measure old and new edited audio durations with
ffprobe. Delta = total cut time. - Identify cut window(s): which seconds were removed, from where.
- Write the Plan table: every scene
data-start,data-duration, every face-mode transitiont, any scene whose internal offsets straddle a cut. - For each scene that straddles a cut, both its parent duration AND its internal offsets change. Scenes entirely on one side of the cut just need parent
data-startshifted. - Lint → draft render → word-exact frame verify → final render. No shortcuts.
What NOT to do in short-form
- Don't animate
<video>element dimensions - freezes frames. Animate wrapper div. - Don't use
repeat: -1on any timeline - breaks the capture engine. Finite counts only. - Don't use
Math.random()orDate.now()- breaks determinism. Seeded PRNG if pseudo-random needed. - Don't use
<br>inside captions - natural wrapping +<br>produces extra unwanted breaks. - Don't skip the frame verification gate. Lint exit code is not visual truth.
- Don't author in original-time if the audio is edited. Edited-time or nothing.
- Don't leave
background: #07121cflat. Layer it. - Don't hard-cut between scenes. Rotate transition flavors.
- Don't polite-caption. Pop them.
- Don't let the face sit still. Grade + Ken Burns always.
Lessons from may-shorts-18 (v1 → v2)
Distilled from the 4 concrete problems the v1 render had and what fixed them in v2. Apply these on every new short.
1. Slam/stamp timing - reveal logic beats word-sync
A SLAM/STAMP overlay (KILLED, DEAD, STOP, etc.) lands AFTER its target text is fully visible, not during the spoken word. In may-shorts-18 v1 scene 1, CLAUDE and CHATGPT were pitched as opponents - KILLED fired at local 0.46s while CHATGPT didn't appear until 0.66s, so viewers saw "Claude … KILLED" with no visible target. The joke collapsed.
Rule: stamp_t ≥ target-text-visible_t + 0.10–0.25s. The "visible" timestamp is the END of the target's entrance animation, not its start. Word-sync is a guideline; visual reveal order is the constraint.
2. BOTTOM face-mode scale - don't ship the default
Default BOTTOM = { x: 0, y: 1136, scale: 0.5625 } (exact horizontal fit for a 1920×1080 source) leaves empty studio background flanking the speaker if they occupy <70% of the source frame. This is the default in may-shorts-19 and was copied into may-shorts-18 v1 - both videos had visible dead space left and right of the speaker in every BOTTOM scene.
Rule: prefer BOTTOM = { x: -180, y: 1110, scale: 0.75 } - crops 180px each side, bottom-anchors to y=1920. Preview ONE frame of BOTTOM mode against the actual source video before committing the constant. If the source speaker is tight-framed already, scale 0.65 may be enough; if the source is wide studio framing, push to scale 0.80 and re-tune x.
Always keep HIDDEN's x, y, scale identical to BOTTOM - they only differ in opacity - so the opacity-fade scenes don't drift geometrically mid-fade.
3. Face-mode transitions - three things at once, not one
When the face changes mode between adjacent scenes, a bare 0.15s pre-roll + 0.32s duration expo.inOut on just the face wrapper reads as rigid - the outgoing scene's panels are still fully opaque behind the morphing face, so the eye sees two things fighting instead of a crossfade.
Rule: for any "hero" scene-to-scene face-mode change (especially BOTTOM ↔ FULLSCREEN), do all three:
- Extend that specific transition's duration to 0.45–0.55s (not the default 0.32s)
- Start it 0.25–0.30s before the new scene's
data-start(not the default 0.15s) - Fade + blur the outgoing scene's panel wrapper to
opacity: 0, filter: blur(6px)over 0.20–0.25s, starting 0.25s before scene end
Implementation-wise, promote the face-mode transition array to per-entry dur so one transition can be longer than the others:
[ { t: 2.06, mode: FULLSCREEN, dur: 0.50 }, { t: 3.71, mode: HIDDEN, dur: 0.32 }, ... ]
.forEach(({ t, mode, dur }) => mainTl.to("#face-wrapper", { ...mode, duration: dur, ease: "expo.inOut" }, t));Three simultaneous changes = "a real editor edited this." Any one alone = rigid.
4. Data-feel scenes beat decoration scenes mid-video
For scenes 3–5 of a 15–20s short (the "middle grind" where attention drops the hardest), lean on visuals that read as information - bar races, stat grids with counting numbers, heatmaps, sparklines, flowcharts, dashboard chrome with telemetry ticking, pain-point grids that flash red in sequence. may-shorts-18 v1 scene 4 was a radar-rings + terminal-chip + sparks combo - functional but decorative, and the user called it "bland." v2 replaced it with a 3×3 pain-point grid lighting up red-orange in sequence + a sparkline stroke-drawing with a YOU-ARE-HERE marker + the payoff slam - same time budget, much higher engagement.
Rule: pure typography-plus-icon scenes feel like slides. Data-feel scenes feel like evidence. When a middle scene feels bland, replace the decoration with something that reads as information: a small number ticking up, a bar filling, a chart stroking in, a grid flashing in sequence.
Reference compositions
video-projects/ is gitignored, so the projects below exist only on the author's machine and are NOT shipped with the repo. Everything they demonstrate is already written out in this skill - the folder layout in "Project structure" above, the scene/caption/SFX wiring in the sections before it. Skip this section if the folders are absent; do not go looking for them.
video-projects/mcp-tiktok-2/(author-local) - a vertical short at 1080x1920: HyperFrames scenes over footage cuts, SFX timed by frame, karaoke captions.video-projects/sapo/(author-local) - a footage-driven short: zoom keyframes on the footage, overlays, and the SFX table kept inmeta.json.
Related skills (invoke in addition)
/hyperframes- framework rules (always first)/hyperframes-cli- CLI commands (init, lint, preview, render)/gsap- animation library reference/hyperframes-registry- installing transition blocks
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

