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.
- Probes must discriminate: before running a probe, state which live hypotheses it separates and what each outcome eliminates. Evidence consistent with every candidate is weak; evidence only one candidate predicts is strong.
- Evidence before implementation: source, runtime objects, frame captures, source maps, and public structured definitions outrank visual fitting.
- No fabricated numbers: confidence is expressed with hypothesis status and
SOURCE/PARTIAL/GUESS, never invented probabilities or scores.
- Baseline before projectization: never overwrite a verified baseline for cleanup, simplification, or native conversion.
- Honest labels: implementation-critical facts are
SOURCE, PARTIAL, or GUESS; unlabeled values are treated as GUESS.
- 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
The full state machine, branches, and gate semantics live in references/recon-kernel.md. The gate order is fixed:
TARGET_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-compare
Use 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.
1---2name: web-shader-extractor3description: 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.4---5
6# Web Shader Extractor
7
8Index for WebGL / WebGPU / Canvas rendering investigation and local replay.
9Start from the target visual. Lock the surface group. Trace source or runtime facts. Build a runnable baseline. Then projectize.
10
11## Router Contract
12
13This file is the index. Do not treat it as the full operating manual. Before task action, read:
14
15- `references/operating-contract.md`
16- `references/recon-kernel.md`
17
18Then load only the focused references needed by the current state.
19Keep large evidence, captures, and generated outputs out of the conversation.
20Store them in the user's output directory.
21
22## Use This For
23
24- Extracting a webpage WebGL, WebGPU, Canvas2D, OffscreenCanvas, shader, or animated canvas effect.
25- Replaying an animated background, product shader, interactive WebGL scene, or Canvas visual locally.
26- Building an evidence-matched baseline first, then an editable project.
27- Investigating target-bound shader/render graph/timing/resource/input facts.
28
29Do not use this for ordinary DOM/CSS cloning, static screenshots, generic website copying, unrelated JavaScript deobfuscation, or product UI redesign.
30Use it only when the task has a shader/canvas target.
31
32## Core Rules
33
34- Target-bound before framework-bound: a global Three.js, platform, or shader signature is only a hypothesis until tied to the target surface group.
35- Probes must discriminate: before running a probe, state which live hypotheses it separates and what each outcome eliminates. Evidence consistent with every candidate is weak; evidence only one candidate predicts is strong.
36- Evidence before implementation: source, runtime objects, frame captures, source maps, and public structured definitions outrank visual fitting.
37- No fabricated numbers: confidence is expressed with hypothesis status and `SOURCE`/`PARTIAL`/`GUESS`, never invented probabilities or scores.
38- Baseline before projectization: never overwrite a verified baseline for cleanup, simplification, or native conversion.
39- Honest labels: implementation-critical facts are `SOURCE`, `PARTIAL`, or `GUESS`; unlabeled values are treated as `GUESS`.
40- No compensation tuning: do not adjust brightness, time, color, offsets, or noise to mask missing pipeline evidence.
41- Gate artifacts are transition guards: if the required artifact is missing, incomplete, or has placeholders in gate-critical fields, the state has not advanced.
42- Ask only for product scope changes or external access/permission blockers.
43- Use plain records: state the fact, evidence path, current unknown, and next action. Avoid metaphor, broad claims, and unsupported conclusions.
44
45## State Router
46
47The full state machine, branches, and gate semantics live in `references/recon-kernel.md`. The gate order is fixed:
48
49`TARGET_LOCKED` must precede deep source/bundle work.
50Before lock, only narrow source probes tied to `nextProbe` are allowed.
51`REPLAY_READY` must precede implementation.
52`BASELINE_VERIFIED` must precede projectization.
53
54## Reference Router
55
56Load only what the current state needs:
57
58| Need | Read |
59|---|---|
60| Global contract, fact labels, completion states | `references/operating-contract.md` |
61| Kernel, initial protocol, state flow, autonomy, budgets | `references/recon-kernel.md` |
62| Surface discovery and visual attribution | `references/surface-discovery.md` |
63| Lock criteria, target-bound evidence, scope, Three.js binding | `references/target-lock.md` |
64| Evidence labels, ledgers, unknown classes, sensitive data | `references/evidence-policy.md` |
65| Tool capability selection | `references/tool-capability-matrix.md` |
66| WebGL, WebGPU, and Canvas2D capture facts | `references/capture-backends.md` |
67| Source maps, bundle slices, config, encoded definitions | `references/source-analysis.md` |
68| Replay readiness, routes, baseline, stack choice, projectization | `references/replay-policy.md` |
69| QA, failure routing, severity, mismatch signatures | `references/qa-failure-policy.md` |
70| Three.js shader injection or TSL reconstruction | `references/three-shader-reconstruction.md` |
71| Unicorn Studio target | `references/unicorn-studio.md` |
72| shaders.com / TSL target | `references/shaders-com.md` |
73
74## Tool And Artifact Policy
75
76Tools are replaceable capabilities, not prerequisites. First record the available capability profile:
77
78```text
79navigate, runtime-eval, preload-script, network-metadata, network-body,
80source-map, canvas-screenshot, interaction, frame-capture-webgl,
81frame-capture-webgpu, local-run, multi-frame-compare
82```
83
84Use `scripts/fetch-rendered-dom.mjs` only as an optional inventory helper when Playwright is already available.
85Use `scripts/scan-bundle.sh` only on target-bound bundle slices or a precise `nextProbe`.
86Script output is hypothesis evidence. It never satisfies Surface Attribution, Target Lock, Replay Ready, or QA gates by itself.
87
88Use bundled templates as schemas, not free-form notes:
89
90- `templates/scout-card.json`
91- `templates/replay-manifest.json`
92- `templates/run-state.json`
93- `templates/qa-report.md`
94- `templates/known-gaps.md`
95- `templates/extraction-report.md`
96
97## Platform Adapters
98
99Load platform references only after target-bound evidence points there:
100
101- Unicorn Studio: `references/unicorn-studio.md`
102- shaders.com / TSL: `references/shaders-com.md`
103- Three.js shader injection or TSL: `references/three-shader-reconstruction.md`
104
105If no adapter fits, follow generic WebGL, WebGPU, or Canvas2D capture in `references/capture-backends.md`.
lixiaolin94