Shader Programming is a cross-engine skill for the technique behind GPU effects: tint, scrolling UVs, dissolve with an edge glow, fresnel rim light, outline, vignette and grading. Snippets are GLSL with HLSL forms alongside, and the engine skills supply syntax and material wiring.
The agent names the shader stage, works in one coordinate space, compiles each file with glslangValidator, checks the parameter endpoints numerically and asks you to look on the target device.
What You Get
- Worked GLSL snippets for tinting, frame-rate independent UV scrolling, dissolve with a glowing edge and fresnel rim light
- A GLSL to HLSL mapping reference, with clip-space and matrix-order notes
- Longer 2D outline, vignette and colour grading shaders in a reference file
- A compile step with glslangValidator, plus an ES 3.00 variant for web targets
- Endpoint checks, such as dissolve at 0 showing no edge colour
- A gotchas list on precision, flipped V, reversed smoothstep and discard cost
Common Use Cases
- Designing or debugging the maths of a dissolve, outline or rim effect
- Porting a shader between GLSL and HLSL or between engines
- Chasing specks, banding or shimmer that shows only on mobile GPUs
- Checking a shader compiles before opening the editor
What Makes It Unique
It teaches the technique once and leaves each engine’s syntax to that engine’s skill. The patterns carry the fixes for real bugs, such as dissolve specks at amount 0, and the skill states which GLSL variants compile under which version header. It also notes renderer limits like three.js WebGPURenderer running only node materials.
Under The Hood
The skill is a SKILL.md with one reference file of longer effects and port notes. The agent writes shader files in your project and runs glslangValidator on them from the command line, and naga for WGSL or the Godot headless check where the engine skill gives one. It may render a test quad in the engine to read pixels back. It does not fetch web pages or call outside services.