القائمة
When Titan frame-graph pass-ordering validation rules conflict with RON config files, RON configs are the authoritative source — fix the validation rule to match the RON
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when working on 3D-specific rendering — deferred chain, G-buffer, clustered shading, Stratum GI, ReGIR, SVGF/A-SVGF, TAA, shadow techniques, depth/HZB, anything 3D-specific. ALWAYS load titan-rendering-core first; this skill assumes core conventions. Loads Titan-specific overrides for realtime-rendering. NOT for 2D rendering or editor panels.
Use when diagnosing a Titan renderer artifact — flicker, ghosting, fireflies, banding, light leaks, seams, boil, NaN/Inf, aliasing, smear/trails, dark voids, shadow artifacts, GI instability, denoiser/TAA issues. The frame-isolation-first debugging method: capture 60Hz, diff frames / A-B vs classical, consult literature, isolate via systematic-debugging, propose (and prove) a fix, record empirically. NOT for landing the production fix (hand to titan-rendering-3d-agent), 2D rendering, or editor panels.
Use when working in titan-rendering-frame-graph, titan-rendering-core, or titan-rendering-post-process-core — frame graph DAG, RenderTarget, DevicePool, PostProcessHook, CameraFrameData, HDR intermediate, tonemap, color management. Foundational layer shared between current 3D and future 2D rendering. Loads Titan-specific overrides for realtime-rendering. NOT for 3D-specific concerns (deferred chain, GI, shadows) — load titan-rendering-3d after this.
When a Titan bench tool using Renderer3d lacks on_resize → renderer.resize(), depth_prepass_view and HZB occlusion resources are never created — DepthPrepass, HzbBuild, and SceneCull passes silently skip, and taps produce no output
When adding a camera UBO shared between Rust and WGSL, verify field-by-field that the CPU layout matches the WGSL struct — especially packed vec4 fields where reordering silently breaks the shader
When building a depth prepass for reverse-Z HZB occlusion culling, use Greater compare (not Always) — the closest fragment must win so the HZB stores the nearest occluding surface, not the farthest
استنادا إلى تصنيف SOC المهني
| name | frame-graph-ron-ordering-authoritative |
| description | When Titan frame-graph pass-ordering validation rules conflict with RON config files, RON configs are the authoritative source — fix the validation rule to match the RON |
| source | auto-skill |
| extracted_at | 2026-06-15T20:25:00.000Z |
When adding ordering validation rules to Titan's frame-graph builder
(titan-rendering-frame-graph/src/lib.rs), the RON config files
(crates/titan-rendering-frame-graph/configs/pipeline_*.ron) are the
source of truth for pass ordering.
Rule: If a new validation rule contradicts an existing RON config, fix the validation rule, not the RON. The RONs are the committed, working pipeline configurations — validation exists to enforce them, not to redefine them.
Why: During VSM Phase 2, the plan specified that StratumVisibleLightHash
must precede StratumVsmRasterize. But both High-tier RONs had
StratumVsmRasterize BEFORE StratumVisibleLightHash. The RONs were
correct — VSM rasterize writes the physical pool depth that shading
eventually reads, so it must complete before the light-hash gates
shading. The validation rule was fixed to match the RONs.
How to apply: Before adding a frame-graph ordering rule:
Catch the conflict early: Ordering conflicts surface as test
failures in cargo test -p titan-rendering-frame-graph --lib. If a
new validation rule causes existing tests to fail, the RON configs
(or test fixtures derived from them) disagree with the rule.
