메뉴
Define and enforce a three.js game asset pipeline around glTF/GLB, compression, validation, naming conventions, runtime prefab assembly, and loader setup. Use when importing or normalizing 3D assets for real-time gameplay.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | threejs-game-asset-pipeline |
| description | Define and enforce a three.js game asset pipeline around glTF/GLB, compression, validation, naming conventions, runtime prefab assembly, and loader setup. Use when importing or normalizing 3D assets for real-time gameplay. |
把美术资源处理成适合游戏运行时使用的 three.js 资产流水线，重点是 glTF / GLB、压缩、验证、命名约定和运行时装配。
glTF / GLBglTF / GLB 作为正式运行时资产FBX / OBJ / blend 等都视作源资产，不直接进入生产 runtimeGLTFLoader至少定义：
socket_weapon_r, socket_cameracol_static, col_trigger默认建议：
但必须说明取舍：
检查是否需要：
setDRACOLoadersetKTX2LoadersetMeshoptDecoder并输出示例初始化方案。
必须至少包含：
不要直接在业务代码里遍历整棵模型树做猜测。导入后应建立：
AssetRegistryUse 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.