web-shader-extractor
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Use when a user gives or references a webpage URL and wants to extract, reproduce, port, or locally replay a WebGL, WebGPU, Canvas, shader-like, animated background, interactive 3D, or web visual effect. Locks the target rendering surface group, records shader/resource/render graph/timing/input evidence, builds an evidence-matched local baseline, then projectizes it. Do not use for ordinary DOM/CSS page cloning.
5 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- lixiaolin94/skillsedited, first seen Nov 2, 2026
- benmix/skillsedited, first seen Oct 13, 2026
- choupiyang/ZAI_SKILLStheir own version, first seen Apr 20, 2026
- twomathematicians-code/AgentForgetheir own version, first seen Apr 16, 2026
- SuperInstance/flux-fleet-scannertheir own version, first seen Apr 14, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- lixiaolin94/skills★ 77090% same
- benmix/skills★ 190% same
Wrote their own version · 3
- choupiyang/ZAI_SKILLS★ 13same name
- SuperInstance/flux-fleet-scanner★ 1same name
- twomathematicians-code/AgentForge★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- biz-html-vizSkill
- gzh-designSkill
- produce-cinematic-videoSkill
- viz-chartsSkill
- viz-deckSkill
- zima-designSkill
- zima-html-pptSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Start from the target visual.
- Distinctive: line 25
Keep large evidence, captures, and generated outputs out of the conversation.
- Distinctive: line 35
Do not use this for ordinary DOM/CSS cloning, static screenshots, generic website copying, unrelated JavaScript deobfuscation, or product …
- Distinctive: line 36
Use it only when the task has a shader/canvas target.
- Distinctive: line 44
No compensation tuning: do not adjust brightness, time, color, offsets, or noise to mask missing pipeline evidence.
- Distinctive: line 46
Ask only for product scope changes or external access/permission blockers.
- Distinctive: line 47
Use plain records: state the fact, evidence path, current unknown, and next action.
- Distinctive: line 51
Use the Recon Kernel state flow:
- Very specific: line 68
Before lock, only narrow source probes tied to nextProbe are allowed.
- Very specific: line 102
Use scripts/fetch-rendered-dom.mjs only as an optional inventory helper when Playwright is already available.
- Very specific: line 103
Use scripts/scan-bundle.sh only on target-bound bundle slices or a precise nextProbe.
- Distinctive: line 106
Use bundled templates as schemas, not free-form notes:
- Very specific: line 123
If no adapter fits, follow generic WebGL, WebGPU, or Canvas2D capture in references/capture-backends.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Web Shader Extractor
Index for WebGL / WebGPU / Canvas rendering investigation and local replay. Start from the target visual. Lock the surface group. Trace source or runtime facts. Build a runnable baseline. Then projectize.
Router Contract
This file is the index. Do not treat it as the full operating manual. Before task action, read:
references/operating-contract.mdreferences/recon-kernel.md
Then load only the focused references needed by the current state. Keep large evidence, captures, and generated outputs out of the conversation. Store them in the user's output directory.
Use This For
- Extracting a webpage WebGL, WebGPU, Canvas2D, OffscreenCanvas, shader, or animated canvas effect.
- Replaying an animated background, product shader, interactive WebGL scene, or Canvas visual locally.
- Building an evidence-matched baseline first, then an editable project.
- Investigating target-bound shader/render graph/timing/resource/input facts.
Do not use this for ordinary DOM/CSS cloning, static screenshots, generic website copying, unrelated JavaScript deobfuscation, or product UI redesign. Use it only when the task has a shader/canvas target.
Core Rules
- Target-bound before framework-bound: a global Three.js, platform, or shader signature is only a hypothesis until tied to the target surface group.
- Evidence before implementation: source, runtime objects, frame captures, source maps, and public structured definitions outrank visual fitting.
- Baseline before projectization: never overwrite a verified baseline for cleanup, simplification, or native conversion.
- Honest labels: implementation-critical facts are
SOURCE,PARTIAL, orGUESS; unlabeled values are treated asGUESS. - No compensation tuning: do not adjust brightness, time, color, offsets, or noise to mask missing pipeline evidence.
- Gate artifacts are transition guards: if the required artifact is missing, incomplete, or has placeholders in gate-critical fields, the state has not advanced.
- Ask only for product scope changes or external access/permission blockers.
- Use plain records: state the fact, evidence path, current unknown, and next action. Avoid metaphor, broad claims, and unsupported conclusions.
State Router
Use the Recon Kernel state flow:
INTAKE -> CAPABILITY_SNAPSHOT -> QUICK_SCOUT -> SURFACE_ATTRIBUTION
-> TARGET_LOCK_GATE
- provisional/failed -> REFINE_SCOUT
- attributed -> targeted owner/backend/source probe -> TARGET_LOCK_GATE
- locked -> SCOPE_CHECK
-> TRACE_ROUTE_SELECT -> SOURCE_TRACE -> CAPTURE_MINIMUM_TRUTH
-> REPLAY_READY_GATE
- not ready -> SOURCE_TRACE / CAPTURE_MINIMUM_TRUTH
- ready -> RAW_REPLAY
-> BASELINE_RUN -> BASELINE_VERIFY
-> BASELINE_VERIFIED -> PROJECTIZE -> PROJECT_VERIFY -> PACKAGETARGET_LOCKED must precede deep source/bundle work.
Before lock, only narrow source probes tied to nextProbe are allowed.
REPLAY_READY must precede implementation.
BASELINE_VERIFIED must precede projectization.
Reference Router
Load only what the current state needs:
| Need | Read |
| Global contract, fact labels, completion states | references/operating-contract.md |
| Kernel, initial protocol, state flow, autonomy, budgets | references/recon-kernel.md |
| Surface discovery and visual attribution | references/surface-discovery.md |
| Lock criteria, target-bound evidence, scope, Three.js binding | references/target-lock.md |
| Evidence labels, ledgers, unknown classes, sensitive data | references/evidence-policy.md |
| Tool capability selection | references/tool-capability-matrix.md |
| WebGL, WebGPU, and Canvas2D capture facts | references/capture-backends.md |
| Source maps, bundle slices, config, encoded definitions | references/source-analysis.md |
| Replay readiness, routes, baseline, stack choice, projectization | references/replay-policy.md |
| QA, failure routing, severity, mismatch signatures | references/qa-failure-policy.md |
| Three.js shader injection or TSL reconstruction | references/three-shader-reconstruction.md |
| Unicorn Studio target | references/unicorn-studio.md |
| shaders.com / TSL target | references/shaders-com.md |
Tool And Artifact Policy
Tools are replaceable capabilities, not prerequisites. First record the available capability profile:
navigate, runtime-eval, preload-script, network-metadata, network-body,
source-map, canvas-screenshot, interaction, frame-capture-webgl,
frame-capture-webgpu, local-run, multi-frame-compareUse scripts/fetch-rendered-dom.mjs only as an optional inventory helper when Playwright is already available.
Use scripts/scan-bundle.sh only on target-bound bundle slices or a precise nextProbe.
Script output is hypothesis evidence. It never satisfies Surface Attribution, Target Lock, Replay Ready, or QA gates by itself.
Use bundled templates as schemas, not free-form notes:
templates/scout-card.jsontemplates/replay-manifest.jsontemplates/run-state.jsontemplates/qa-report.mdtemplates/known-gaps.mdtemplates/extraction-report.md
Platform Adapters
Load platform references only after target-bound evidence points there:
- Unicorn Studio:
references/unicorn-studio.md - shaders.com / TSL:
references/shaders-com.md - Three.js shader injection or TSL:
references/three-shader-reconstruction.md
If no adapter fits, follow generic WebGL, WebGPU, or Canvas2D capture in references/capture-backends.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

