A tween that plays once, a scroll story that is actually a film, and a shader that fully appears in one browser are three different engineering problems. Generating the page did not solve any of them.
The last three repositories package API guidance, a media pipeline with a bill, and GPU effects laid over an interface that still has to work. They overlap earlier entries in this roundup. Choose the one that matches the failure in front of you.
-
GSAP Skills. Official agent guidance for the GSAP API: tweens, timelines, scroll-linked behavior, framework integration, and performance. The skills repository is MIT. That license is separate from the GSAP library’s own terms. The skills README says the library, including plugins that used to require a membership, is free for commercial use. Confirm that on GSAP’s terms before you depend on it.
-
Scroll World. A workflow for a cinematic landing page: generated scene stills, video clips joined at matching frames, and an engine that advances playback as someone scrolls. Scroll position controls time through that media. This is a playback pipeline, not a real-time interactive 3D world. Stills and video are both paid. The README’s own example, marked in the file as checked on 25 July 2026, puts the video portion of one six-scene 1080p chain at about $27 on Monid, the default video backend, before a mobile version and before the stills. The skill is written to state an estimate before spending.
-
Canvas UI. GPU effects drawn over live HTML, with framework wrappers and a documented fallback when the full effect is unavailable. Expect different results across browsers. Full HTML-in-canvas capture depends on experimental browser support; other browsers are given a simpler overlay, and the underlying page is meant to remain usable. The license is MIT plus a Commons Clause: use in your own product is allowed; selling, sublicensing, or redistributing the components themselves is not.
Keep motion when the interaction needs it and you can maintain the dependency. Budget a scroll film as production, not as a prompt. Add a GPU effect only on top of an interface that already works with a keyboard, on the devices you support, when the effect is missing.
Review starting point, not a release standard:
- Does it fit the user’s task and the product’s design system?
- Does it work across the required devices and browsers?
- Can people use it with a keyboard and reduced motion?
- Have you checked loading, empty, error, and long-content states?
- Have you reviewed performance, dependencies, and licensing?
These repositories can make coding agents more useful. They do not remove responsibility for design decisions, implementation quality, or verification.
The agent can generate the interface. Your team still owns whether it works.
Source: github.com/greensock/gsap-skills — README. github.com/oso95/scroll-world — README. github.com/DavidHDev/canvas-ui — README and LICENSE.md. Retrieved 23 October 2026.
#AgentSkills #ProductDesign #Frontend