video-scrub-deck
Skill4 starsChanged 3 months agoMITView on GitHub
Build or repair a guided or free-scroll video-scrub website deck with scrub-ready media, approved pause points, transitions, navigation, mobile behavior, and reverse-scroll QA.
In this repository26 other files it gives its agents.
- aigentSkill
- aigent-3d-scroll-systemSkill
- aigent-asset-gallery-systemSkill
- aigent-business-sitesSkill
- aigent-designSkill
- aigent-landing-page-polishSkill
- asset-provenance-auditSkill
- cinematic-asset-gallerySkill
- cinematic-site-qaSkill
- cinematic-studioSkill
- cinematic-web-directorSkill
- creative-asset-directorSkill
- design-forensicsSkill
- design-resolverSkill
- gsap-scroll-choreographySkill
- hyperframes-videoSkill
- inspiration-originality-auditSkill
- modular-scroll-pageSkill
- publish-siteSkill
- reference-synthesisSkill
- remotion-web-assetsSkill
- spline-web-sceneSkill
- threejs-web-sceneSkill
- video-asset-pipelineSkill
- visual-design-criticSkill
- web-3d-asset-pipelineSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use free scroll when exploration is part of the page.
- Distinctive: line 18
Use guided Next and Previous controls when the sequence should feel presented and exact states matter.
- Distinctive: line 45
Do not patch one visible slide while sibling states share the same broken timeline function.
≈ “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
Video Scrub Deck
Read:
docs/cinematic-scroll-deck-playbook.mdrecipes/video-scrub-deck/README.mdskills/video-asset-pipeline/SKILL.md
Decide the interaction
Use free scroll when exploration is part of the page.
Use guided Next and Previous controls when the sequence should feel presented and exact states matter.
Production contract
- short clips
- frequent-keyframe or all-intra test exports
- approved pause points
- one source of truth for copy
- poster and reduced-motion state
- first clip warmed on intent
- later clips warmed near use
- byte-range delivery
State rules
- the hero CTA targets the deck boundary
- opening copy is visible at the first approved state
- transitions read as transitions, not accidental flashes
- active media and copy remain synchronized
- reverse navigation restores prior states
- sticky evidence moves only after its source state
- generic scroll cues disappear when guided controls take over
Verify
Inspect video currentTime, forward and reverse travel, first load, mobile fitting, failed media, reduced motion, and every guided pause point.
Do not patch one visible slide while sibling states share the same broken timeline function. Fix the shared state mapping.
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.