webgl-halftone-drift

Generate a cursor-reactive WebGL2 hero animation with a rotated halftone dot grid aesthetic.

93.2k|10.8k|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/nexu-io/open-design --skill webgl-halftone-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webgl-halftone-drift
Source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/examples/webgl-halftone-drift
Command: npx skills add https://github.com/nexu-io/open-design --skill webgl-halftone-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of creating high-performance, visually engaging hero sections that require GPU-accelerated graphics without the overhead of heavy external frameworks or complex build pipelines.

Core Features & Use Cases

  • GPU-Accelerated Rendering: Utilizes WebGL2 for high-performance, real-time flow field animations.
  • Generative Aesthetics: Implements a custom shader-based halftone screen with duotone color mapping.
  • Interactive Design: Provides a cursor-reactive drift effect that responds to user input for immersive web experiences.

Quick Start

Generate a new webgl-halftone-drift hero component for the current design project.

Frequently Asked Questions about webgl-halftone-drift

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

FAQPage Schema
How do I implement a WebGL2 hero animation?

Use the webgl-halftone-drift skill to generate a self-contained HTML file containing the necessary vertex and fragment shaders. The skill handles the canvas initialization and render loop automatically.

Can I customize the halftone dot pattern?

Yes, you can modify the fragment shader code within the generated index.html file. Adjust the 'cells' variable or the rotation matrix to change the density and orientation of the halftone grid.

Does this animation work on mobile devices?

The animation is designed for modern browsers supporting WebGL2. Performance depends on the device's GPU capabilities, and the code includes a fallback check to ensure graceful handling if WebGL2 is unavailable.

What are the limitations of this shader-based approach?

This approach relies entirely on GPU fragment shaders, meaning it does not use traditional DOM elements or meshes. It is best suited for abstract, generative visuals rather than complex 3D models.