agentleFS
ITS-MSWITS-MSW/skills/hyperframes-promo/SKILL.md

hyperframes-promo

Skill2 starsChanged 5 months agoMITView on GitHub

Structure promotional product/app videos with HyperFrames — storyboard-first workflow, scene pacing guidelines, mid-scene motion patterns, and quality gates. Companion to the core hyperframes skill; does not replace it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. PURPLE-ORCA/skills★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every scene must have continuous motion through its full duration.

    line 61
  2. Distinctive:

    Rule: Every scene gets one. Scale 1→1.02 for text-heavy, 1→1.03 for visual-heavy.

    line 68
  3. Very specific:

    Trigger: Always use for dollar amounts, days, percentages.

    line 78
  4. Distinctive:

    Rule: Never animate exit tweens before a transition — the transition IS the exit.

    line 113
  5. Distinctive:

    Use this table when translating user direction to GSAP:

    line 119
  6. Very specific:

    Run npx hyperframes validate before rendering and fix contrast warnings.

    line 142
  7. Very specific:

    GSAP tween overlap on opacity: When a from() entrance and a to() breathing/animation target the same element, the timeline's overwrite: …

    line 153

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HyperFrames Promo Video Production

Companion to creative/hyperframes. This skill fills the gap between "make a promo video" and the raw HyperFrames composition skill: scene structure, pacing, mid-scene motion, and quality gates for product/app promos.

Load both: load creative/hyperframes first, then load this one.


Workflow (Do This Every Time)

1. STORYBOARD.md   → scene-by-scene beat sheet with timings
2. DESIGN.md       → colors, typography, motion rules, anti-patterns
3. assets/         → copy app icons, logos, media into project
4. index.html      → build composition (static hero frames first, then GSAP)
5. npm run check   → lint + validate + inspect
6. npx hyperframes render --quality draft --output draft.mp4  → timing check
7. ffprobe + ffmpeg frame grab → verify duration + visuals
8. npx hyperframes render --quality standard --output final.mp4 → final delivery

Never skip step 1 or 2. Writing HTML before a storyboard produces bloated scenes and bad pacing.


Scene Template: 30s Promo (7 Scenes)

#TimeSceneDurationContent
10–3.5sBrand Hook3.5sApp icon + brand name + tagline + divider. Aggressive entrance.
23.5–7.5sThe Problem4sProvocative headline. Counter animation showing fake vs real numbers.
37.5–11.5sThe Solution4sKey metric with animated counter. Stat breakdown rows below.
411.5–16sUrgency4.5sSurvival/time clock. Progress bar filling. Warning colors.
516–21sFeatures5s4-card grid staggered in. Each card: number + label + description.
621–25sDifferentiator4s3 bullet lines with dot markers. Each staggers in from left.
725–30sCTA5sApp icon + brand + tagline + platform availability. Breathe out.

Scene Duration Reference

Content DensityDuration
Visual only (icon/hero)1.5–2s
1–3 words2–3s
4–10 words3–4s
11–20 words4–6s
21–35 words6–8s
Hard ceiling5s (unless justified)

Mid-Scene Motion (Never Static)

Every scene must have continuous motion through its full duration. Bare minimum: Ken Burns zoom.

1. Ken Burns Zoom

Slow zoom on the scene container over its full duration:

tl.to("#s1", { scale: 1.02, transformOrigin: "center center", duration: 3.5, ease: "none" }, 0);

Rule: Every scene gets one. Scale 1→1.02 for text-heavy, 1→1.03 for visual-heavy.

2. Number Counters

Animate a number from 0 to target using GSAP's onUpdate:

tl.to({}, { duration: 1.8, ease: "power1.out", onUpdate: function() {
  const val = Math.round(12480 * this.progress());
  document.getElementById("amount").textContent = "$" + val.toLocaleString();
}}, startTime);

Trigger: Always use for dollar amounts, days, percentages. Ease: power1.out for natural feel, power1.in for "loss" (slowing down hurts more).

