What problem does it solve? Authoring a product demo video that honestly proves one mechanism works is hard: cursors that click nothing, or UI changes on independent timers, read as fake. This Skill provides the playbook for structuring a demo scene in the Vawe engine so the cursor path, the click, and its visible consequence are causally linked. ## Core Features & Use Cases - Length-adaptive spine: switches between a single continuous action (under ~15s) and a hook-demo-payoff-close beat spine (15s and longer) via make scaffold TYPE=demo DUR=<n>. - Real cursor and click causality: uses a cursor layer with path keyframes and clicks times, requiring any consequence (chip, state flip) to start at or just after the click. - Motion and asset guidance: recommends motion blocks per role (kineticHook, verdictProof, ctaEnd), zoom via ken or cameraMove, and real captured UI via make capture. - Use Case: An agent asked to prove an export button works scaffolds a 10s scene where a cursor follows a real path onto the button, fires a click ripple, and an "Exported." chip appears only after the click. ## Quick Start Ask the agent to scaffold a Vawe demo scene proving one UI mechanism, for example by running make scaffold TYPE=demo DUR=10 and composing a cursor layer whose click triggers a visible consequence.
