Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

renderdoc-current-selection-explainer

Estrellas1

Forks0

Actualizado6 de julio de 2026 a las 18:12

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Kirkice

Kirkice/Vertex-Code

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

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.

RenderDoc Current Selection Explainer

Translate the current RenderDoc selection into a short, grounded explanation without making the user specify raw IDs.

Workflow

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.

Output

Explain:

What the selected item is
What role it appears to play in the frame
The most important evidence behind that explanation
The next best follow-up question or inspection step

Prefer plain language over raw JSON.

Guardrails

If there is no current selection, say that explicitly and ask for a selection only if the user intent truly depends on it.
Do not guess what "this" refers to without renderdoc_getSelectionContext.
Keep the answer scoped to the selected item unless the user asks for broader frame context.

Más de este repositorio

mismo repositorio

renderdoc-buffer-inspector

Kirkice/Vertex-Code

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.

2026-07-061

renderdoc-frame-overview

Kirkice/Vertex-Code

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.

2026-07-061

renderdoc-pass-to-project-mapping

Kirkice/Vertex-Code

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.

2026-07-061

renderdoc-performance-investigation

Kirkice/Vertex-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.

2026-07-061

renderdoc-shader-review

Kirkice/Vertex-Code

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.

2026-07-061

renderdoc-texture-trace

Kirkice/Vertex-Code

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.

2026-07-061

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.

RenderDoc Current Selection Explainer

Translate the current RenderDoc selection into a short, grounded explanation without making the user specify raw IDs.

Workflow

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.

Output

Explain:

What the selected item is
What role it appears to play in the frame
The most important evidence behind that explanation
The next best follow-up question or inspection step

Prefer plain language over raw JSON.

Guardrails

If there is no current selection, say that explicitly and ask for a selection only if the user intent truly depends on it.
Do not guess what "this" refers to without renderdoc_getSelectionContext.
Keep the answer scoped to the selected item unless the user asks for broader frame context.