GLSL shader programming — holographic effects, TDD workflow
GLSL shader expertise — TDD-first workflow with visual regression tests, GPU performance patterns (branchless math, texture atlases, LOD, precision tuning), safety rules (constant loop bounds, zero-division guards), and holographic/effect shader recipes
- What
- GLSL shader expertise — TDD-first workflow with visual regression tests, GPU performance patterns (branchless math, texture atlases, LOD, precision tuning), safety rules (constant loop bounds, zero-division guards), and holographic/effect shader recipes
- Cost
- Free
- Needs
- a WebGL/GLSL project the agent can read and work on (browser, Three.js, or similar) — the skill is shader methodology, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @martinholovsky's GLSL shader-programming skill: GPU-side expertise for holographic visual effects (the JARVIS HUD theme is framing — the techniques are generic). A TDD-first implementation workflow: write failing tests first (shader compilation, uniform accessibility, visual regression against baselines, UV edge cases), implement the minimum to pass, then refactor to the full shader and run the full verification suite (`test:shaders`, `test:visual`, `bench:shaders`, cross-browser WebGL compat). Performance patterns with ❌/✅ pairs: branchless math (mix/step over if/else), texture atlases to cut draw calls, distance-based LOD for noise octaves, uniform batching into vectors/matrices, precision matching to data needs, caching texture lookups. Safety standards: constant loop bounds always (dynamic bounds can hang the GPU), guard every division, limit texture sizes. Includes ready recipes (holographic panel with scanlines, energy field, data-visualization bars) and a pre-commit checklist. Honest caveats: methodology only — the agent needs a WebGL/GLSL project to apply it to; the author declares risk level LOW (GPU code has limited attack surface but can freeze the system if careless). Unlicense (public-domain dedication). Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a WebGL/GLSL project the agent can read and work on (browser, Three.js, or similar) — the skill is shader methodology, not software to install Install "GLSL shader programming — holographic effects, TDD workflow" for me. It gives my agent @martinholovsky's GLSL workflow: TDD-first implementation (write failing tests — shader compilation, uniform accessibility, visual regression, UV edge cases — then implement, then refactor and run the full verification suite), GPU performance patterns (branchless mix/step math, texture atlases, distance-based LOD, uniform batching, precision tuning, cached texture lookups), safety rules (constant loop bounds always, guard every division, limit texture sizes), ready shader recipes (holographic panel with scanlines, energy field, data-visualization bars), and a pre-commit checklist — with advanced patterns in references/advanced-patterns.md. Unlicensed (public domain). Repository: https://github.com/martinholovsky/claude-skills-generator/blob/main/skills/glsl/SKILL.md 1. Fetch the SKILL.md file (and the references/ folder) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "glsl". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my WebGL/GLSL project or shader files; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.