メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | renderdoc-current-selection-explainer |
| description | 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. |
Translate the current RenderDoc selection into a short, grounded explanation without making the user specify raw IDs.
Resolve capture state if needed.
Call renderdoc_openCapture if no capture is loaded.
Resolve the selection first.
Call renderdoc_getSelectionContext before interpreting "this", "current", or "selected".
Branch on the selected thing.
If a draw or event is selected, call renderdoc_getEventDetails.
If pipeline or shader context matters, call renderdoc_getShaderInfo or renderdoc_getPipelineState.
If a resource is selected, call renderdoc_getResourceDetail or renderdoc_getTextureInfo.
Add only the most useful supporting detail. Pull in mesh, texture, or buffer details only if they materially explain the selection.
Explain:
Prefer plain language over raw JSON.
renderdoc_getSelectionContext.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.
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.
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.
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.