What problem does it solve? Choosing the right WebGL shader approach for a frontend hero visual is error-prone: teams must pick a library, define a visual thesis, plan GPU fallbacks, and respect performance budgets. This Skill turns a short operator brief into a validated shader.json decision document covering all of those concerns. ## Core Features & Use Cases - Library Selection: Picks among Paper Shaders, OGL, react-three-fiber, Lygia, CSS Houdini paint worklets, or a zero-library CSS gradient fallback based on the brief. - Performance Budgeting: Emits fps targets, draw-call limits, low-end and no-WebGL fallback strategies, and prefers-reduced-motion handling. - Schema-Validated Output: Produces a shader.json (schema_version 1) consumed by the /li:frontend-design orchestrator or used directly in solo component mode. - Use Case: Given a brief like "hero background for an enterprise SaaS landing with a subtle mesh gradient", the Skill recommends @paper-design/shaders-react with a MeshGradient snippet, mobile downscale strategy, and CSS fallback. ## Quick Start Ask the agent to run the frontend-shader skill with a brief describing your desired hero visual, for example a subtle mesh-gradient background for a landing page, and review the generated shader.json.