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 procedural scenes.
Start a fresh conversation. Replace the highlighted placeholders.
Use threejs-visual-validation to Following the loading of a subject or image-effect skill, validate [Three.js scene] by capturing no-post baselines, diagnostic views, camera-distance envelopes, and stress seeds to produce a budget and stability report with an accept/reject decision.
Required inputs
[Three.js scene]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: threejs-visual-validationdescription: 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 procedural scenes.
Visual Validation
Evaluate the mechanism that creates the image. A beautiful hero screenshot can hide unstable fields, broken depth, seed failures, or post-processing dependence.
Validation sequence
Freeze deterministic inputs.
Capture the no-post baseline.
Capture system-specific diagnostic views.
Test the intended camera-distance envelope.
Sweep representative seeds and parameter extremes.
Test motion and temporal stability.
Record image, geometry, memory, and timing budgets.
Keep a small regression set tied to visual invariants.
Read references/graphics-validation-protocol.md
for visual contracts, required inspection controls, mechanism-specific
evidence, temporal checks, budgets, and explicit rejection criteria.
Required evidence
fixed camera and seed manifest;
final and no-post captures;
field/pass diagnostic mosaic;
near, design, and far camera views;
at least one stress seed;
frame-time and render-target inventory;
written invariants and known compromises.
Failure conditions
approval relies on a single frame;
post-processing cannot be disabled per pass;
random seeds are not reproducible;
GPU time is inferred only from CPU frame time;
temporal artifacts are judged from still images;
comparison thresholds ignore intentional stochastic pixels without stabilizing them.
Routing boundary
This skill evaluates an implementation; it does not supply the implementation
mechanism. Load the subject or image-effect skill first, then use this protocol
to decide whether the result is acceptable.