菜单
When QWEN.md auto-memory format/completeness keeps failing, close the gap with a PreToolUse hook that checks frontmatter (name/description/type) and MEMORY.md indexing — same pattern as todo_gate_guard
用 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 | memory-guard |
| description | When QWEN.md auto-memory format/completeness keeps failing, close the gap with a PreToolUse hook that checks frontmatter (name/description/type) and MEMORY.md indexing — same pattern as todo_gate_guard |
| source | auto-skill |
When auto-memory format violations (missing frontmatter, unindexed files in MEMORY.md) are a recurring problem, or when the user asks for mechanical enforcement of the memory discipline from QWEN.md.
The hook lives at .qwen/local-scripts/memory_guard.py with tests at .qwen/local-scripts/test_memory_guard.py. It's a PreToolUse hook on Write/Edit to files under ~/.qwen/projects/ or ~/.qwen/memories/.
Frontmatter — every .md file in a memory subdirectory must have ---\nname:\ndescription:\ntype:\n---. The type: field must be one of user, feedback, project, reference.
MEMORY.md indexing — when writing MEMORY.md itself, all .md files in the memory subtree must have a one-line - [Title](file.md) — description pointer in the index. File writes without a MEMORY.md write are NOT blocked (the user can update MEMORY.md next). The MEMORY.md write gate ensures completeness.
~/.qwen/projects/ and ~/.qwen/memories/_memory_files_in_dir() walks the directory tree finding .md files (excluding MEMORY.md)_indexed_files() parses MEMORY.md extracting ](file.md) references_check_frontmatter() validates the --- frontmatter block fieldsdocs/TODO.md doesn't exist, allow (infrastructure error shouldn't block)Tests create temp directories with .qwen/memory/MEMORY.md and memory files, mocking _find_project_root to point at the temp dir. Key test cases:
The QWEN.md memory discipline (one lesson per file, frontmatter, MEMORY.md index) is a recurring failure point because it requires the agent to remember a multi-step protocol that has no mechanical enforcement. A PreToolUse hook catches the violation at the point it happens (Write/Edit to a memory file), same as todo_gate_guard catches TODO omissions at the Write/Edit point.