Audit and prepare Node3D packages for safe npm publishing. Use for pre-publish checks, package.json exports/files, npm pack dry-runs, lockfile scope, standalone package readiness, workspace versus submodule safety, release hygiene, package metadata, and root/submodule commit or push planning.
Maintain Node3D GitHub Actions and CI infrastructure. Use for workflow files, reusable actions, lint/test/build/publish jobs, platform matrices, native addon CI, CUDA/GPU limitations, prebuilt binary constraints, npm install script safety, cpplint, and keeping package CI consistent across repositories.
Work on Node3D native addon packages and N-API binding surfaces. Use for C++ addon production, addon-tools macros, binding.gyp/common.gypi, install.js, binary loading, ts/native.ts typing, pointer and handle modeling, native package scripts, or native addon verification in packages such as glfw, image, webgl, segfault, bullet, cuda, opencl, qml, iohook, and webaudio.
Implement Node3D GPU compute workflows. Use for CUDA, OpenCL, GLSL render-to-texture compute, GL/CUDA or GL/OpenCL interop, GPU-side model data layout, VBO/texture memory ownership, kernel argument packing, shared/local memory optimization, compute-driven rendering examples, and boids-style simulations.
Work on Node3D core browser, DOM, canvas, WebGL, and Three.js compatibility. Use for @node-3d/core, browser-like environment setup, Document/Window/Canvas behavior, global object wiring, raw WebGL support, Three.js helper compatibility, resource/context management, and the philosophy of Node.js desktop 3D with real OpenGL.
Work on Node3D deps-* packages that bundle third-party binaries, headers, and thin entrypoints. Use for dependency package layout, platform archives, bundled library motivation, getPaths/bin/include contracts, licensing notes, install behavior, and creating or updating packages such as deps-opengl, deps-freeimage, deps-bullet, deps-labsound, deps-qt-*, deps-qmlui, and deps-uiohook.
Write and maintain Node3D package documentation. Use for package README files, API sections, usage snippets, examples derived from source, feature descriptions, package role explanations, third-party license notes, and synchronizing documentation with TypeScript exports and runnable examples.
Create, review, or maintain Node3D examples. Use for runnable examples, package self-imports, realistic consumer-like usage, feature coverage demos, example assets, screenshots, README snippets derived from examples, and avoiding legacy relative imports into ts or dist.