johannesPettersson80/scena

scena-git-github

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.

scena-release-hygiene

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.

scena-remote-builder

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.

scena-renderer-quality

Use when adding or reviewing scena tests, visual proof, browser/WASM checks, headless screenshots, color/capability validation, resource lifetime tests, dirty-state tests, allocation gates, or benchmark evidence.

scena-app-builder

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…

scena-doctor

Use when adding, changing, or reviewing scena doctor checks, validation gates, silent-failure prevention, source-derived architecture rules, or checklist enforcement.

scena-renderer-architecture

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.

scena-gltf-assets

Use when implementing or reviewing glTF/GLB loading, KHR extensions, asset cache/dedup/hot reload, anchors/extras, units, coordinate conversion, animation clips, skinning, morph targets, or import rebinding.

scena-rfc-governance

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.