Three.js r186

TJ-L12/S08 · Three.js loading, initialization and compilation failures are not swallowed (empty catch, .catch(() => {}))

TJ-F09/F10/L13/P08/X11 · Per-frame callbacks do no unguarded allocation, GPU object construction or recompilation triggers

TJ-F10/F11/G06/G16/P19/S05/X13 · Per-frame callbacks do no unguarded loading, compilation, PMREM generation, vertex baking, layout reads, logging, scene scans or sync readback

TJ-L02/L04 · Code that removes or clears scene objects it built releases their GPU resources (remove/clear/null do not dispose; material.dispose() keeps its textures)

TJ-L06/L13 · Resize and re-setup handlers resize or reuse renderers and render targets instead of constructing new ones without disposing the old

TJ-L10/X07/X08 · KTX2/DRACO loaders are configured once (transcoder path, detectSupport), reused across assets and disposed when done

TJ-L09/L14/S09 · A teardown that exists stops the render loop and releases the renderer, controls, timer and animation mixers the module created

TJ-A06 · Reusable Three.js modules receive their canvas/container and size from the host (no document.body append or window sizing outside entry modules)

TJ-S02 · Renderer, scene, camera and loaders are not published as mutable globals (window.x / globalThis.x)

TJ-S06 · With a selected budget (maxFunctionLines), functions in Three.js modules stay within it (warn; off by default)

TJ-A07/S07 · No patching of three internals (private renderer fields, ShaderChunk/ShaderLib overrides, prototype monkey patches, raw GL state)

TJ-V01/V02/V04 · At session start, Claude learns the resolved three (and @types/three) version and whether this r186 profile applies

TJ-V03 · No r187+ API in r186 code (Light.registerNode light registration)

TJ-V05 · New code imports three as an ES module (require('three') is deprecated in r186 and warns at run time)

TJ-V05/V08/V09/V10/V41 · Imports from three and three/webgpu name exports the resolved package has (no Geometry, *Encoding, *BufferGeometry, default import…)

TJ-V05/V06/V08/V11 · three subpath imports exist in the resolved package (no examples/js, three/nodes, removed addons, removed global builds)

TJ-V05/V42 · TSL imports from three/tsl name functions the resolved package exports (no tslFn, timerLocal, cond, uniforms, rangeFog, blend renames…)

TJ-V04/V06 · HTML pages load three as modules from one revision: no removed three(.min).js builds, an import map for bare imports, core and addons on the same version

TJ-V07 · New addon imports use the public three/addons/ alias rather than three/examples/jsm/

TJ-V09/V10/V14/V34/V35/V37/V41 · No removed three members or options (outputEncoding, useLegacyLights, addAttribute, updateRange, waitForGPU, reverseDepthBuffer, TextGeometry height…)

TJ-V11/V16/V17/V18/V31/V42/V45 · New code avoids three exports r186 deprecates (Clock, PostProcessing, PCFSoftShadowMap, Source, RGBELoader, PI2, cache, label…)

TJ-V12/V25/V27/V32/V33/V34 · New code avoids deprecated three members (renderAsync/clearAsync/…, setDecoderConfig, detectSupportAsync, createShapes, GTAO distance settings…)

TJ-V11/V12/V45 · No new call or member resolves to a declaration three marks @deprecated (language server: Matrix3 transforms, PassNode.setResolution, PMREM async…)

TJ-V13 · WebGPURenderer is initialized (await init() or setAnimationLoop) before hasFeature/compute/render/initTexture/detectSupport, and init failures are handled

TJ-V15 · WebGPURenderer.dispose() is awaited or returned when teardown completes asynchronously (WebGLRenderer disposal stays synchronous)

TJ-V19 · A class extending a three Object3D type that overrides dispose() calls super.dispose() (r186 Object3D.dispose dispatches the dispose event)

TJ-V21 · toTrianglesDrawMode() mutates its geometry in place since r186: a second name for the result is a shared, changed geometry

TJ-V22/V33 · Promise-returning three APIs (SimplifyModifier.modify, EXR/KTX2 parse, parseAsync, loadAsync, fromCubeRenderTarget) are awaited or chained, not used as values

TJ-V23 · WebGLRenderer code uses r186's LightProbeGridWebGL / LightProbeGridHelperWebGL (LightProbeGrid is now the WebGPU class)

TJ-V24 · Sky / SkyMesh code does not write the removed up uniform (+Y up is assumed since r186)

TJ-V29 · FileLoader.load() and ImageBitmapLoader.load() results come from onLoad or loadAsync (their return value is undefined since r184)

TJ-V30 · No blanket Z-up correction on FBX imports (FBXLoader converts Z-up assets itself since r184)

TJ-V36 · copyTextureToTexture / copyFramebufferToTexture use the r186 argument order (textures first, positions after)

TJ-V38 · BatchedMesh geometries become visible through addInstance(geometryId), not addGeometry alone

TJ-V39 · TransformControls is shown by adding controls.getHelper() to the scene (the controls are not an Object3D since r169)

TJ-V40 · Controls.connect() receives the DOM element to listen to (no undefined fallback since r175)

TJ-V44 · A positionNode built from positionLocal on skinned or morphed meshes is a deliberate choice (positionGeometry keeps skinning/morphing)

TJ-A02/A03 · WebGPURenderer code customizes shading with node materials/TSL and post-processes with RenderPipeline (no ShaderMaterial, onBeforeCompile, EffectComposer)

TJ-A04 · Node materials rendered by WebGLRenderer go through the r186 WebGLNodesHandler (renderer.setNodesHandler)

TJ-A08 · Stencil-based materials render with a stencil buffer enabled on the renderer created in the same module (off by default since r163)

TJ-A09 · TSL nodes are combined with node methods (add/mul/If/select), not JavaScript operators or if/ternaries that run once on the CPU

TJ-A10 · ShaderMaterial uniforms are { value } objects, updated through uniform.value (no raw numbers/vectors, no replacing a uniform)

TJ-A11 · Custom GLSL 3 shaders set glslVersion: GLSL3 and do not embed their own #version directive

TJ-E03 · Reusable passes (functions receiving the renderer) that switch the render target restores the previous one (getRenderTarget) instead of assuming it was null

TJ-E05 · Replacing RenderPipeline.outputNode after setup sets pipeline.needsUpdate = true

TJ-F01 · A callback given to setAnimationLoop does not also schedule itself with requestAnimationFrame (one scheduling owner per surface)

TJ-F02 · XR rendering is scheduled by renderer.setAnimationLoop (window requestAnimationFrame does not run inside an XR session)

TJ-F05 · AnimationMixer.update and OrbitControls.update receive a delta in seconds, not a millisecond timestamp or an elapsed time

TJ-F06 · A Timer the module creates and reads is advanced with timer.update() (core Timer never advances on its own)

TJ-F08 · Controls with damping or auto-rotation enabled are updated every frame (controls.update) while those features run

TJ-G03 · Buffer attributes written in per-frame callbacks are flagged for upload (attribute.needsUpdate = true)

TJ-G05 · Instances moved every frame keep valid bounds for culling and picking (computeBoundingSphere, or a justified frustumCulled = false)

TJ-G07 · Literal vertex data matches its attribute itemSize (array length divisible by itemSize)

TJ-G08 · setMatrixAt / setColorAt / setMorphAt in frame callbacks and event handlers are followed by the matching needsUpdate flag

TJ-G13 · The result of mergeGeometries / mergeAttributes is checked for null before it replaces geometry

TJ-G14 · traverse() callbacks do not add or remove scene objects while iterating (collect, then mutate)

TJ-G15 · Objects with matrixAutoUpdate = false recompute their local matrix after transform changes and flag matrixWorldNeedsUpdate after direct matrix edits

TJ-P01 · The drawing buffer's pixel ratio is bounded (no raw devicePixelRatio: cost grows with its square)

TJ-P02 · Changing a camera's aspect, fov, near/far, zoom or frustum is followed by updateProjectionMatrix() in the same function

TJ-P03 · Aspect ratios computed from element sizes guard a zero height (hidden, collapsed or detached surfaces)

TJ-P04 · Literal perspective cameras use a valid depth range (0 < near < far) and, with a selected budget, a bounded far/near ratio

TJ-P05/P06 · Costly renderer options (preserveDrawingBuffer, MSAA under post-processing, logarithmicDepthBuffer) come with a stated purpose

TJ-P09 · onBeforeCompile code that varies the shader with closure values declares customProgramCacheKey

TJ-P13 · Materials using MultiplyBlending or SubtractiveBlending set premultipliedAlpha: true (required since r178)

TJ-P14/P15 · Shadows are enabled per object, not for a whole traversal, and shadow maps stay within the project's selected budget

TJ-P17/P18 · Pointer picking computes coordinates from the canvas rectangle and does not raycast the whole scene recursively on every move

TJ-X01 · Color textures loaded with TextureLoader and used as map/emissiveMap get colorSpace = SRGBColorSpace (TextureLoader leaves NoColorSpace)

TJ-X02 · Data maps (normal, roughness, metalness, AO, displacement, bump, alpha…) are not tagged SRGBColorSpace

TJ-X03 · Hex/CSS colors are not converted to linear a second time (ColorManagement already converts in setters)

TJ-X04/X05 · Post-processing applies tone mapping and output color conversion exactly once (OutputPass for EffectComposer; outputColorTransform off when renderOutput is manual)

TJ-X10 · Render targets are resized with setSize(), not by assigning width/height

TJ-X09/X12 · Textures assigned to glTF materials keep glTF orientation (flipY = false), and max anisotropy is not applied to every texture

TJ-T01 · Dependencies change through the package manager (add/remove/update), never by editing package.json by hand

TJ-T01/T02 · A new package.json comes from the package-manager initializer (or a generator), and gets its dependencies from the package manager

Records the tool calls that run a package manager (they may rewrite package.json and lockfiles; TJ-T01/T08)

TJ-T02 · A new package.json without dependencies is initialized with the package manager

TJ-T03 · Registry version lookups are not a step before installing

TJ-T03 · Packages are installed by name: no guessed exact version, no --save-exact without a reason

TJ-T04 · Dependencies are installed with the project's package manager (packageManager field, lockfile)

TJ-T04 · No second lockfile next to another package manager's lockfile

TJ-T05 · CI and container builds restore dependencies from the lockfile (npm ci, --frozen-lockfile, --immutable)

TJ-T06/S07 · Project sources do not contain copied three builds or addon modules (license header of Three.js Authors)

TJ-T06 · three builds and addons are not downloaded into the project by hand (curl/wget); the package manager or an import map provides them

TJ-T08 · Lockfiles are written by the package manager only (no hand edit, no script rewriting them)

TJ-T08 · A turn that changes package.json dependencies also updates the lockfile next to it (once per stop)

TJ-V01/T03 · Installing three or @types/three at a version outside this profile's release line needs the user's confirmation

TJ-V01 · After an install that named three, the resolved three is still on this profile's release line

Records, per session, Claude's edits (file tools and shell writes) and the typecheck, lint and test runs that succeeded after them (TJ-Q01)

TJ-Q01 · A turn adds no TypeScript errors to the changed files or their importers (language server, once per stop)

TJ-Q01 · A turn that changed Three.js code ends only after the configured checks (default: typecheck) succeeded on the final files (once per stop)

Records that the turn ran a measurement (benchmark, profiler, performance trace) for TJ-Q03

TJ-Q03 · A turn that changed Three.js code does not claim a measured performance gain without a measurement in the turn (once per stop)

Records the work tree when a prompt starts: the baseline of the Three.js end-of-turn checks (TJ-T08, Q01)