| name | cinematic-web-motion |
| description | Use when a website task involves visual direction, existing-project discovery, animation, browser verification, or delivery and the smallest bounded route is not yet explicit. |
Cinematic Web Motion Router
Choose the smallest specialist skill that owns the decision. Do not load every module for a small CSS or copy correction. Do not create a review loop.
First read ../../references/routing-contract.md. Select one base route, one experience lane, and one delivery gate before loading specialists.
| If the task needs… | Start with… |
|---|
| one vague sentence turned into a whole finished site | one-sentence-website |
| a premise, hierarchy, visual critique, or anti-generic direction | visual-story-direction |
| an existing repo, unknown files, accepted baseline, or stack read | website-motion-intake |
| UI motion, scroll choreography, canvas, WebGL, or reduced motion | motion-choreography |
| screenshots, browser readback, console review, recording, or verdict | browser-evidence |
| a delivery note, release boundary, or another contributor to continue | delivery-handoff |
| an explicitly requested independent review | adversarial-quality-loop |
For a non-trivial website change, follow the selected contract: direction or intake → implementation/motion → route-specific evidence → handoff. Do not route to adversarial-quality-loop automatically, and never treat a build pass as browser evidence.
Read ../../docs/ARCHITECTURE.md before adding or changing a module.
