vgpu

Build, debug, and optimize WebGPU projects using version-matched vgpu CLI documentation.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill vgpu-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vgpu
Source: https://github.com/Chia1104/agent-air/tree/main/skills/shared/vgpu
Command: npx skills add https://github.com/Chia1104/agent-air --skill vgpu-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? WebGPU projects pinned to a specific vgpu version often break when developers rely on remembered APIs, hosted docs, or the latest release notes. This Skill ensures every API answer, migration step, and debugging workflow comes from the documentation bundled with the exact vgpu package installed in the target project. ## Core Features & Use Cases - Version-Safe Resolution: Detects the project-local vgpu version via package manifests, lockfiles, and no-install CLI invocations like pnpm exec vgpu --version, avoiding accidental downloads from bare npx or bunx. - Bundled Docs Routing: Queries the local CLI's docs corpus with docs ls, docs cat, docs find, and docs grep so answers always match the installed version. - Guided Upgrades: Records the previous version, reads intervening migration guides in order via docs ls /migrations, and reports missing guides instead of substituting current hosted docs. - Use Case: When upgrading a WebGPU app from one vgpu release to another, the Skill walks each migration guide for the authorized target version and verifies changes step by step. ## Quick Start Ask the assistant to check the vgpu version installed in this project and explain how to set up a WebGPU render pipeline using that version's bundled documentation.

Frequently Asked Questions about vgpu

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which vgpu version my project uses?▼

Run the project-local executable with a no-install command such as `pnpm exec vgpu --version` or `npm exec --no -- vgpu --version`. Check the package manifest and lockfile first, and avoid bare `npx vgpu` or `bunx vgpu`, which may download a missing package.

How do I read vgpu documentation for my installed version?▼

Use the local CLI's docs commands: `docs ls` lists pages, `docs cat` reads a page, `docs find` searches topics or symbols, and `docs grep` searches within pages. These serve the corpus bundled with your installed version, not hosted docs.

Can I use npx vgpu to discover my local version?▼

No. Bare `npx vgpu` may download the package if it is missing, and npm's `--offline` flag can still install from cache. Use `npm exec --no -- vgpu` or an already resolved `node_modules/.bin/vgpu` binary instead.

How do I upgrade a project to a newer vgpu version?▼

Record the previous version first, then run `docs ls /migrations` through the target version's local CLI and read each intervening migration guide in order. If older packages lack bundled guides, consult that exact release's notes rather than current hosted docs.

What if the installed vgpu docs do not contain an API I need?▼

Do not invent the API or silently switch versions. Report the mismatch to the user and only change versions when the task explicitly authorizes it, since the bundled docs are the authority for that project.