メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | renderdoc-buffer-inspector |
| description | 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. |
Inspect buffers carefully and incrementally so the answer stays grounded and readable.
Resolve capture state.
Call renderdoc_openCapture if needed.
Identify the target buffer exactly.
Use renderdoc_getSelectionContext for selected resources.
Call renderdoc_getResourceDetail first to confirm the resource is a buffer and to capture size and role.
Read a small slice before reading more.
Call renderdoc_getBufferContents with a narrow offset and len by default.
Page outward only if the user asks for more or the first slice is clearly insufficient.
Add event context when needed.
Call renderdoc_findDrawsByResourceId or renderdoc_getEventDetails if the meaning of the data depends on how the buffer is used.
Prefer decoded constant-buffer views when available. If the question is really about bound constant values at an event, use shader and pipeline inspection before falling back to raw bytes.
Explain:
