vneskills

Shared Cursor / Claude Code skills for the VertexNova 3D visualization stack: window, GPU (vnerhi), shaders (vneshaderc), scene (vnegfx), XR (vnexr), and Gaussian splatting (vne3dgs).

A visualization change is finished when the picture is right, or when a CPU check proves the data that feeds the picture. Compiling is not that check.

Install

Install both plugins. pstack owns generic engineering rigor; this plugin owns VertexNova visualization playbooks.

/add-plugin pstack
/add-plugin vneskills

Or clone next to the other VertexNova checkouts and point Cursor at this directory:

git clone https://github.com/vertexnova/vneskills.git ../vneskills

As a submodule (preferred in VertexNova libraries)

In each library, delete the old shared skill copies and add this repo under skills/vneskills:

git submodule add https://github.com/vertexnova/vneskills.git skills/vneskills
git submodule update --init skills/vneskills

Keep only domain skills next to the submodule (for example vne-xr-session in vnexr). Symlink for Claude Code:

mkdir -p .claude/skills
for s in skills/vneskills/skills/*/; do
  ln -sfn "../../../$s" ".claude/skills/$(basename "$s")"
done
for s in skills/*/; do
  name=$(basename "$s")
  [ "$name" = "vneskills" ] && continue
  ln -sfn "../../$s" ".claude/skills/$name"
done

Claude Code: you can also install as a marketplace plugin when published.

Get started

Type /vne-mode at the start of visualization work. It detects the current repo (vnerhi, vnegfx, vnexr, vnewindow, vne3dgs, ...) and routes to the matching playbooks.

For investigation, refactor, overnight landing, or PR babysit, use pstack's /poteto-mode. Do not reimplement those playbooks here.

Skills

Skill	Use when
vne-mode	Default entry for visualization tasks
plain-ascii-authoring	Any authored text or source
vne-coding-style	Writing or editing C++ / Objective-C++
vne-header-hygiene	Editing includes or creating headers
vne-testing	Adding or changing GoogleTest coverage
vne-build-verify	Format, build, run, test before finishing
vne-frame	Naming frame inputs before editing a pass
vne-picture-check	Proving the picture or the data behind it
vne-cross-repo	Public API or binding changes across repos
vne-gpu-benchmark	Claiming a GPU speedup or regression
vne-backend-matrix	Shader or binding changes across backends

Domain skills that name concrete paths stay in each library repo (for example vne-shader-pipeline in vnerhi / vnegfx, vne-xr-session in vnexr). /vne-mode opens the local skill when present.

Use with pstack (no local copy)

/poteto-mode, /how, /why, /teach, /interrogate, /tdd, /no-comments, /technical-writing, /show-me-your-work, /reflect, /correct.

Doxygen on non-obvious public APIs stays. /no-comments does not strip @brief / @param / @return.

Self-check

rg -nP "[^\x00-\x7F]" skills README.md plugin.json

A clean run prints nothing.

License

Apache-2.0. See LICENSE.