القائمة
Before declaring any Titan work complete, run the 4-command CI gate — cargo check, fmt, clippy, nextest — and verify zero warnings outside vendored crates
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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
| name | validation-ci-gate |
| description | Before declaring any Titan work complete, run the 4-command CI gate — cargo check, fmt, clippy, nextest — and verify zero warnings outside vendored crates |
| source | auto-skill |
Before declaring any Titan implementation work complete, committing, or pushing. This is the local CI gate that must pass before work is considered done.
cargo check --workspace --all-targets
cargo fmt --all -- --check
cargo clippy --workspace --exclude joltc-sys --exclude rolt --all-targets --no-deps -- -D warnings
cargo nextest run --workspace --exclude joltc-sys --exclude rolt
crates/third_party/) may carry warnings. Any warning in crates/titan-*/ or tools/titan-*/ must be fixed before declaring work complete.cargo test may not properly exercise all golden-pinned tests).-D warnings. This converts all clippy warnings to hard errors. No #[allow(...)] exceptions without justification.Recurring problem: work is declared complete but fails CI because of un-run clippy warnings, golden-file drift, or test breakage in crates the agent didn't think to check. The 4-command gate catches this at the point of declaration, not at the CI server.