What problem does it solve? Writing Vawe scenes by hand often produces broken renders: impure frame logic that breaks sharded rendering, generic AI-looking layouts, spacing collisions, and missing theme tokens. This Skill encodes the full authoring contract so scenes render deterministically and look intentional. ## Core Features & Use Cases - Purity contract enforcement: Teaches the renderFrame(n) purity rule (no Date.now, no Math.random, compositor-only properties) guarded by make probe, so frames shard safely across parallel Chrome tabs. - Design system guidance: Covers theme-owned look tokens, per-film design specs, group-first layout containment, motion primitives (interpolate, spring, track), and anti-generic taste rules for hooks, CTAs, and cards. - QA loop: Provides the validation ladder (probe, audit, look, verify, review) with rendered-frame inspection before declaring a scene done. - Use Case: You need a 9:16 product teaser video. Use this Skill to write the data JSON with a declared theme, lay out layers in groups, animate with pure motion primitives, then run make audit and eyeball the storyboard before rendering. ## Quick Start Use the vawe-scene-authoring skill to create a new scene JSON and scene.html for a short product teaser video, then run the purity probe and layout audit.
