菜单
Create or refactor a three.js game runtime into a maintainable project structure with a renderer factory, game loop, resize flow, lifecycle hooks, and service boundaries. Use for new projects or when a demo needs production-grade runtime structure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to report, summarize, audit, or present the implementation result of a plan, roadmap, PRD, engineering plan, refactor plan, migration plan, release plan, or task list. Produces evidence-based completion reports with overall, stage, and module completion percentages; goal-to-result verification tables; explicit concrete engineering benefits; unfinished-work impact analysis; and concrete next actions, using tables and charts instead of vague prose.
Use when the user asks for a software engineering plan, implementation plan, refactor plan, migration plan, rollout plan, bug-fix plan, performance optimization plan, security change plan, DevOps / CI/CD plan, technical execution plan, or review of an existing engineering plan. Produces phased, executable, independently verifiable, reviewable, rollback-aware plans with strict phase gates, plan-to-code completeness, benefit validation, and chain-state logging evidence for software engineering work.
Use when a task needs independent adversarial review during vibe coding, design work, implementation, testing, release planning, documentation, skill creation, or agent workflow design. It uses fresh internal subagents, or a user-approved local CLI reviewer fallback when internal subagents are unavailable, to attack artifact assumptions, happy paths, implementation completeness, target benefit realization, user-perspective usability, failure scenarios, and evidence gaps through formal /vs_review/ reports and mandatory response closure.
Use when Codex needs to design, reorganize, audit, or maintain a repository's documentation system: docs/ directory hierarchy, global vs version-level documents, version PRDs, technical designs, engineering plans, document versioning, naming conventions, link/index management, archive policy, or automated docs structure validation.
Use when debugging medium or large bugs, regressions, flaky failures, production symptoms, repeated failed fixes, or user-explicit requests where the agent must combine persistent /coe case tracking, independent multi-path root-cause investigation, and a hard diagnostic evidence gate before repair design or implementation.
Use when a user brings a new product, feature, app, website, internal tool, automation, workflow, or other product requirement that needs multi-round clarification before implementation. The skill keeps the conversation focused on product logic, user experience, interaction design, rules, edge cases, and acceptance criteria, then writes a Draft or Ready PRD.
| name | threejs-game-bootstrap-runtime |
| description | Create or refactor a three.js game runtime into a maintainable project structure with a renderer factory, game loop, resize flow, lifecycle hooks, and service boundaries. Use for new projects or when a demo needs production-grade runtime structure. |
建立一个可维护、可扩展、适合游戏开发的 three.js 运行时基线，而不是一次性 demo 脚本。
Vite + TypeScript strictrenderer.setAnimationLoop() 驱动循环App, World, Render, Input, UI, AssetRegistry 服务推荐最小骨架：
src/
main.ts
app/
GameApp.ts
render/
RendererService.ts
CameraService.ts
SceneService.ts
world/
WorldRoot.ts
input/
InputService.ts
ui/
UiRoot.ts
assets/
AssetRegistry.ts
shared/
events.ts
types.ts
必须显式设置：
antialiaspowerPreferencealphacanvasoutputColorSpace默认要求：
setPixelRatio(Math.min(window.devicePixelRatio, 2))主循环至少分成：
不要把所有内容都塞进一个 tick()。
推荐做法：
rawDelta：原始帧间隔gameDelta：受暂停/slow-motion 影响的逻辑间隔fixedDelta：物理固定步长至少拆分：
避免：
必须提供：
init()start()pause()resume()dispose()资源释放要贯穿运行时，不要等项目大了再补。
window / DOM 操作散落到所有模块