菜单
Map RenderDoc passes, events, and shaders back to likely project-side source files and implementation points. Use when asked where a pass is implemented, which project files correspond to a capture event, or how a RenderDoc shader links back to workspace code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Inspect buffer resources and their contents in a RenderDoc capture, including raw bytes and event context. Use when asked to inspect a GPU buffer, constant-buffer contents, structured data, or the meaning of selected buffer bytes in a RenderDoc capture.
Explain the currently selected RenderDoc draw, event, or resource in practical terms. Use when the user refers to "this", "current", or "selected" in a RenderDoc capture and wants to know what it is doing, why it matters, or what to inspect next.
Summarize the structure of a RenderDoc capture and identify its top-level passes, markers, and likely inspection targets. Use when asked for a frame overview, pass breakdown, render flow, first-look summary, or "what is happening in this frame?" for a RenderDoc capture.
Investigate performance bottlenecks in a RenderDoc capture and explain which passes or draws are expensive and why. Use when asked to find the hottest work in a frame, rank expensive draws, explain GPU cost, or produce an optimization report for a RenderDoc capture.
Recover from missing RenderDoc capture or replay state before attempting deeper analysis. Use when tools report no capture loaded, replay inactive, native-only data unavailable, or when the user asks to restore enough state for RenderDoc inspection to continue.
Review shader behavior for a RenderDoc event, including stage roles, bindings, constant buffers, and likely issues. Use when asked to analyze a shader, explain shader-stage behavior, inspect bindings, review constant data, or suggest shader optimizations from a RenderDoc capture.
| name | renderdoc-pass-to-project-mapping |
| description | Map RenderDoc passes, events, and shaders back to likely project-side source files and implementation points. Use when asked where a pass is implemented, which project files correspond to a capture event, or how a RenderDoc shader links back to workspace code. |
Connect capture evidence to workspace code so the user can leave the frame and change the real implementation.
Resolve capture state.
Call renderdoc_openCapture if needed.
Resolve the target pass or event.
Use renderdoc_getSelectionContext for current-selection questions.
Call renderdoc_getEventDetails for the target EID.
Call renderdoc_getFrameSummary when the user starts from a high-level pass description instead of a specific event.
Gather the best search anchors.
Call renderdoc_getShaderInfo for stage names, entry points, and binding context.
Call renderdoc_getShaderSource only if the source text is needed to improve project-side matching.
Search the workspace implementation.
Call renderdoc_findProjectImplementation with the strongest available anchors from the event, pass, and shader data.
Report:
