What problem does it solve?
Trying to deliver cinematic, high-performance UI moments without clear direction often results in effects that feel out of place or janky. Overdrive prevents misfires by mandating context gathering, progressive direction proposals, and AskUserQuestion confirmations before any technically ambitious engineering begins so the result aligns with what the project really needs. It also demands iteration with browser automation to ensure the "extraordinary" feeling actually holds up across real devices.
Core Features & Use Cases
- Context-first entry: Invoke /frontend-design (and /teach-impeccable if no context exists) before coding, so you understand the brand personality, technical constraints, and what would genuinely wow these users.
- Directional proposals & confirmation: Think through 2-3 radically different techniques—shader-driven hero, View Transitions morph, streaming validation form—describe each with trade-offs, and pause for the AskUserQuestion response before writing code.
- High-velocity validation: Use browser automation tools to preview, verify, and refine each iteration, respecting prefers-reduced-motion, progressive enhancement, and fallback experiences so advanced animations never compromise usability.
Quick Start
Ask overdrive to run /frontend-design, gather project context, describe several extraordinary directions with trade-offs, confirm via AskUserQuestion, and then execute the user-approved option.