GSAP Timeline with Frame Checking
Author’s claim: Claude Opus 5.5 · not verified by us
Prompt the author shared
Build a GSAP timeline for UI cards with specific timing constraints: 280ms for cards, 220ms for title, 160ms for metadata, and a 60ms stagger between elements. Implement a verification loop where the animation is stepped through frame-by-frame using Playwright, screenshots are compared to detect overshoot or errors, and the code is patched until it passes the checks without rewriting everything.
As given in awesome-opus5-5-videos; we have not checked it against the post. Where it was shared ↗
What we know
- Model
- Claude Opus 5.5 (author’s claim)
- Posted
- Oct 8, 2026
- Made with
- Not known
- Source
- Listed in awesome-opus5-5-videos (opens in a new tab) by yihui-dev (MIT). The post was live on X on Nov 4, 2026.
Make one yourself: video Skills
These four are free. Checkout is not open yet: it opens once our payment provider finishes its review, and downloads open with it. Nothing is charged until then.
Every Screen Agent
An agent finishes a job on a laptop; the result shows up on a phone, then in a terminal, a chat and a code review. A 6.8-second light product shot.
See it in the catalog →Warp Liftoff
A blue spiral galaxy, a flash and a rocket climbing off a planet, then your headline and button. An 11-second dark launch teaser.
See it in the catalog →Paint Sweep Finale
A paint stroke wipes the frame, your wordmark is painted on letter by letter, and torn paper brings in the tagline. 8.6 seconds.
See it in the catalog →Dust Erase
A data-broker listing is scanned, crumbles into dust, and your payoff types on in blue. A 7-second privacy-product sting.
See it in the catalog →
