Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

renderdoc-texture-trace

Étoiles1

Forks0

Mis à jour6 juillet 2026 à 18:12

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Kirkice

Kirkice/Vertex-Code

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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.

RenderDoc Texture Trace

Follow a texture through the frame as a resource, not just as a screenshot.

Workflow

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.

Output

Summarize:

What the texture is
Where it is likely produced
Where it is sampled or referenced
Which passes seem to depend on it

Prefer a short producer-to-consumer story over a long event list.

Guardrails

Do not assume a texture is a shadow map, G-buffer target, or post-process intermediate without evidence.
If there are many matches, group them by pass or role instead of dumping every EID.
If the selected resource is not a texture, say so and switch to the most relevant resource-level explanation.

Plus depuis ce dépôt

même dépôt

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-current-selection-explainer

Kirkice/Vertex-Code

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.

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

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.

RenderDoc Texture Trace

Follow a texture through the frame as a resource, not just as a screenshot.

Workflow

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.

Output

Summarize:

What the texture is
Where it is likely produced
Where it is sampled or referenced
Which passes seem to depend on it

Prefer a short producer-to-consumer story over a long event list.

Guardrails

Do not assume a texture is a shadow map, G-buffer target, or post-process intermediate without evidence.
If there are many matches, group them by pass or role instead of dumping every EID.
If the selected resource is not a texture, say so and switch to the most relevant resource-level explanation.