motionsite
Skill1 starsChanged 10 days agoMITView on GitHub
Build an animated, video-driven landing page or hero section - full-bleed looping video background with a gradient overlay, glass cards, animated headline and call-to-action buttons, scroll reveals - that stays fast and accessible (poster image, lazy video, reduced-motion and mobile fallbacks). Includes a site template, ffmpeg asset script and a motion audit script. Use proactively when asked for an animated website, motion site, cinematic landing page, video hero, or to make a page feel alive.
In this repository8 other files it gives its agents.
- skills/zero-trust-review/references/agents.mdAGENTS.md
- api-security-guardSkill
- app-readiness-auditSkill
- build-flow-mapSkill
- monitor-alerts-builderSkill
- session-journalSkill
- skeletonizerSkill
- zero-trust-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Not affiliated with motionsites.ai.
- Distinctive: line 12
Runs on its own: when you ask for a landing page, hero or animated site, Claude picks this skill, builds from the template and runs the …
- Distinctive: line 19
Build the page from the template: Keep these parts: hero (video + overlay + headline + CTA), a glass navigation bar, 3 to 6 content …
- Very specific: line 21
Audit: Run python3 <skill-dir>/scripts/check_motion.py <site-folder> and fix every FAIL.
- Very specific: line 29
Animate only
transformandopacity: Never animate top, left, width, height or margin. - Distinctive: line 30
Text stays readable over video: Put a gradient overlay between video and text, keep body text at least 4.5:1 contrast against the darkest …
- Very specific: line 34
Own your assets: No third-party CDN video, fonts self-hosted or from a font provider, licenses recorded in assets/README.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Motionsite
Builds the "motion site" look: a full-screen looping video hero, a dark gradient overlay for readable text, glass-effect cards, words that animate in, buttons that react, and sections that reveal on scroll. The difference between a good one and a slow, inaccessible one is the checklist below, so this skill builds the page and then audits it.
Not affiliated with motionsites.ai. This skill contains no third-party prompts or assets.
Runs on its own: when you ask for a landing page, hero or animated site, Claude picks this skill, builds from the template and runs the audit before it reports back.
Procedure
- Get the brief in one pass. Brand name, one-line promise, main call to action, 3 to 6 sections (features, proof, pricing, FAQ), tone (calm, bold, playful, luxury), and any logo, colors or fonts they already own. If the user gave none, choose a direction yourself and say which one.
- Pick the stack from the project. Existing React/Next/Vue/Svelte project: build components in that stack. Empty folder with no preference: use the single-file
templates/site.html(no build step, opens by double-click). If they ask for React, Vite, TypeScript and Tailwind, usetemplates/Hero.tsxandtemplates/useReveal.ts. - Get the video honest and light. See
references/assets.md. Use the user's own footage or a generated or licensed clip, never hotlink someone else's CDN. Until real footage exists, ship the CSS animated gradient background the template includes so the page already looks finished. Real footage is switched on by filling three data attributes on.hero-media(data-video-mp4,data-video-webm,data-poster). Make web versions withscripts/make_video_assets.sh(mp4 + webm + poster). - Build the page from the template. Keep these parts: hero (video + overlay + headline + CTA), a glass navigation bar, 3 to 6 content sections with reveal animations, footer. Apply the design recipes in
references/design-recipes.md(type scale, spacing, palette, glass cards, button states, timing). - Wire the performance and accessibility rules (below). They are not optional extras; they are what makes the page usable on a phone.
- Audit. Run
python3 <skill-dir>/scripts/check_motion.py <site-folder>and fix every FAIL. Then look at it in a browser: desktop and phone width, reduced motion on, JavaScript disabled for the first paint. Details inreferences/performance-accessibility.md. - Report the files made, how to replace the placeholder video, what the audit said, and one thing to look at.
Rules that decide quality
- Video:
muted,loop,playsinline(without these mobile browsers refuse to play it in the page),posterset,preload="metadata", no audio track. Start playback from script after checking reduced motion and data saver, as the template does, so those visitors never download the video. Target 2 to 4 MB for the hero clip, 1080p at most, 6 to 12 seconds that loop cleanly. - Poster is the first paint. The poster image (or the gradient) is what the visitor sees and what Largest Contentful Paint measures. Give it
fetchpriority="high"and exact dimensions. - Respect the visitor. Under
prefers-reduced-motion: reduce, or when data saver is on, show the poster instead of playing video and turn off animations. Pause the video when it is scrolled off screen. - Animate only
transformandopacity. Never animatetop,left,width,heightormargin; they force layout and jank on phones. - Text stays readable over video. Put a gradient overlay between video and text, keep body text at least 4.5:1 contrast against the darkest and lightest frame, and never put small text directly on moving footage.
- One idea per section, one motion per element. Stagger within 60 to 100 ms steps, durations 400 to 800 ms, ease-out. If everything moves, nothing leads the eye.
- Mobile first. Hero uses
100svh, not100vh. Test at 375 px width; no horizontal scroll. Consider a lighter or still hero on small screens. - Real content structure. One
h1, landmarks (header,main,footer), buttons are<button>or<a>, links have text, images havealt. - Own your assets. No third-party CDN video, fonts self-hosted or from a font provider, licenses recorded in
assets/README.md.
Files
| File | Purpose |
templates/site.html | Complete one-file landing page: video hero (switched on with data attributes) with CSS gradient fallback, glass nav, animated headline, reveal-on-scroll, cards, CTA, footer |
templates/Hero.tsx, templates/useReveal.ts | React versions of the hero and the scroll-reveal hook |
references/design-recipes.md | Type, color, spacing, glass, buttons, motion timing, section patterns |
references/performance-accessibility.md | Budgets, reduced motion, video behavior, testing steps |
references/assets.md | Where video comes from, licensing, generating a clip, encoding |
scripts/make_video_assets.sh | ffmpeg: input clip to web mp4, webm, poster |
scripts/check_motion.py | Audit a site folder for the problems above |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

