菜单
Trace how a texture is produced, consumed, and related to passes in a RenderDoc capture. Use when asked where a texture comes from, which draws sample it, where a render target is written, or how a texture flows through a frame.
用 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.
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.
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.
| name | renderdoc-texture-trace |
| description | Trace how a texture is produced, consumed, and related to passes in a RenderDoc capture. Use when asked where a texture comes from, which draws sample it, where a render target is written, or how a texture flows through a frame. |
Follow a texture through the frame as a resource, not just as a screenshot.
Resolve capture state.
Call renderdoc_openCapture if needed.
Identify the texture precisely.
Use renderdoc_getSelectionContext when the user refers to a selected resource.
Call renderdoc_getTextureInfo or renderdoc_getResourceDetail to confirm identity, dimensions, format, and type.
Find producer and consumer events.
Call renderdoc_findDrawsByTexture when tracing sampled usage.
Call renderdoc_findDrawsByResourceId when tracing exact resource references.
Add pass context.
Inspect representative events with renderdoc_getEventDetails.
Use renderdoc_getPipelineState only when the binding context or render-target role needs confirmation.
Summarize:
Prefer a short producer-to-consumer story over a long event list.
