bpodwinski

World42's CBT/OCBT terrain-LOD knowledge and workflow. Every planet runs the single integrated, validated GPU pool-CBT (OCBT) terrain engine. Use when requests mention Concurrent Binary Trees, OCBT, large_cbt, bisectors, triangle-area/screen-space LOD, or the GPU topology engine in paths under src/systems/lod/, src/app/setup_lod_and_shadows.ts, src/game_world/stellar_system/, and camera-space contracts.

Analyze, tune, and evolve the OCBT lighting pipeline in World42. CDLOD is abandoned — this skill covers only the OCBT WebGPU path. Use when editing the OCBT fragment shader (terrain_render_material.ts), baked lighting constants, Lommel-Seeliger BRDF, Cook-Torrance specular, curvature AO, aerial fog, opposition surge, procedural albedo, ambient/light uniforms, tone-mapping consistency, or atmospheric scattering integration.

Profile and diagnose World42 GPU/CPU performance with a headed Playwright harness plus nvidia-smi and OS counters. Use when a request mentions GPU at 100%, perf profiling, frame drops/hitches, gpuMs, GPU/CPU utilization, terrain/OCBT cost, fragment-vs-compute bottleneck, before/after optimization comparison, a repeatable bench scene/camera path, or "why is it slow at ground/orbit". Covers scripts/perf_probe.mjs (knob sweeps), scripts/bench_flight.mjs (deterministic ground→orbit flight for before/after diff), the window.__world42Perf / __world42Bench debug APIs, and the webgpu-inspector MCP for structural captures.

World42's CBT/OCBT terrain-LOD knowledge and workflow. Per planet a planet runs CDLOD or a Concurrent Binary Tree (never both); the CBT side has grown from a CPU stub into an integrated, validated GPU pool-CBT (OCBT) engine. Use when requests mention Concurrent Binary Trees, OCBT, large_cbt, bisectors, triangle-area/screen-space LOD, the GPU topology engine, or selecting the per-planet terrain algorithm in paths under src/systems/lod/, src/app/setup_lod_and_shadows.ts, src/game_world/stellar_system/, and camera-space contracts.

Implement and tune Babylon.js CDLOD terrain rendering with GPU vertex geomorphing, quadtree patch selection, crack prevention, and stable LOD transitions. Use when tasks mention terrain or planet LOD popping, cracks between tiles, patch churn, ShaderMaterial terrain displacement, or edits to quadtree LOD logic and terrain vertex shaders.

Audit and enforce coordinate-space boundaries in World42 across WorldDouble, render-space, and planet-local data paths. Use when requests mention precision drift, wrong culling distances, broken teleport/camera placement, incorrect shader lighting vectors, or any edits in src/core/camera/, src/systems/lod/chunks/, src/game_world/stellar_system/, and ScaleManager conversions.

Tune and stabilize World42 CDLOD behavior, including split/merge hysteresis, scheduler frame budgets, worker pressure, and chunk culling decisions. Use when requests mention LOD popping, frame spikes, over-subdivision, delayed detail, chunk churn during camera motion, or edits under src/systems/lod/, src/app/setup_lod_and_shadows.ts, and related LOD constants.

Analyze and safely evolve World42 OriginCamera floating-origin behavior end-to-end. Use when requests mention OriginCamera, doublepos vs position, teleport/camera placement, camera speed/velocity metrics, world/render conversion bugs, or when editing camera integrations in src/core/camera/, src/core/control/, src/app/, src/systems/lod/, and render postprocess paths.

Incrementally fix Clippy lints across a Cargo workspace. Use this skill whenever the user asks to fix clippy warnings, address lints, clean up Rust code quality, run a clippy pass, or reduce warnings. Also trigger when the user mentions "clippy bot", "rust-clippy", "lint pass", "fix warnings", "deny lints", or wants to systematically address clippy diagnostics. Works on any multi-crate Cargo workspace with a persistent branch strategy and incremental history tracking.

Scans a Rust project to identify functions/methods missing unit tests, then generates them. Usage: /rust-unit-tests [path] — path is optional, defaults to the current working directory.

Incrementally add missing Rustdoc (///) for undocumented public Rust items across a Cargo workspace. Use this skill whenever the user asks to document Rust code, add missing rustdoc, improve documentation coverage, run a doc audit, or maintain documentation hygiene on a Rust project. Also trigger when the user mentions "rustdoc bot", "rust-doc", "documentation pass", "doc coverage", "undocumented pub items", or wants to systematically add /// comments to public API surfaces. Works on any multi-crate Cargo workspace with a persistent branch strategy and incremental history tracking.

Build, review, and debug Leptos/Rust applications with pragmatic architecture guidance, component patterns, reactive state management, server functions, SSR/hydration, routing, and deployment checklists; use when implementing or maintaining a Leptos codebase.