overdrive

Implement GPU-driven animations and physics-backed interactions with progressive enhancement.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/OmOc3/physica --skill overdrive-omoc3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overdrive
Source: https://github.com/OmOc3/physica/tree/main/.codex/skills/overdrive
Command: npx skills add https://github.com/OmOc3/physica --skill overdrive-omoc3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams push UI beyond ordinary interactions by designing and implementing technically ambitious, high-performance visual and motion treatments that create genuine "wow" moments without sacrificing accessibility or performance.

Core Features & Use Cases

  • Cinematic transitions: Shared-element morphs and View Transitions to make navigation feel native.
  • GPU & shader effects: WebGL/WebGPU and shader-driven backgrounds or particle systems for immersive visuals.
  • Performance-first patterns: Virtual scrolling, OffscreenCanvas, Web Workers, WASM fallbacks, and lazy initialization for large datasets or heavy rendering.
  • Use Case: Transform a product listing into a cinematic browsing experience with scroll-driven reveals, GPU-accelerated charts, and a morphing detail dialog that preserves 60fps and respects prefers-reduced-motion.

Quick Start

Use the overdrive skill to propose 2-3 ambitious visual directions for a target UI component, explain trade-offs, and then implement the confirmed direction with progressive enhancement and performance safeguards.

Frequently Asked Questions about overdrive

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

FAQPage Schema
How do I add cinematic transitions and GPU-driven visuals to my web UI without dropping below 60fps?

To add cinematic transitions while maintaining 60fps, you can apply GPU-driven visuals, physics-backed interactions, and View Transitions. Use lazy initialization for heavy resources and verify performance iteratively in the browser to ensure smooth rendering.

What is the best way to implement virtual scrolling for data-heavy visualizations?

The best way to implement virtual scrolling for data-heavy visualizations involves combining OffscreenCanvas, Web Workers, and WASM fallbacks. This performance-first pattern ensures large datasets render fluidly without blocking the main thread.

Do I need WebGPU to create shader-driven backgrounds, or can I use WebGL?

You do not strictly need WebGPU, as the approach supports both WebGL and WebGPU for shader-driven backgrounds and particle systems. It includes progressive enhancement and graceful fallbacks to ensure compatibility across different browser API support levels.

Can I build scroll-driven animations that respect prefers-reduced-motion?

Yes, you can build scroll-driven choreography and physics-backed interactions that strictly comply with prefers-reduced-motion. The implementation ensures accessibility by providing graceful fallbacks for users who disable motion effects.

Why does my heavy animation UI lag on large datasets, and how can I optimize it?

Heavy animation UIs lag when rendering large datasets without offloading work. You can optimize by using virtual scrolling, OffscreenCanvas, Web Workers, and lazy initialization of heavy resources to keep visual rendering at 60fps.