Run any Skill in Manus with one click

renderdoc-pass-to-project-mapping

Stars1

Forks0

UpdatedJuly 6, 2026 at 18:12

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Kirkice

Kirkice/Vertex-Code

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	renderdoc-pass-to-project-mapping
description	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.

RenderDoc Pass To Project Mapping

Connect capture evidence to workspace code so the user can leave the frame and change the real implementation.

Workflow

Resolve capture state. Call renderdoc_openCapture if needed.
Resolve the target pass or event. Use renderdoc_getSelectionContext for current-selection questions. Call renderdoc_getEventDetails for the target EID. Call renderdoc_getFrameSummary when the user starts from a high-level pass description instead of a specific event.
Gather the best search anchors. Call renderdoc_getShaderInfo for stage names, entry points, and binding context. Call renderdoc_getShaderSource only if the source text is needed to improve project-side matching.
Search the workspace implementation. Call renderdoc_findProjectImplementation with the strongest available anchors from the event, pass, and shader data.

Output

Report:

The pass or event being mapped
The strongest implementation clues from the capture
The most likely project files or code regions
Any ambiguity and how to disambiguate it

Guardrails

Do not present weak filename guesses as confirmed ownership.
If the mapping is ambiguous, show the leading candidates and explain why.
Keep RenderDoc facts and project-side guesses clearly separated.

More from this repository

same repository

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-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-pass-to-project-mapping
description	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.

RenderDoc Pass To Project Mapping

Connect capture evidence to workspace code so the user can leave the frame and change the real implementation.

Workflow

Resolve capture state. Call renderdoc_openCapture if needed.
Resolve the target pass or event. Use renderdoc_getSelectionContext for current-selection questions. Call renderdoc_getEventDetails for the target EID. Call renderdoc_getFrameSummary when the user starts from a high-level pass description instead of a specific event.
Gather the best search anchors. Call renderdoc_getShaderInfo for stage names, entry points, and binding context. Call renderdoc_getShaderSource only if the source text is needed to improve project-side matching.
Search the workspace implementation. Call renderdoc_findProjectImplementation with the strongest available anchors from the event, pass, and shader data.

Output

Report:

The pass or event being mapped
The strongest implementation clues from the capture
The most likely project files or code regions
Any ambiguity and how to disambiguate it

Guardrails

Do not present weak filename guesses as confirmed ownership.
If the mapping is ambiguous, show the leading candidates and explain why.
Keep RenderDoc facts and project-side guesses clearly separated.