菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/johannesPettersson80/scena --skill scena-renderer-architecture命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
基于 SOC 职业分类
正在显示 SKILL.md
| name | scena-renderer-architecture |
| description | 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. |
scene: scene graph, typed keys, transforms, bounds, anchors, clipping, queries.assets: fetchers, caches, glTF/GLB parsing, texture decoding, asset handles, retain policy.geometry: primitives, technical lines, helpers, labels metadata.material: material descriptors, texture slots, color space, alpha modes.render: wgpu device/surface, prepare lifecycle, pipelines, passes, stats, GPU resources.animation: glTF clips, mixer state, skinning, morph targets.controls: platform-neutral camera controls.picking: rays, acceleration, typed hit results.diagnostics: structured errors, debug overlays, capabilities.platform: thin winit/browser adapters only.render().Manager/Engine/World/broad Context types, and add
abstractions only when they remove real duplication or enforce a current contract.Use scena-remote-builder for compile/test gates and follow its validation ladder. Start
with the focused contract test or rendered proof for the change, then add scoped gates for
the touched surface. Do not run local cargo/build/test unless the user explicitly permits
it. Full release gates are for cross-module renderer changes, public API/schema behavior,
release-ready handoff, or explicit user request.
Common scoped gates on scena-builder:
ssh scena-builder 'cd "$HOME/.cache/codex-worktrees/scena-<task-slug>" && env CARGO_TARGET_DIR="$HOME/.cache/codex-targets/scena-<task-slug>" cargo fmt --check'
ssh scena-builder 'cd "$HOME/.cache/codex-worktrees/scena-<task-slug>" && env CARGO_TARGET_DIR="$HOME/.cache/codex-targets/scena-<task-slug>" cargo clippy --all-targets -- -D warnings'
ssh scena-builder 'cd "$HOME/.cache/codex-worktrees/scena-<task-slug>" && env CARGO_TARGET_DIR="$HOME/.cache/codex-targets/scena-<task-slug>" cargo test'
Use the full set only after the focused proof is green and the implementation risk justifies
it. Use scena-remote-builder to sync local uncommitted work before running these gates.
For multi-step architecture work, validate one ownership or lifecycle change at a time with
its focused proof. Save the full cargo/clippy/test/doc/browser chain for the integration
checkpoint unless the user explicitly requests it earlier.