Frontend VitePlus

Use this skill to move a frontend repo closer to the stock VitePlus toolchain without blindly deleting repo-specific release or runtime logic.

Workflow

1. Inspect the repo's current scripts, workflows, Vite config, test imports, release flow, and package manager.
2. Read references/bootstrap.md when creating a new repo or running vp migrate.
3. Read references/packages.md for standalone package repos.
4. Read references/monorepos.md for workspace repos.
5. Read references/ci-cd.md before changing GitHub Actions or release automation.
6. Read references/testing.md before migrating test imports, coverage, or test commands.
7. For Git hooks, prefer the stock vp config plus staged block flow documented by VitePlus instead of hand-rolled hook scaffolding.
8. Keep repo-specific binary, release, or packaging steps only where VitePlus does not replace them cleanly.
9. Prefer one coherent migration: scripts, workflows, and test surface should move together.
10. Verify with repo-native guardrails, then prove the important runtime surface still works.

Guardrails