What problem does it solve? Standard web interfaces often feel flat and conventional, and developers struggle to know which advanced browser techniques (shaders, spring physics, virtual scrolling, scroll-driven reveals) are appropriate for a given context without breaking performance or accessibility. ## Core Features & Use Cases - Context-Aware Ambition: Assesses whether a surface is visual/marketing, functional UI, performance-critical, or data-heavy before choosing a technique, so effects match the product's personality. - Technique Toolkit: Covers View Transitions, scroll-driven animations, WebGL/WebGPU, virtual scrolling, spring physics, Web Workers, OffscreenCanvas, and WASM, organized by the experience goal rather than technology name. - Disciplined Implementation: Enforces progressive enhancement, prefers-reduced-motion support, 60fps performance targets, and mandatory browser-based visual iteration. - Use Case: A developer wants a data table rendering 100k rows to feel fluid. The skill proposes virtual scrolling plus animated state transitions, verifies the result in a browser, and ensures a static fallback exists. ## Quick Start Ask the AI to push a specific feature into overdrive, for example: take the orders table into overdrive so it handles thousands of rows with smooth animated transitions.