com um clique
renderdoc-for-vscode
renderdoc-for-vscode contém 8 skills coletadas de Kirkice, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
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.
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.