scroll-video-website

Scroll Video Website

When to use

Use this skill when the user wants to:

• build an Apple-style scroll animation from a video;
• create a scroll-controlled or scroll-scrubbed video website;
• turn a product video into a cinematic landing page;
• build a scrollytelling experience driven by video;
• convert video into an optimized image sequence for scroll animation;
• create a Canvas-based product reveal controlled by scrolling;
• optimize an existing generated scroll-video frame sequence.

Do not use it for ordinary autoplay video backgrounds or unrelated scroll effects.

Create a minimal full-page experience like a product animation viewer: the page itself supplies scroll distance while a fixed canvas fills the viewport and scrubs a frame sequence derived from the user's video. The animation is the interface, not a background behind a conventional landing page.

Invocation

This skill has two modes: build a scroll-video website from a video, or optimize an existing frame sequence. If the first argument is optimize, follow references/optimize.md and do not run the build workflow below.

Treat this concise form as a complete build request:

$scroll-video-website <path/to/video.mp4>

The video path must be the first argument after the skill name. Everything after the path is optional user direction for styling, layout, copy, or behavior:

$scroll-video-website ./media/product-reveal.mp4
$scroll-video-website ./media/product-reveal.mp4 use a black background and condensed typography

The first example means: derive the frame sequence and build the full default scroll-animation website described below. In the second, preserve the same video-driven animation architecture while following the added visual direction. Let the agent using this skill interpret and implement the rest of the prompt; this skill does not define a separate command grammar for style options.

Interpret the video path as relative to the current working directory unless it is absolute. If it contains spaces, the user should quote it. Check the exact path first. If a bare filename is not there, search the current project for an exact filename match while excluding dependency, build, cache, and VCS directories. Continue automatically when exactly one match exists. If there are no matches or multiple matches, ask the user for the precise path. Braces in <path/to/video.mp4> or {video_path} indicate a placeholder and are not part of the actual path. Do not require or interpret a use keyword.