guitar-gear-qa
Guitar Gear QA
Use this skill as the final audit for guitar pedal, amplifier, cabinet, and related Blender product scenes.
Read the QA checklist for the inspection matrix, mounting tests, boundary diagnosis, preservation evidence and delivery gates. scripts/scene_audit.py is an optional direct-scene heuristic; it does not validate nested evaluated assemblies, physical clearances or visual quality.
Runtime GLB and WebView QA
For interactive plugin assets, read runtime QA for semantic hierarchy/pivot checks, browser visual parity, a reusable metrics report, host automation/state restore and instance-ladder profiling. Run standalone WebGL acceptance before JUCE integration and repeat on each target WebView backend. The static Blender audit is insufficient for these claims.
During a performance pass, every change that can alter the picture (pixel ratio, shadow-map size, texture resolution, redraw rate, merged geometry) is a candidate, not a default. Judge it with the performance candidate procedure: a measured benefit, matched views at every critical size tier, and a recorded ACCEPT or REJECT with the reason.
Refinement decision rules
Lock accepted systems and name the allowed changes before editing. For ambiguous visible defects, compare the baseline with restrained candidates under fixed conditions; keep the smallest change that improves reference match at delivery size. Stop when requested work is complete, delivery-preventing or visibly/dimensionally wrong issues are resolved, and protected systems pass regression checks; do not discard verified repairs or mark unfinished requirements passed to stop.
Use the refinement contract for source/target versions, evidence and stop conditions. The shared candidate and diagnosis procedure owns detailed comparison rules. If using this skill alone, record facts, accepted values, uncertain estimates, allowed changes and protected properties in the existing project brief.