vite-plus-best-practiceslisted
Install: claude install-skill Firzus/agent-skills
# Vite+ Best Practices
Apply these rules when setting up, writing, reviewing, or migrating a Vite+ project — configuring `vite.config.ts`, running `vp` commands, or wiring Vite+ into CI / coding agents.
**Done when:** every touched package uses `vite-plus` / `vite-plus/test` imports where required (exceptions: non-config `vite` imports via the core alias; `@nuxt/test-utils` packages keeping upstream `vitest`; pnpm direct `vite` entries aliased to core — leave those); no legacy per-tool config remains unless a documented exception applies; upgrade/migrate followed the `vp migrate` path; and `vp check && vp test` plus `vp build` (apps) or `vp pack` (libs/CLIs) pass.
Vite+ is a **unified toolchain**: one CLI and one config file replace the usual split of Vite, Vitest, ESLint/Oxlint, Prettier/Oxfmt, tsdown, lint-staged, and a task runner.
| Part | What it is | Scope |
|------|-----------|-------|
| `vp` | Global CLI + managed Node.js / package-manager runtime | Per machine |
| `vite-plus` | Local package installed in each project | Per project |
## Setup
Fastest path to a working project. Full details in [setup.md](./setup.md) (install, env, deps, create, upgrade).
```bash
# 1. Install the global vp CLI (once per machine)
curl -fsSL https://vite.plus | bash # macOS / Linux
irm https://vite.plus/ps1 | iex # Windows (PowerShell)
# 2. Open a NEW shell, then verify
vp help
# 3a. New project
vp create # interactive scaffold
vp inst