메뉴
Set a three.js game rendering baseline for color management, PBR, lighting, environment maps, shadows, transparency, and post-processing. Use when visual consistency, performance budgets, and WebGL/WebGPU boundaries need to be defined.
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-render-lighting |
| description | Set a three.js game rendering baseline for color management, PBR, lighting, environment maps, shadows, transparency, and post-processing. Use when visual consistency, performance budgets, and WebGL/WebGPU boundaries need to be defined. |
建立 three.js 游戏项目的渲染基线：颜色空间、PBR、灯光、阴影、透明、后处理和渲染预算。
必须输出：
默认优先：
scene.environment如果没有环境贴图却要求写实金属材质，先指出问题，不要硬调 directional light 强行顶替。
先判断：
输出应包含：
按对象类别定义：
alphaTest 风格transparentWebGL 路径可考虑：
但要明确：
只有在以下情况再建议 WebGPU / TSL 进阶：
否则先稳在 WebGL。