3. Breathing Pulse

Subtle opacity pulse on the hero number:

tl.to("#amount", { opacity: 0.85, duration: 1.5, ease: "sine.inOut", yoyo: true, repeat: 1, overwrite: "auto" }, startTime);

4. Staggered Grid

Cards enter with stagger:

tl.from(".card", { opacity: 0, y: 25, duration: 0.35, stagger: 0.1, ease: "power2.out" }, startTime);

5. Progress Bar Fill

tl.to("#bar-fill", { width: "100%", duration: 3, ease: "power1.in" }, startTime);

6. Bullet Points with Dot Markers

tl.from("#row1", { opacity: 0, x: -30, duration: 0.35, ease: "power2.out" }, startTime);
tl.from("#row1 .dot", { scale: 0, duration: 0.2, ease: "back.out(2)" }, startTime);
// Repeat for each row with +0.6s stagger

Transitions

  • 80% hard cuts — clean, fast, professional
  • Flash-through-white for the key energy shift (build-up to climax)
  • Install shaders: npx hyperframes add <name>
  • Mood-to-shader mapping: calm → cross-warp-morph, professional → cinematic-zoom, aggressive → chromatic-split

Rule: Never animate exit tweens before a transition — the transition IS the exit.


GSAP Ease Vocabulary

Use this table when translating user direction to GSAP:

Natural LanguageGSAP Ease
Smoothpower2.out
Snappypower4.out
Bouncyback.out (back.out(2) for extra pop)
Springyelastic.out
Aggressive fallpower1.in

Contrast Rules

Muted text needs 4.5:1 contrast ratio on dark surfaces:

  • #18181b card bg → min #878787 for 13px text, #7c7c82 for 18px+
  • #0a0a0a bg → min #a1a1aa for 14px+ text
  • #27272a border → not suitable for text
  • #52525b on #18181b = 2.56:1 — too low. Use #71717a minimum or #878787 for 13px.
  • #52525b on #0a0a0a = 2.56:1 — bump to #a1a1aa.

The sub-muted pattern (color: #52525b, 18px) is a common trap — 18px is "large text" (≥18px) so it only needs 3:1, but the validator flags it. Use #7c7c82 to stay safe.

Run npx hyperframes validate before rendering and fix contrast warnings.


Pitfalls

  • Two clips referencing the same src image triggers duplicate-media warnings. Copy the asset to a second filename if it appears in multiple scenes.
  • GSAP to() and from() on the same element at overlapping times needs overwrite: "auto" on the later tween.
  • Scene position: absolute; inset: 0 on clip containers prevents layout overflow from bleeding across scenes.
  • No Math.random() or Date.now() — breaks deterministic rendering.
  • No repeat: -1 — compute finite repeat: Math.ceil(duration / cycleDuration) - 1.
  • GSAP tween overlap on opacity: When a from() entrance and a to() breathing/animation target the same element, the timeline's overwrite: "auto" is not the default. Add it explicitly: tl.to("#el", { opacity: 0.85, overwrite: "auto" }, time).
  • Duplicate media discovery: HyperFrames warns when the same src (img, video, audio) appears in multiple clip elements. Copy the asset file with a different name per usage (e.g. icon.png and icon-cta.png).
  • Draft quality != final quality: CRF 28 draft renders are great for timing checks but colors and text will look worse. Don't judge visual polish on draft.

Verification (After Every Render)

ffprobe -v error -show_entries format=duration -of default=nw=1:nk=1 final.mp4     # duration check
ffmpeg -i final.mp4 -ss 00:00:05 -vframes 1 preview.png                              # visual frame check
ffprobe -v error -show_streams -select_streams a -of default=nw=1:nk=1 final.mp4 | head -1  # audio check

References

  • references/scene-timing.md — detailed scene duration table + rationale
  • references/gsap-patterns.md — reusable animation code blocks
  • templates/storyboard.md — blank storyboard template to copy
  • templates/design.md — blank DESIGN.md template with motion rules section

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.