product-launch-motion
Use when asked to make a launch video, product film, motion design piece, UI motion reel, Dribbble-style UI animation or animated brand/logo sting — anything rendered to MP4 from HTML with a cursor, morphing UI, springs, beat-synced music and SFX. Carries Chan's full creative direction (one shape never cut, blur content swaps, springs, real data, logo slams, no creative limits) and the proven build/render pipeline (pure seek(t), closed-form springs, Playwright subframes, ffmpeg tmix, numpy beat grid).
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/abubakrchan--product-launch-motion)HTML
<a href="/listings/abubakrchan--product-launch-motion"><img src="/api/listings/abubakrchan--product-launch-motion/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 119 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: product-launch-motion
- description: Use when asked to make a launch video, product film, motion design piece, UI motion reel, Dribbble-style UI animation or animated brand/logo sting — anything rendered to MP4 from HTML with a cursor, morphing UI, springs, beat-synced music and SFX. Carries Chan's full creative direction (one shape never cut, blur content swaps, springs, real data, logo slams, no creative limits) and the proven build/render pipeline (pure seek(t), closed-form springs, Playwright subframes, ffmpeg tmix, numpy beat grid).
- ---
- # Motion design launch videos
- This is how Chan wants launch films made. It is the distilled direction from every prompt and review
- that produced "The Spark" (v1) and the real-data cut (v2) for Cheerful.
- The prompts themselves, verbatim and in order, are in `references/prompts.md` — read them before
- starting; they are the spec. The code patterns are in `references/technique.md`.
- Prior films demonstrate the technique; compose this product's own story from its customer's
- problem, current brand assets and actual behavior. Preserve the one-shape continuity throughout.
- ## The stance: you are the director
- - **No constraints on creativity.** Chan says "I want you to be the director", "full creative control",
- "think out of the box", "no limits on shapes or buttons". Do not ask permission for creative choices;
- make them, log them as DECISIONs, and list them at the end so he can overturn any in one reply.
- - **Original, never a template, never a copy.** Do not lift the product website's copy, UI, stats or
- images wholesale. Invent the scenes. "Anything that looks like a template" is banned.
- - **Launch-film energy.** Modern, futuristic, premium — the way top motion designers do it (Linear,
- Apple, Arc). Something happens on every beat; there is no dead time.
- - **Attention to detail is the product.** Micro-interactions (button press, knob stretch, name pill
- lag, click ripple, odometer settle, sticker tilt) are what make it read as expensive.
- - **Make it easy to follow.** One clear takeaway per scene, short prompts and answers, and enough
- settled time to read the result. Keep the beat alive through secondary motion and sound while
- the main idea holds; simplify the content or add beats rather than rushing the viewer.
- ## Non-negotiable motion rules
- 1. **One shape, never cut.** Every state is the same element morphing its size, radius and colour
- while its content swaps with a short blur. Cuts are not encouraged; transitions are morphs,
- camera moves, zooms into an element that becomes the next scene (a tile opens into an inbox,
- a reply card becomes the order, the cursor becomes the logo star).
- 2. **Content swaps with a short blur**, and text inside a morphing container gets its own enter and
- exit timing — exit short and early — or old and new text overlap.
- 3. **Springs everywhere, a tiny overshoot at most.** No bouncy easing. Closed-form damped spring step
- responses only (see technique).
- 4. **Leading/trailing edges on different springs** so things stretch: tab indicators, toggle knobs,
- liquid pills — the leading edge runs ahead of the trailing one.
- 5. **A cursor drives every change with real clicks and drags.** Drags are direct manipulation: while
- held, the value is computed from the cursor position; on release it springs back from wherever it
- was. The product's agent can be its own cursor (a gradient multiplayer cursor with a name pill, a
- short motion trail, lean with velocity, press scale + ripple on clicks) handing off from the user's
- cursor ("You").
- 6. **The camera zooms so each state fills the frame.** Empty frames are a bug; frame the content, then
- push, whip or pull back. Pull-backs reveal scale (one email → a grid of hundreds; one post → a wall).
- 7. **Music-first timing.** Choose the soundtrack before choreographing: energetic, brand-appropriate,
- with a build, a clear drop and a satisfying ending. BPM alone is not energy; do not default to a
- repetitive synthesized loop. Use a licensed track or an original score with that musical arc.
- Aim for ~120 BPM, analyse the song with numpy for the beat grid, start on a
- downbeat, cut the song window so the drop lands on the product's big moment. Something happens on
- every beat; typing rides 32nds on a snare build; slams accelerate beats → 8ths → 16ths.
- 8. **Every UI sound is synthesized and placed by its measured peak** on the kick-peak grid.
- Treat sound design as seriously as the visuals: original, layered sound effects that make the
- film feel rich and alive (the Hoopoe Club film is one example). Be creative with it.
- 9. **Loops:** when the piece loops, the last frame is the first frame — cursor position and speed
- included — or the loop stutters.
- ## Look
- - **Palette:** the brand's own design system (for Cheerful: warm near-white canvas, brand gradient
- #B04ADC → #E35C91 → #FF7247 → #FFB21E, lilac/peach light pools, ink #111827). Not "black plus one
- purple". One clean UI font.
- - **Banned (from the original brief, still binding unless Chan overrides):** bouncy easing, particle
- bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, template looks.
- ## Content
- - **Use real data.** Chan: "You have access to the database. You can be creative and not just pick
- images." Pull real, defensible numbers read-only (creators reached, gifts sent, posts/views
- tracked) and show them as rolling odometers. Invent the micro-story (creator, brand, messages) but
- keep the big numbers true, and say which is which in the report.
- - **Customer logos one by one, boom boom boom** — never a website-style "trusted by" row. One shape
- re-sized/re-coloured on every hit, only brands that really ran campaigns.
- - **Licensed media only.** Stock video/stills from free-licence sources, checked per item (Mixkit has
- Restricted items mixed in). Never the product's own marketing images as a shortcut.
- - **Keep what he liked:** for Cheerful the headline intro, the typed brief, the discovery search wall
- and the wordmark ending tested well — keep strong beats between versions and iterate the rest.
- ## Process
- 1. **Ask for inputs first** (unless already given or he says "you decide"): 8–12 states the shape
- should become, palette (B/W, one accent, or the brand system), and a royalty-free ~120 BPM song.
- Offer "Director's cut / Director picks" options — he usually picks those.
- 2. **Direct first, implement second.** Finalize a concise creative plan before writing animation code:
- the product story and payoff, brand treatment, soundtrack and musical arc, then a beat-by-beat
- scene plan covering framing, key interactions, transitions and sound cues. Show the plan, resolve
- gaps as the director, and only then implement it. Do not wait for approval unless requested.
- Give each scene a clear takeaway and reading window, and carry a recognizable customer example
- through the demo. Simplify real product behavior for film without inventing actions or outcomes.
- 3. **Build** one HTML file where every style is computed from time inside `seek(t)` — no CSS
- transitions, no timers, no state between frames.
- 4. **Render one frame per beat before the full render**, contact-sheet it, and fix anything off the
- grid, cramped, empty, hard to read or overlapping. Then check transitions at ±0.1 s. Review a
- low-resolution moving draft at normal speed before the full render: verify readable holds,
- cursor actions and continuous morphs. Still frames alone cannot prove the timing works.
- 5. **Full render** with Playwright subframes → ffmpeg tmix motion blur → 60 fps H.264 + mix.
- 6. **Verify the MP4 itself** with a 1-per-second storyboard and a frame-difference scan for seams
- and glitches. Review its pacing and transitions at normal speed, check for flicker, and verify audio cue sync
- against the picture. Listen when playback is available; distinguish listening from measurements.
- Serve it over the tailnet, and report: link, concept, scene list, real-vs-invented data,
- DECISIONs, caveats (whether audio was heard or only measured; logo/likeness permissions).
- ## Gotchas that cost hours
- - Never put `will-change` on anything the camera scales — text renders blurry.
- - Springs start at their event: a target that must *arrive* at time T is issued one settle-lead early.
- - `hide()` that zeroes opacity must be undone by the draw function, or elements stay invisible.
- - Proportional digits jump in odometers: size each slot to its final glyph, clip only vertically.
- - On the VPS: disk is tight (render in 4 s chunks and delete PNGs), Chromium is the first thing
- earlyoom kills (auto-retry, relaunch, hard-exit when done), a stray `/tmp/inspect.py` shadows the
- stdlib (run Python from the project dir), PreToolUse hooks block some ffmpeg glob strings.
- ## Output
- Deliverables in a `deliver/` folder served with `serve <dir>` (tailnet URL, never localhost):
- the MP4, a 1-per-second storyboard, key stills, and the previous version for comparison.
README.md · README · 158 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Product Launch Motion — a Claude Code Skill
- ### Paste your website URL. Get a product launch video. That's it.
- ```bash
- npx skills add AbubakrChan/product-launch-motion
- ```
- Already installed it? Get the latest version with `npx skills update`.
- [](https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/launch-film-1080p60.mp4)
- **No Claude Code? Get the film made for you: a polished launch video in 30 minutes, from $20 → [launchvideos.app](https://launchvideos.app)**
- Then, in Claude Code:
- > Make a launch video for https://your-website.com
- Claude reads your site, writes the story, directs every scene and renders a 60 fps MP4 with
- music, synced sound effects and real motion blur. No editing, no After Effects, no templates.
- The film above started the same way: a URL, then a few rounds of notes.
- <details>
- <summary><b>v2 is here.</b> Use it with Claude Opus 5.5 to get results like these films.</summary>
- This skill has been rebuilt on a newer, simpler stack: plain HTML and closed-form springs
- instead of GSAP and HyperFrames, music-first timing instead of voiceover, and Playwright
- subframes with ffmpeg motion blur. **Use it with Claude Opus 5.5 to get results like these
- films.** The original v1 (190 ⭐, thank you) is kept in [`legacy/`](legacy/).
- </details>
- > 🔊 **Download it and turn the sound on.** The preview above is silent. The real film is cut to the beat
- > of its music, and every click, whoosh and number roll lands on a drum hit.
- > **[Download the film (1080p, 60 fps, with sound)](https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/launch-film-1080p60.mp4)**
- > to watch it as intended.
- 30 s, made for [cheerful.ai](https://www.cheerful.ai). No After Effects, no stock templates,
- no AI video model: every frame is HTML computed from time. Bonus: the same film with a
- [WebGL glass pass](https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/launch-film-glass-1080p60.mp4)
- (refractive 3D shapes floating through every scene).
- <table><tr>
- <td width="45%"><a href="https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/one-shape-loop-1440.mp4"><img src="examples/one-shape-loop.webp" alt="One shape, never cut: a button becomes a loader, a check, a creator reel, a rate slider, a toggle, tabs, a chart, a command palette and a toast, then loops"></a></td>
- <td>
- **[▶ One shape, never cut](https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/one-shape-loop-1440.mp4)**
- (14 s seamless loop, 1440×1440, with sound)
- The idea the whole skill is built on. One element morphs through eleven UI states:
- button → loader → check → dynamic island → video reel → slider → toggle → tabs → chart →
- ⌘K palette → toast → button. Its content swaps with a short blur, the cursor does every
- click and drag, and the last frame is the first frame.
- </td></tr></table>
- [](https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/hoopoe-club-1080p60.mp4)
- **[▶ Hoopoe Club](https://github.com/AbubakrChan/product-launch-motion/releases/download/v2.0.0/hoopoe-club-1080p60.mp4)** · 43 s, Arabic, with sound
- ---
- ## What makes it look expensive
- These are the rules the skill enforces. Each one came from a review note on a real film
- ([`references/prompts.md`](references/prompts.md) has the prompts and notes, verbatim).
- - **One shape, never cut.** Every state is the same element morphing size, radius and
- colour. Transitions are morphs, camera pushes, or zooms into an element that *becomes*
- the next scene.
- - **Blur content swaps.** Text inside a morphing container exits short and early, then the
- new text springs in. Nothing overlaps.
- - **Springs, a tiny overshoot at most.** Closed-form damped springs, never bouncy easing.
- Toggle knobs and tab indicators stretch because their two edges ride different springs.
- - **A cursor drives everything.** Real clicks with press-scale and ripple, real drags that
- spring back on release. The product's own agent can take over as a second cursor.
- - **The camera frames every state.** An empty frame is a bug. Pull-backs reveal scale: one
- email becomes a wall of hundreds.
- - **Music first.** The beat grid is measured with numpy, the drop lands on the big moment,
- and every synthesized UI sound is placed by its own measured peak, so it hits the beat.
- - **Real data, original scenes.** Real numbers on odometers, customer logos slammed one per
- beat, and nothing copied from the product's website.
- - **You get a director.** It makes the creative calls itself and logs each one as a
- `DECISION:` line you can overturn in one reply.
- ## What's in the box
- | Path | What it is |
- |---|---|
- | [`SKILL.md`](SKILL.md) | The creative direction and the process Claude follows |
- | [`references/prompts.md`](references/prompts.md) | The original prompts and every review note, verbatim. Swap the product and reuse them |
- | [`references/technique.md`](references/technique.md) | Springs, camera, cursor, odometer, audio and render code patterns |
- | [`legacy/`](legacy/) | The v1 skill: voiceover-led films with GSAP + HyperFrames, 34 traps |
- ## Requirements
- | Need | For |
- |---|---|
- | [Claude Code](https://claude.com/claude-code) with **Opus 5.5** | Directing and building the film. Smaller models follow the rules but miss the detail |
- | Node ≥ 20 + Playwright | Rendering |
- | FFmpeg | Motion blur, encoding, loudness checks |
- | Python 3 + numpy | Beat grid and synthesized SFX |
- | A ~120 BPM royalty-free song | Optional. Check each track's licence; some free libraries mix in restricted items |
- Everything runs locally and nothing costs money.
- ## How it works
- ```
- brief ──► state list on the beat grid ──► one HTML film, every pixel = f(t) in seek(t)
- ──► one frame per beat, contact sheet, fix ──► Playwright: 4 subframes per frame
- ──► ffmpeg tmix (motion blur) ──► 60 fps H.264 + mix ──► storyboard + seam scan
- ```
- Because every frame is a pure function of time, renders are deterministic: seek to any
- moment and you get the same pixels, which is what makes per-beat QA and parallel rendering
- possible.
- ## v1 → v2
- | | v1 (legacy) | v2 |
- |---|---|---|
- | Timing | Locked to voiceover words | Locked to the music's measured beat grid |
- | Motion | GSAP timelines | Closed-form springs, pure `seek(t)` |
- | Renderer | HyperFrames | Playwright subframes + ffmpeg `tmix` motion blur |
- | Structure | Shots and transitions | One shape that never cuts |
- | Sound | Library SFX, levelled | Synthesized SFX placed by measured peak |
- | Depth | CSS camera rig | Camera springs + optional WebGL glass |
- v1 is still the better choice for a narrated explainer. It lives on in [`legacy/`](legacy/).
- ### Updating
- - **Installed v1 (before 13 October 2026)?** Run `npx skills update`. Your `product-launch-motion` skill is
- replaced by v2.
- - **Installed v2 on 13 or 14 October 2026?** It was briefly named `motion-launch-video`, so `update` can't
- find it. Reinstall once:
- ```bash
- npx skills remove motion-launch-video
- npx skills add AbubakrChan/product-launch-motion
- ```
- - **Want to keep v1 for narrated explainers?** Install it alongside v2:
- `npx skills add AbubakrChan/product-launch-motion/legacy`
- ## Made by
- Muhammad Abubakr, who builds [Cheerful](https://www.cheerful.ai). Made a film with this skill?
- Tag me on X and I'll share it.
- [](https://x.com/Muhamma77800831)
- [](https://www.linkedin.com/in/muhammad-abubakar-05173b20a/)
- ## License
- MIT for the skill and references — see [`LICENSE`](LICENSE).
- **The sample films do not travel.** They were made for Cheerful and are theirs; see
- [`NOTICE`](NOTICE) for that and for third-party credits (music, footage, fonts).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.