Use this skill when working with Vite+, vp CLI, or the VoidZero unified toolchain. Triggers on project scaffolding with vp create, migrating existing Vite projects with vp migrate, running dev/build/test/lint/fmt commands, configuring vite.config.ts with lint/fmt/test/run/pack/staged blocks, managing Node.js versions with vp env, monorepo task execution with vp run, and library packaging with vp pack. Also triggers on references to Oxlint, Oxfmt, Rolldown, tsdown, Vitest, or Vite Task in a Vite+ context.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Use this skill when working with Vite+, vp CLI, or the VoidZero unified toolchain. Triggers on project scaffolding with vp create, migrating existing Vite projects with vp migrate, running dev/build/test/lint/fmt commands, configuring vite.config.ts with lint/fmt/test/run/pack/staged blocks, managing Node.js versions with vp env, monorepo task execution with vp run, and library packaging with vp pack. Also triggers on references to Oxlint, Oxfmt, Rolldown, tsdown, Vitest, or Vite Task in a Vite+ context.
[{"url":"https://viteplus.dev/guide/","accessed":"2026-03-14T00:00:00.000Z","description":"Main guide covering all CLI commands and workflows"},{"url":"https://viteplus.dev/config/","accessed":"2026-03-14T00:00:00.000Z","description":"Configuration reference for all vite.config.ts blocks"}]
license
MIT
maintainers
[{"github":"maddhruv"}]
When this skill is activated, always start your first response with the 🧢 emoji.
Vite+
Vite+ is the unified toolchain for web development by VoidZero. It consolidates
the dev server (Vite), bundler (Rolldown), test runner (Vitest), linter (Oxlint),
formatter (Oxfmt), task runner (Vite Task), and library packager (tsdown) into a
single CLI called vp. It also manages Node.js versions and package managers
globally, replacing the need for nvm, fnm, or Corepack.
When to use this skill
Trigger this skill when the user:
Wants to scaffold a new project or monorepo with vp create
Needs to migrate an existing Vite/Vitest project to Vite+
Asks about vp dev, vp build, vp test, vp lint, vp fmt, or vp check
Configures vite.config.ts with lint, fmt, test, run, pack, or staged blocks
Runs monorepo tasks with vp run -r or workspace filtering
Packages a library with vp pack (tsdown integration)
Manages Node.js versions with vp env
References the vp or vpx CLI commands
Do NOT trigger this skill for:
Plain Vite (without Vite+) configuration - use standard Vite docs instead
Vitest standalone usage without Vite+ wrapping
Setup & authentication
Installation
# macOS / Linux
curl -fsSL https://vite.plus | bash
# Windows (PowerShell)
irm https://vite.plus/ps1 | iex
Basic project setup
# Interactive project creation
vp create
# Create from a specific template
vp create vite -- --template react-ts
# Monorepo
vp create vite:monorepo
# Migrate existing Vite project
vp migrate
Configuration
All tool configuration lives in a single vite.config.ts:
Vite+ ships as two pieces: vp (global CLI) and vite-plus (local project
package). The global CLI handles runtime management and project scaffolding.
The local package provides the defineConfig function and all tool integrations.
Unified config model - instead of separate config files for each tool
(vitest.config.ts, .oxlintrc.json, .prettierrc), everything consolidates
into vite.config.ts. Do not create separate config files for Oxlint, Oxfmt,
Vitest, or tsdown when using Vite+.
Command surface - vp wraps each integrated tool behind a consistent CLI.
vp dev and vp build run standard Vite. vp test runs Vitest (single-run by
default, unlike standalone Vitest which defaults to watch). vp check runs
fmt + lint + typecheck in one pass using Oxfmt, Oxlint, and tsgolint.
Environment management - Vite+ manages Node.js installations in
~/.vite-plus. In managed mode (default), shims always use the Vite+-managed
Node.js. Use vp env off to switch to system-first mode. Pin project versions
with vp env pin which writes a .node-version file.
vp dev # Start Vite dev server with HMR
vp build # Production build via Rolldown
vp preview # Serve production build locally
vp build --watch --sourcemap # Watch mode with source maps
vp build always runs the built-in Vite build. If your package.json has a custom build script, use vp run build instead.
Lint, format, and type-check
vp check # Format + lint + type-check in one pass
vp check --fix # Auto-fix formatting and lint issues
vp lint # Lint only (Oxlint)
vp lint --fix # Lint with auto-fix
vp fmt# Format only (Oxfmt)
vp fmt --check # Check formatting without writing
The exe option builds standalone executables for CLI tools.
Execute monorepo tasks
vp run build # Run build script in current package
vp run build -r # Run across all workspace packages (dependency order)
vp run build -t # Run in package + all its dependencies
vp run build --filter "my-app"# Filter by package name
vp run build -v # Verbose with cache stats
Tasks in vite.config.ts are cached by default. Package.json scripts are not - use --cache to enable.
Manage Node.js versions
vp env pin 22 # Pin project to Node 22 (.node-version)
vp env default 22 # Set global default
vp env install 22 # Install a Node.js version
vp env current # Show resolved environment
vp env on / vp env off # Toggle managed vs system-first mode
vp env doctor # Run diagnostics
Error handling
Error
Cause
Resolution
vp: command not found
Vite+ not installed or shell not reloaded
Run the install script and restart terminal, or run vp env print and add the output to shell config
vp build runs custom script instead of Vite build
package.json has a build script
Use vp build for Vite build, vp run build for the package.json script
Type-aware lint rules not working
typeAware / typeCheck not enabled
Set lint.options.typeAware: true and lint.options.typeCheck: true in config
vp test stays in watch mode
Standalone Vitest habit
vp test is single-run by default; use vp test watch for watch mode
Migration leaves broken imports
Incomplete vp migrate
Run vp install, then vp check to catch remaining import issues
Gotchas
vp build and vp run build are different commands - vp build always invokes the built-in Vite build regardless of package.json scripts. vp run build executes the build script in package.json. If your project has a custom build script that wraps Vite with additional steps, use vp run build. Using vp build will skip those steps silently.
Separate config files for Vitest/Oxlint/Oxfmt will conflict with Vite+ config - Vite+ reads all tool configuration exclusively from vite.config.ts. If a vitest.config.ts, .oxlintrc.json, or .prettierrc exists alongside it, the behavior is undefined and tools may use conflicting settings. Remove separate configs entirely when migrating to Vite+.
vp test is single-run by default, unlike standalone Vitest - Developers migrating from standalone Vitest expect watch mode. Running vp test in CI is correct; running it locally for development requires vp test watch. This is the opposite of Vitest's default behavior.
vp migrate does not update import paths for tool-specific APIs - The migration command handles config consolidation but does not rewrite imports like import { defineConfig } from 'vitest/config' to import { defineConfig } from 'vite-plus'. Remaining broken imports will surface as type errors after migration; run vp check to find them.
Node.js managed mode intercepts all node calls, including CI scripts - In managed mode (default), the Vite+ shim is at the front of PATH. CI environments with pre-installed Node.js may behave unexpectedly. Run vp env doctor to verify the resolved environment and use vp env off to switch to system-first mode in CI if needed.
References
For detailed configuration options and advanced usage, read these files:
references/config.md - full configuration reference for all vite.config.ts blocks (lint, fmt, test, run, pack, staged)
references/env-management.md - Node.js version management and runtime modes
references/task-runner.md - monorepo task execution, caching, and dependency ordering
Only load a references file if the current task requires it - they consume context.
Companion check
On first activation of this skill in a conversation: check which companion skills are installed by running ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/ .claude/skills/ .agent/skills/ .agents/skills/ 2>/dev/null. Compare the results against the recommended_skills field in this file's frontmatter. For any that are missing, mention them once and offer to install:
