DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a WebGL glass pass to a launch film with Product Launch Motion

Render a second version of a launch film with refractive 3D glass shapes floating through each scene.

  • Content
  • Advanced
  • 150 minutes
  • From the README
  • Claude Code

Who it is forA product marketer who already has a launch film and wants a more striking variant for a second channel.

The problemA standard launch film can look flat next to other launch videos, and adding depth by hand takes a motion designer.

The outcomeA glass variant of the same film, with refractive 3D shapes moving through every scene, alongside the standard cut.

What you need first

  • Claude Code with Claude Opus 5.5 selected
  • Node 20 or newer with Playwright
  • FFmpeg installed and on the PATH
  • Python 3 with numpy
  • Optional: a royalty-free song of about 120 BPM with a licence that allows your use

Steps

  1. Install the skill with npx skills add AbubakrChan/product-launch-motion if it is not already installed.
  2. Build the standard launch film first by asking Claude Code for a launch video of your site.
  3. Ask Claude Code in the same session to add the optional WebGL glass pass to the film.
  4. Review the glass version with sound on and reply with notes on the shapes and timing.
  5. Export both the standard and glass MP4 files for your channels.

Prompt for your agent

In the repo AbubakrChan/product-launch-motion, add the optional WebGL glass pass to the launch film for <target website URL>. Expect a second 60 fps MP4 with refractive 3D shapes through every scene. Verify both films have the same length and the glass version keeps the beat-synced sound.

Caveat. The README only says the glass pass is optional and shows it as a bonus on the sample film, so check the glass render's quality on your own footage before you publish it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page