CtrlK
BlogDocsLog inGet started
Tessl Logo

uinaf/viteplus

Migrate or align frontend repositories to the stock VitePlus workflow. Use when standardizing package or monorepo repos around `vp`, `voidzero-dev/setup-vp`, `vite-plus/test`, and VitePlus-native CI, test, and packaging flows, including updating scripts, test config, CI setup, and packaging commands.

94

2.63x
Quality

94%

Does it follow best practices?

Impact

95%

2.63x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

testing.mdreferences/

Testing

Use this reference when migrating tests to VitePlus-native usage.

Defaults

  • Prefer imports from vite-plus/test over direct vitest imports when migrating to VitePlus.
  • Move coverage and test-command wiring together with script updates.
  • Verify both the default test pass and any coverage mode the repo actually depends on.
  • Use vp test rather than attempting to invoke Vitest through a made-up subcommand.

Caveat

At the time this skill was written, adding @vitest/coverage-v8 to a VitePlus project can still produce a mixed-version warning during vp test --coverage, even in a fresh stock scaffold. Treat that as a VitePlus limitation to verify and document, not as an automatic repo regression.

SKILL.md

tile.json