overdrive

Implements technically ambitious interface effects using shaders, spring physics, and scroll-driven animations.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill overdrive-joaopaulotr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overdrive
Source: https://github.com/joaopaulotr/PesquiseMaisHealth/tree/main/.agents/skills/overdrive
Command: npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill overdrive-joaopaulotr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard web interfaces often feel flat and conventional. This Skill pushes interfaces past conventional limits by applying advanced browser capabilities — WebGL shaders, spring physics, View Transitions, scroll-driven animations, and GPU-accelerated rendering — so that pages, forms, tables, and dashboards feel extraordinary rather than ordinary. ## Core Features & Use Cases - Cinematic Transitions: Uses the View Transitions API, @starting-style, and spring physics to make dialogs, page changes, and state shifts feel physical and fluid. - Advanced Rendering: Applies WebGL/WebGPU shaders, Canvas 2D, OffscreenCanvas, and SVG filter chains for effects CSS alone cannot express. - High-Performance Data UI: Implements virtual scrolling, GPU-accelerated charts, Web Workers, and WASM so large datasets render at 60fps without jank. - Use Case: A developer wants a landing page hero with a scroll-driven shader reveal, or a data table that renders 100k rows smoothly — the Skill proposes 2-3 directions, confirms one with the user, then iterates with browser automation until the result looks right. ## Quick Start Ask the AI to use the overdrive skill to make a specific interface element feel extraordinary, such as adding a scroll-driven reveal and spring-physics transitions to your landing page hero section.

Frequently Asked Questions about overdrive

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

FAQPage Schema
How do I add scroll-driven animations to a web page?

Use the CSS scroll-driven animations API with animation-timeline: scroll() to tie parallax, progress bars, and reveal sequences to scroll position without JavaScript. It works in Chrome, Edge, and Safari; provide a static fallback for Firefox where support is flag-only.

What is the View Transitions API used for?

The View Transitions API enables shared element morphing between UI states, such as a button morphing into a dialog or a list item expanding into a detail page. Same-document transitions work in all browsers; cross-document transitions are unsupported in Firefox.

WebGL vs WebGPU for shader effects on websites?

WebGL works in all browsers and suits shader effects, post-processing, and particle systems via libraries like Three.js or OGL. WebGPU offers more GPU compute power but only ships in Chrome and Edge, so always provide a WebGL2 fallback.

How do I render 100k rows in a table without lag?

Use virtual scrolling to render only visible rows, which keeps large tables at 60fps. Simple cases need no library; complex ones can use TanStack Virtual. For heavy computation, move work to Web Workers or WASM.

Does scroll-driven animation support reduced motion preferences?

Yes, respecting prefers-reduced-motion is mandatory for accessibility. Always provide a beautiful static alternative when reduced motion is enabled, and gate enhanced effects behind @supports queries or feature detection.

When should I not use advanced animation effects?

Avoid them when they cause jank on mid-range devices, when they mask weak design fundamentals, or when multiple competing effects create noise. Context matters: a particle system suits a creative portfolio but not a settings page.