threejs-visual-validation

Name: threejs-visual-validation
Author: scottstts

377stars47forks

How to install threejs-visual-validation?

scottstts/threejs-awesome-graphics-agent-skills/threejs-visual-validation

$npx -y skills add scottstts/Threejs-Awesome-Graphics-Agent-Skills --skill threejs-visual-validation

Installs into the current project.

Summary

Validate advanced Three.js graphics as authored systems rather than subjective screenshots. Use for fixed-view visual contracts, field and pass diagnostics, no-post baselines, seed sweeps, camera-scale tests, temporal stability checks, GPU budgets, and regression evidence for pro

Files · 1

View on GitHub

SKILL.md

1	# Visual Validation
2
3	Evaluate the mechanism that creates the image. A beautiful hero screenshot can hide unstable fields, broken depth, seed failures, or post-processing dependence.
4
5	## Validation sequence
6
7	1. Freeze deterministic inputs.
8	2. Capture the no-post baseline.
9	3. Capture system-specific diagnostic views.
10	4. Test the intended camera-distance envelope.
11	5. Sweep representative seeds and parameter extremes.
12	6. Test motion and temporal stability.
13	7. Record image, geometry, memory, and timing budgets.
14	8. Keep a small regression set tied to visual invariants.
15
16	Read [references/graphics-validation-protocol.md](references/graphics-validation-protocol.md)
17	for visual contracts, required inspection controls, mechanism-specific
18	evidence, temporal checks, budgets, and explicit rejection criteria.
19
20	## Required evidence
21
22	- fixed camera and seed manifest;
23	- final and no-post captures;
24	- field/pass diagnostic mosaic;
25	- near, design, and far camera views;
26	- at least one stress seed;
27	- frame-time and render-target inventory;
28	- written invariants and known compromises.
29
30	## Failure conditions
31
32	- approval relies on a single frame;
33	- post-processing cannot be disabled per pass;
34	- random seeds are not reproducible;
35	- GPU time is inferred only from CPU frame time;
36	- temporal artifacts are judged from still images;
37	- comparison thresholds ignore intentional stochastic pixels without stabilizing them.
38
39	## Routing boundary
40
41	This skill evaluates an implementation; it does not supply the implementation
42	mechanism. Load the subject or image-effect skill first, then use this protocol
43	to decide whether the result is acceptable.

People who liked this also viewed

6 picks

Type

threejs-visual-validation

377stars47forks

View on GitHub

How to install threejs-visual-validation?

scottstts/threejs-awesome-graphics-agent-skills/threejs-visual-validation

$npx -y skills add scottstts/Threejs-Awesome-Graphics-Agent-Skills --skill threejs-visual-validation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Visual Validation
2
3	Evaluate the mechanism that creates the image. A beautiful hero screenshot can hide unstable fields, broken depth, seed failures, or post-processing dependence.
4
5	## Validation sequence
6
7	1. Freeze deterministic inputs.
8	2. Capture the no-post baseline.
9	3. Capture system-specific diagnostic views.
10	4. Test the intended camera-distance envelope.
11	5. Sweep representative seeds and parameter extremes.
12	6. Test motion and temporal stability.
13	7. Record image, geometry, memory, and timing budgets.
14	8. Keep a small regression set tied to visual invariants.
15
16	Read [references/graphics-validation-protocol.md](references/graphics-validation-protocol.md)
17	for visual contracts, required inspection controls, mechanism-specific
18	evidence, temporal checks, budgets, and explicit rejection criteria.
19
20	## Required evidence
21
22	- fixed camera and seed manifest;
23	- final and no-post captures;
24	- field/pass diagnostic mosaic;
25	- near, design, and far camera views;
26	- at least one stress seed;
27	- frame-time and render-target inventory;
28	- written invariants and known compromises.
29
30	## Failure conditions
31
32	- approval relies on a single frame;
33	- post-processing cannot be disabled per pass;
34	- random seeds are not reproducible;
35	- GPU time is inferred only from CPU frame time;
36	- temporal artifacts are judged from still images;
37	- comparison thresholds ignore intentional stochastic pixels without stabilizing them.
38
39	## Routing boundary
40
41	This skill evaluates an implementation; it does not supply the implementation
42	mechanism. Load the subject or image-effect skill first, then use this protocol
43	to decide whether the result is acceptable.

People who liked this also viewed

6 picks

Type