Cinematic web motion
Skill twk0672005/sentence-to-site/skills/cinematic-web-motion
One sentence in, a verified website out. Agent skills that close the gap between vibe coding and software engineering - so people with no coding background can build a website that holds up.
npx -y skills add twk0672005/sentence-to-site --skill cinematic-web-motionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.6 KB, as published. Nobody here has run it
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.