vertexnova/vneskills
VertexNova skills for 3D visualization: frames, shaders, backends, XR, and the picture on screen. Pair with pstack for generic rigor; type /vne-mode for visualization work.
Keep all authored code, comments, docs, commit messages, and PR text free of AI-generated symbols and stock AI phrasing. Use this skill whenever you write or edit any text or source in a VertexNova repository.
List which GPU backends a shader, binding, or resource change must hit (Vulkan, Metal, WebGPU, Null). Use when editing pipelines, descriptors, swapchains, or cross-compiled shaders.
Standard format, build, run, and test pipeline for VertexNova libraries. Use before finishing a C++, Objective-C++, shader, or packaging change. Detect the git toplevel name and follow the matching row in repos.md.
Enforce VertexNova C++ and Objective-C++ conventions (naming, formatting, initialization, modern C++). Use this skill when writing or modifying any code under src/, include/, samples/, examples/, or tests/ in a VertexNova library.
Map blast radius across VertexNova repos when changing a public API, C API, native window handle, or shader bundle. Use before editing interfaces that other libraries or bindings consume.
Name the frame inputs (camera, lights, per-pass GPU struct, bindings, target texture) before editing a pass, shader, material, or swapchain path. Use when changing rendering, volume, mesh, OIT, picking, CSG, splat, or XR view draws.
Vet a GPU speedup or regression before reporting it. Same scene, camera, and resolution; warmup; repeat; name the limiter (submit, bandwidth, overdraw, or the pass). Use for volume isosurface, splat sort, OIT, or any frame-time claim.
Enforce include ordering, header self-containment, and forward-declaration rules. Use this skill when adding or editing #include / #import directives or creating C++ / Objective-C++ headers in a VertexNova repository.
Default entry for VertexNova 3D visualization work. Detects the current repo and routes to frame, picture-check, backend-matrix, cross-repo, build-verify, and local domain skills. Use at the start of pass, shader, GPU, XR, or sample tasks. For investigation, refactor, overnight landing, or PR babysit, use pstack /poteto-mode instead.
Prove a visualization change: descriptor or matrix test when the bug is data; image goldens when present; otherwise run a named sample on one real backend. Use before declaring a rendering, shader, XR, or sample change done.
Conventions for writing and organizing GoogleTest tests in VertexNova libraries, including backend-gated and null-backend tests. Use this skill when adding or changing tests, or when a behavior change needs test coverage.