Vitexec
Testing & QualityvitexecVitexec is an Agent Skill for testing & quality published in the pmndrs/uikit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use this skill when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured artifacts. Use for client state after interactions, imported app modules, DOM state, human-like input, canvas/WebGL/Three.js state, screenshots, videos, CPU/network/performance/heap analysis, WebXR/Three.js XR with IWER, and runtime-only behavior without editing app files.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/pmndrs/uikit/blob/HEAD/.agents/skills/vitexec/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vitexec, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
vitexec
Use vitexec when the truth lives in the running browser: client state, imported app modules, DOM, canvas/WebGL, screenshots, recordings, or browser-only errors.
Do not use it for questions static files, unit tests, or TypeScript can answer directly.
References
- If
vitexecor Playwright is missing, read references/install.md. - For mouse, keyboard, pointer lock, gamepad, or other input, read references/inputs.md.
- For CPU, network, performance timeline, or heap analysis, read references/performance.md.
- For WebXR, read references/webxr.md.
Workflow
- Identify the page path if it is not
/. - Write the smallest snippet that performs the user-like action or reads the browser-only state.
- Run
vitexec '<snippet>', adding--path,--gpu,--screenshot,--record,--cpu-profile,--network-trace,--performance-trace,--heap-snapshot,--timeout, or--configonly when needed. - Treat stdout as browser logs. It starts with
logs:.
vitexec 'console.log("ready")'
For structured state, log JSON:
vitexec --path /cart '
import { useCartStore } from "/src/store/cart.ts";
document.querySelector("[data-testid=add-to-cart]")?.click();
await new Promise((resolve) => requestAnimationFrame(resolve));
console.log("cart", JSON.stringify(useCartStore.getState()));
'
Guidance
- Prefer importing exported app state over scraping DOM when state is available.
- Use direct state reads for observation and assertions, not to bypass user interaction.
- Use live progress logs and focused assertions to early-exit on failures and see current progress.
- Keep logs concise; overly verbose logs become unreadable and unnecessarily fill the context.
- Prefer browser-root imports such as
/src/store.ts, not local filesystem paths. - Use
--gpufor WebGL, canvas, Three.js, and WebXR behavior. - Use screenshots or recordings only when visual evidence matters.
- Do not leave temporary code in the app when
vitexeccan inspect it from outside.