Use this agent to review scena public API ergonomics, happy-path examples, beginner failure modes, typed handles, actionability of errors, scene authoring helpers, and whether the API is easier than Three.js for Rust application developers.
Use this agent to review scena doctor rules, silent-failure prevention, source-derived validation gates, checklist enforcement, and whether new bug families should become automated checks.
Use this agent for glTF/GLB import, KHR extensions, animation clips, skinning, morph targets, anchors/extras, units, coordinate conversion, SceneImport rebinding, asset cache/dedup, and hot reload semantics.
Use this agent to review scena RFC changes, Three.js replacement claims, v1.0/v1.x scope, non-goals, milestones, and whether proposed features belong in a renderer rather than a simulation/game/domain engine.
Use this agent to review visual correctness, browser/WASM rendered-output proof, headless screenshot tests, color management, labels/lines/clipping proof, leak/allocation gates, and capability-matrix evidence.
Use when an LLM needs to build, verify, debug, or iterate on a scena application, scene recipe, viewer, CAD inspection workflow, digital twin, product configurator, dashboard, documentation renderer, or agent verification loop using public scena CLI/schema/docs instead of repo internals.
Use when adding, changing, or reviewing scena doctor checks, validation gates, silent-failure prevention, source-derived architecture rules, or checklist enforcement.
Use when working with scena Git state, branches, commits, tags, GitHub issues, pull requests, workflow runs, release publication, or when the user asks to verify local state against GitHub.
Use when preparing scena user-visible changes for release, changing crate metadata, versioning, changelog/release notes, public API stability, cargo publish dry runs, semver checks, or v1.0 release evidence.
Use when compiling scena, running cargo fmt/clippy/test/doc/doctor/publish dry-run, synchronizing local work to the Hetzner CPU builder, or reporting remote build/test proof.
Use when implementing or refactoring scena renderer architecture, public API, module ownership, typed handles, resource lifetime, prepare/render lifecycle, surface/context recovery, or native/WASM platform boundaries.
Use when editing, reviewing, or executing the scena RFC, including v1.0/v1.x scope, milestones, Three.js replacement claims, non-goals, and whether a feature belongs in the renderer.
IEC 61131-3 Structured Text language server for Claude Code. Wires the trust-lsp binary into Claude Code's LSP integration for diagnostics, go-to-definition, find references, hover, document and workspace symbols, and call hierarchy on .st files.