overdrive

Guides ambitious interface enhancements with cinematic transitions and dynamic interactions.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Lin-0096/welove --skill overdrive-lin-0096
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overdrive
Source: https://github.com/Lin-0096/welove/tree/main/.claude/skills/overdrive
Command: npx skills add https://github.com/Lin-0096/welove --skill overdrive-lin-0096

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.

Core Features & Use Cases

  • Proposes 2-3 directions and requires user confirmation before proceeding.
  • Iterates with browser automation to preview, verify, and refine results.
  • Emphasizes context-driven decisions to ensure alignment with brand and goals.

Quick Start

Ask the user to pick one of the proposed directions and begin implementing the chosen approach.

Frequently Asked Questions about overdrive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create cinematic UI transitions and 60fps web animations?

Cinematic UI transitions and 60fps web animations are achieved by applying shaders, spring physics, and scroll-driven reveals. The implementation proposes multiple directions, requires user confirmation, and iterates via browser automation to verify performance.

What is the best way to implement scroll-driven reveals with spring physics?

Implementing scroll-driven reveals with spring physics requires proposing 2-3 initial directions for user confirmation. The chosen approach is then iterated with browser automation to preview, verify, and refine the dynamic interactions safely.

Do I need browser automation to validate high-performance shader effects?

Browser automation is required to validate high-performance shader effects. It iterates within the browser to preview, verify, and refine results, ensuring ambitious web animations perform safely and effectively across devices and viewports.

Can I use this approach for web applications requiring dynamic interactions across different viewports?

This approach applies to web applications requiring dynamic interactions across devices and viewports. It emphasizes context-driven decisions to ensure alignment with brand and goals while delivering extraordinarily responsive interfaces.

Why does implementing complex UI effects require upfront preparation and directional proposals?

Complex UI effects require upfront preparation and directional proposals to ensure safe, effective implementations. Proposing 2-3 directions before proceeding aligns technically ambitious shaders and animations with the user's specific context and goals.