Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
95
Does it follow best practices?
Validation for skill structure
Vite 8 library mode configuration
TypeScript config file
100%
100%
ESM syntax in config
100%
100%
Uses defineConfig
100%
100%
rolldownOptions used
0%
100%
import.meta.dirname for entry
0%
100%
Peer deps externalized
55%
100%
package.json type module
100%
100%
package.json module field
100%
100%
package.json main field
77%
100%
package.json exports map
100%
100%
package.json files field
100%
100%
Without context: $0.1790 · 33s · 11 turns · 11 in / 1,999 out tokens
With context: $0.3029 · 45s · 16 turns · 17 in / 2,210 out tokens
Vite plugin authoring conventions
virtual: prefix for user-facing id
0%
100%
\0 prefix for resolved id
100%
100%
resolveId returns resolved id
100%
100%
load returns module content
100%
100%
enforce property used
100%
100%
apply property used
0%
100%
Plugin is a factory function
100%
100%
TypeScript or ESM
100%
100%
configureServer uses return function
100%
100%
Plugin name property
100%
100%
Without context: $0.2220 · 56s · 11 turns · 11 in / 3,289 out tokens
With context: $0.2486 · 39s · 14 turns · 13 in / 2,058 out tokens
Vite 7 to 8 config migration
rollupOptions renamed
0%
100%
No rollupOptions remaining
0%
100%
esbuild option renamed
0%
100%
No esbuild option remaining
100%
100%
JSX pragma migrated
0%
100%
JSX fragment migrated
0%
100%
oxc.jsx.runtime specified
0%
100%
Gradual migration step mentioned
0%
100%
TypeScript config file
100%
100%
ESM syntax in config
100%
100%
Without context: $0.2061 · 59s · 10 turns · 10 in / 3,134 out tokens
With context: $0.2115 · 38s · 11 turns · 11 in / 2,129 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.