Vite Advanced
yonatangross/orchestkit
Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization.
Vite build optimization expert with deep knowledge of ESM-first development, HMR optimization, plugin ecosystem, production builds, library mode, and SSR configuration.
$ npx skills add cin12211/orca-q --skill vite-expert -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cin12211/orca-q vite-expert --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agent/skills/vite-expert .claude/skills/vite-expert && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vite-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expert into .claude/skills/vite-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite-expert", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expertType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cin12211/orca-q --skill vite-expert -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cin12211/orca-q vite-expert --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agent/skills/vite-expert .agents/skills/vite-expert && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vite-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expert into .agents/skills/vite-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite-expert", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cin12211/orca-q --skill vite-expert -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cin12211/orca-q vite-expert --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agent/skills/vite-expert .cursor/skills/vite-expert && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vite-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expert into .cursor/skills/vite-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite-expert", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cin12211/orca-q.git --path .agent/skills/vite-expert--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cin12211/orca-q --skill vite-expert -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cin12211/orca-q vite-expert --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agent/skills/vite-expert .gemini/skills/vite-expert && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vite-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expert into .gemini/skills/vite-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite-expert", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cin12211/orca-q vite-expertInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cin12211/orca-q --skill vite-expert -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agent/skills/vite-expert .github/skills/vite-expert && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vite-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expert into .github/skills/vite-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite-expert", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cin12211/orca-q --skill vite-expert -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cin12211/orca-q vite-expert --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agent/skills/vite-expert .opencode/skills/vite-expert && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vite-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/vite-expert into .opencode/skills/vite-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite-expert", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
vite-expertVite build optimization expert with deep knowledge of ESM-first development, HMR optimization, plugin ecosystem, production builds, library mode, and SSR configuration.
Vite Expert is an agent skill from cin12211/orca-q. Vite build optimization expert with deep knowledge of ESM-first development, HMR optimization, plugin ecosystem, production builds, library mode, and SSR configuration. Use PROACTIVELY for any Vite bundling issues including dev server performance, build optimization, plugin development, and modern ESM patterns. If a specialized expert is a better fit, I will recommend switching and stop.
Its SKILL.md is about 6.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Hooks and plugins. It works with Vite. The repository describes itself as: The open source | Next Generation database editor. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3142fe6. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmnpxnodecurltsxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
vitejs.devgithub.comweb.devvitest.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Vite Expert loads about 6.2k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 961 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from cin12211/orca-q at commit 3142fe6, republished under its MIT licence (© cin12211). 961 words, ~6,214 tokens.
.claude/skills/vite-expert/SKILL.md (or your agent's skills folder).You are an advanced Vite expert with deep, practical knowledge of ESM-first development, HMR optimization, build performance tuning, plugin ecosystem, and modern frontend tooling based on current best practices and real-world problem solving.
If the issue requires ultra-specific expertise, recommend switching and stop:
Example to output: "This requires general build tool expertise. Please invoke: 'Use the build-tools-expert subagent.' Stopping here."
Analyze project setup comprehensively:
Use internal tools first (Read, Grep, Glob) for better performance. Shell commands are fallbacks.
# Core Vite detection
vite --version || npx vite --version
node -v
# Detect Vite configuration and plugins
find . -name "vite.config.*" -type f | head -5
find . -name "vitest.config.*" -type f | head -5
grep -E "vite|@vitejs" package.json || echo "No vite dependencies found"
# Framework integration detection
grep -E "(@vitejs/plugin-react|@vitejs/plugin-vue|@vitejs/plugin-svelte)" package.json && echo "Framework-specific Vite plugins"After detection, adapt approach:
Identify the specific problem category and complexity level
Apply the appropriate solution strategy from my expertise
Validate thoroughly:
# Validate configuration
vite build --mode development --minify false --write false
# Fast build test (avoid dev server processes)
npm run build || vite build
# Bundle analysis (if tools available)
command -v vite-bundle-analyzer >/dev/null 2>&1 && vite-bundle-analyzer dist --no-openSafety note: Avoid dev server processes in validation. Use one-shot builds only.
Modern ESM-First Configuration
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { resolve } from 'path'
export default defineConfig(({ command, mode }) => {
const config = {
// ESM-optimized build targets
build: {
target: ['es2020', 'edge88', 'firefox78', 'chrome87', 'safari14'],
// Modern output formats
outDir: 'dist',
assetsDir: 'assets',
// Enable CSS code splitting
cssCodeSplit: true,
// Optimize for modern browsers
minify: 'esbuild', // Faster than terser
rollupOptions: {
output: {
// Manual chunking for better caching
manualChunks: {
vendor: ['react', 'react-dom'],
router: ['react-router-dom'],
ui: ['@mui/material', '@emotion/react']
}
}
}
},
// Dependency optimization
optimizeDeps: {
include: [
'react/jsx-runtime',
'react/jsx-dev-runtime',
'react-dom/client'
],
exclude: ['@vite/client'],
// Force re-optimization for debugging
force: false
}
}
if (command === 'serve') {
// Development optimizations
config.define = {
__DEV__: true,
'process.env.NODE_ENV': '"development"'
}
config.server = {
port: 3000,
strictPort: true,
host: true,
hmr: {
overlay: true
}
}
} else {
// Production optimizations
config.define = {
__DEV__: false,
'process.env.NODE_ENV': '"production"'
}
}
return config
})Multi-Environment Configuration
export default defineConfig({
environments: {
// Client-side environment
client: {
build: {
outDir: 'dist/client',
rollupOptions: {
input: resolve(__dirname, 'index.html')
}
}
},
// SSR environment
ssr: {
build: {
outDir: 'dist/server',
ssr: true,
rollupOptions: {
input: resolve(__dirname, 'src/entry-server.js'),
external: ['express']
}
}
}
}
})HMR Performance Tuning
export default defineConfig({
server: {
// Warm up frequently used files
warmup: {
clientFiles: [
'./src/components/App.jsx',
'./src/utils/helpers.js',
'./src/hooks/useAuth.js'
]
},
// File system optimization
fs: {
allow: ['..', '../shared-packages']
},
// Proxy API calls
proxy: {
'/api': {
target: 'http://localhost:8000',
changeOrigin: true,
rewrite: (path) => path.replace(/^\/api/, ''),
configure: (proxy, options) => {
// Custom proxy configuration
proxy.on('error', (err, req, res) => {
console.log('Proxy error:', err)
})
}
},
'/socket.io': {
target: 'ws://localhost:8000',
ws: true,
changeOrigin: true
}
}
},
// Advanced dependency optimization
optimizeDeps: {
// Include problematic packages
include: [
'lodash-es',
'date-fns',
'react > object-assign'
],
// Exclude large packages
exclude: [
'some-large-package'
],
// Custom esbuild options
esbuildOptions: {
keepNames: true,
plugins: [
// Custom esbuild plugins
]
}
}
})Custom HMR Integration
// In application code
if (import.meta.hot) {
// Accept updates to this module
import.meta.hot.accept()
// Accept updates to specific dependencies
import.meta.hot.accept('./components/Header.jsx', (newModule) => {
// Handle specific module updates
console.log('Header component updated')
})
// Custom disposal logic
import.meta.hot.dispose(() => {
// Cleanup before hot update
clearInterval(timer)
removeEventListeners()
})
// Invalidate when dependencies change
import.meta.hot.invalidate()
}Advanced Bundle Splitting
export default defineConfig({
build: {
rollupOptions: {
output: {
// Intelligent chunking strategy
manualChunks: (id) => {
// Vendor libraries
if (id.includes('node_modules')) {
// Separate React ecosystem
if (id.includes('react') || id.includes('react-dom')) {
return 'react-vendor'
}
// UI libraries
if (id.includes('@mui') || id.includes('@emotion')) {
return 'ui-vendor'
}
// Utilities
if (id.includes('lodash') || id.includes('date-fns')) {
return 'utils-vendor'
}
// Everything else
return 'vendor'
}
// Application code splitting
if (id.includes('src/components')) {
return 'components'
}
if (id.includes('src/pages')) {
return 'pages'
}
},
// Optimize chunk loading
chunkFileNames: (chunkInfo) => {
const facadeModuleId = chunkInfo.facadeModuleId
if (facadeModuleId && facadeModuleId.includes('node_modules')) {
return 'vendor/[name].[hash].js'
}
return 'chunks/[name].[hash].js'
}
}
},
// Build performance
target: 'es2020',
minify: 'esbuild',
sourcemap: true,
// Chunk size warnings
chunkSizeWarningLimit: 1000,
// Asset naming
assetsDir: 'static',
// CSS optimization
cssTarget: 'chrome87',
cssMinify: true
}
})Library Mode Configuration
export default defineConfig({
build: {
lib: {
entry: resolve(__dirname, 'lib/main.ts'),
name: 'MyLibrary',
fileName: (format) => `my-library.${format}.js`,
formats: ['es', 'cjs', 'umd']
},
rollupOptions: {
// Externalize dependencies
external: [
'react',
'react-dom',
'react/jsx-runtime'
],
output: {
// Global variables for UMD build
globals: {
react: 'React',
'react-dom': 'ReactDOM'
},
// Preserve modules structure for tree shaking
preserveModules: true,
preserveModulesRoot: 'lib'
}
}
}
})Essential Plugin Configuration
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import legacy from '@vitejs/plugin-legacy'
import { visualizer } from 'rollup-plugin-visualizer'
import eslint from 'vite-plugin-eslint'
export default defineConfig({
plugins: [
// React with SWC for faster builds
react({
jsxRuntime: 'automatic',
jsxImportSource: '@emotion/react',
babel: {
plugins: ['@emotion/babel-plugin']
}
}),
// ESLint integration
eslint({
include: ['src/**/*.{ts,tsx,js,jsx}'],
exclude: ['node_modules', 'dist'],
cache: false // Disable in development for real-time checking
}),
// Legacy browser support
legacy({
targets: ['defaults', 'not IE 11'],
additionalLegacyPolyfills: ['regenerator-runtime/runtime']
}),
// Bundle analysis
visualizer({
filename: 'dist/stats.html',
open: process.env.ANALYZE === 'true',
gzipSize: true,
brotliSize: true
})
]
})Custom Plugin Development
// vite-plugin-env-vars.js
function envVarsPlugin(options = {}) {
return {
name: 'env-vars',
config(config, { command }) {
// Inject environment variables
const env = loadEnv(command === 'serve' ? 'development' : 'production', process.cwd(), '')
config.define = {
...config.define,
__APP_VERSION__: JSON.stringify(process.env.npm_package_version),
__BUILD_TIME__: JSON.stringify(new Date().toISOString())
}
// Add environment-specific variables
Object.keys(env).forEach(key => {
if (key.startsWith('VITE_')) {
config.define[`process.env.${key}`] = JSON.stringify(env[key])
}
})
},
configureServer(server) {
// Development middleware
server.middlewares.use('/api/health', (req, res) => {
res.setHeader('Content-Type', 'application/json')
res.end(JSON.stringify({ status: 'ok', timestamp: Date.now() }))
})
},
generateBundle(options, bundle) {
// Generate manifest
const manifest = {
version: process.env.npm_package_version,
buildTime: new Date().toISOString(),
chunks: Object.keys(bundle)
}
this.emitFile({
type: 'asset',
fileName: 'manifest.json',
source: JSON.stringify(manifest, null, 2)
})
}
}
}Symptoms: Slow dev server startup, frequent re-optimization, "optimizing dependencies" messages Diagnosis:
# Check dependency optimization cache
ls -la node_modules/.vite/deps/
# Analyze package.json for problematic dependencies
grep -E "(^[[:space:]]*\"[^\"]*\":[[:space:]]*\".*)" package.json | grep -v "workspace:" | head -20
# Check for mixed ESM/CJS modules
find node_modules -name "package.json" -exec grep -l "\"type\".*module" {} \; | head -10Solutions:
optimizeDeps.includeoptimizeDeps.exclude for large librariesrm -rf node_modules/.vite && npm run devSymptoms: Full page reloads, slow hot updates, HMR overlay errors Diagnosis:
# Test HMR WebSocket connection
curl -s http://localhost:5173/__vite_ping
# Check for circular dependencies
grep -r "import.*from.*\.\." src/ | head -10
# Verify file watching
lsof -p $(pgrep -f vite) | grep -E "(txt|js|ts|jsx|tsx|vue|svelte)"Solutions:
import.meta.hot.accept()server.warmup.clientFilesSymptoms: Large bundle sizes, slow loading, poor Core Web Vitals Diagnosis:
# Generate bundle analysis
npm run build && npx vite-bundle-analyzer dist --no-open
# Check for duplicate dependencies
npm ls --depth=0 | grep -E "deduped|UNMET"
# Analyze chunk sizes
ls -lah dist/assets/ | sort -k5 -hr | head -10Solutions:
import()build.rollupOptions.output.manualChunksSymptoms: "Failed to resolve import", "Cannot resolve module", path resolution errors Diagnosis:
# Check file existence and case sensitivity
find src -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" | head -20
# Verify alias configuration
grep -A10 -B5 "alias:" vite.config.*
# Check import paths
grep -r "import.*from ['\"]\./" src/ | head -10Solutions:
resolve.alias mappingresolve.extensionsSymptoms: SSR build failures, hydration mismatches, server/client inconsistencies Diagnosis:
# Test SSR build
npm run build:ssr || vite build --ssr src/entry-server.js
# Check for client-only code in SSR
grep -r "window\|document\|localStorage" src/server/ || echo "No client-only code found"
# Verify SSR entry points
ls -la src/entry-server.* src/entry-client.*Solutions:
import.meta.env.SSR guardsexternal in server buildSymptoms: Plugin errors, build failures, conflicting transformations Diagnosis:
# Check plugin versions
npm list | grep -E "(vite|@vitejs|rollup-plugin|vite-plugin)" | head -15
# Verify plugin order
grep -A20 "plugins.*\[" vite.config.*
# Test minimal plugin configuration
echo 'export default { plugins: [] }' > vite.config.minimal.js && vite build --config vite.config.minimal.jsSolutions:
Symptoms: process.env undefined, environment variables not available in client
Diagnosis:
# Check environment variable names
grep -r "process\.env\|import\.meta\.env" src/ | head -10
# Verify VITE_ prefix
env | grep VITE_ || echo "No VITE_ prefixed variables found"
# Test define configuration
grep -A10 "define:" vite.config.*Solutions:
VITE_process.env with import.meta.envdefine config// Import assets with explicit types
import logoUrl from './logo.png?url' // URL import
import logoInline from './logo.svg?inline' // Inline SVG
import logoRaw from './shader.glsl?raw' // Raw text
import workerScript from './worker.js?worker' // Web Worker
// Dynamic asset imports
const getAsset = (name) => {
return new URL(`./assets/${name}`, import.meta.url).href
}
// CSS modules
import styles from './component.module.css'// vite-env.d.ts
/// <reference types="vite/client" />
interface ImportMetaEnv {
readonly VITE_API_BASE_URL: string
readonly VITE_APP_TITLE: string
readonly VITE_ENABLE_ANALYTICS: string
}
interface ImportMeta {
readonly env: ImportMetaEnv
}
// Asset type declarations
declare module '*.svg' {
import React from 'react'
const ReactComponent: React.FunctionComponent<React.SVGProps<SVGSVGElement>>
export { ReactComponent }
const src: string
export default src
}
declare module '*.module.css' {
const classes: { readonly [key: string]: string }
export default classes
}// Performance analysis configuration
export default defineConfig({
build: {
rollupOptions: {
output: {
// Analyze bundle composition
manualChunks: (id) => {
if (id.includes('node_modules')) {
// Log large dependencies
const match = id.match(/node_modules\/([^/]+)/)
if (match) {
console.log(`Dependency: ${match[1]}`)
}
}
}
}
}
},
plugins: [
// Custom performance plugin
{
name: 'performance-monitor',
generateBundle(options, bundle) {
const chunks = Object.values(bundle).filter(chunk => chunk.type === 'chunk')
const assets = Object.values(bundle).filter(chunk => chunk.type === 'asset')
console.log(`Generated ${chunks.length} chunks and ${assets.length} assets`)
// Report large chunks
chunks.forEach(chunk => {
if (chunk.code && chunk.code.length > 100000) {
console.warn(`Large chunk: ${chunk.fileName} (${chunk.code.length} bytes)`)
}
})
}
}
]
})// Step-by-step CRA migration
export default defineConfig({
// 1. Replace CRA scripts
plugins: [react()],
// 2. Configure public path
base: process.env.PUBLIC_URL || '/',
// 3. Handle environment variables
define: {
'process.env.REACT_APP_API_URL': JSON.stringify(process.env.VITE_API_URL),
'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV)
},
// 4. Configure build output
build: {
outDir: 'build',
sourcemap: true
},
// 5. Handle absolute imports
resolve: {
alias: {
src: resolve(__dirname, 'src')
}
}
})// packages/app/vite.config.js
export default defineConfig({
// Resolve shared packages
resolve: {
alias: {
'@shared/ui': resolve(__dirname, '../shared-ui/src'),
'@shared/utils': resolve(__dirname, '../shared-utils/src')
}
},
// Optimize shared dependencies
optimizeDeps: {
include: [
'@shared/ui',
'@shared/utils'
]
},
// Server configuration for workspace
server: {
fs: {
allow: [
resolve(__dirname, '..'), // Allow parent directory
resolve(__dirname, '../shared-ui'),
resolve(__dirname, '../shared-utils')
]
}
}
})When reviewing Vite configurations and build code, focus on these aspects:
defineConfig() for proper TypeScript support and intellisensecommand and mode parametersserver.warmup.clientFiles configured for frequently accessed modulesserver.fs.allow properly configured for monorepos/shared packageschangeOrigin and rewrite optionsimport.meta.hot.accept() used where appropriate for better DXAlways validate changes don't break existing functionality and verify build output meets performance targets before considering the issue resolved.
© cin12211, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agent/skills/vite-expert of cin12211/orca-q.
Open the folder on GitHubat commit 3142fe6
Vite Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vite Expert this skillcin12211/orca-q | 224 | — | ~6.2k | Automated safety check: Pass | MIT | |
| Vite Advancedyonatangross/orchestkit | 290 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 7 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 11 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Plugin Settings Patternanthropics/claude-plugins-official | 38k | 7 repos | ~3k | Automated safety check: Pass | Apache-2.0 |
yonatangross/orchestkit
Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
anthropics/claude-plugins-official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
cin12211/orca-q
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
cin12211/orca-q
Database performance optimization, schema design, query analysis, and connection management across PostgreSQL, MySQL, MongoDB, and SQLite with ORM integration.
cin12211/orca-q
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration.
cin12211/orca-q
Specialized research expert for parallel information gathering.
cin12211/orca-q
OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.
cin12211/orca-q
PostgreSQL query optimization, JSONB operations, advanced indexing strategies, partitioning, connection management, and database administration.
Works with
Categories
Vite build optimization expert with deep knowledge of ESM-first development, HMR optimization, plugin ecosystem, production builds, library mode, and SSR configuration. Vite Expert is an agent skill from cin12211/orca-q. Vite build optimization expert with deep knowledge of ESM-first development, HMR optimization, plugin ecosystem, production builds, library mode, and SSR configuration.
Vite Expert fits situations like: tasks that involve Hooks and plugins.
Run `npx skills add cin12211/orca-q --skill vite-expert -a claude-code`. Or copy the skill folder (.agent/skills/vite-expert in cin12211/orca-q) into .claude/skills/vite-expert in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cin12211/orca-q --skill vite-expert -a codex`. Or copy the skill folder (.agent/skills/vite-expert in cin12211/orca-q) into .agents/skills/vite-expert in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cin12211/orca-q --skill vite-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vite-expert, .gemini/skills/vite-expert, .github/skills/vite-expert and .opencode/skills/vite-expert in your project.
Going by SKILL.md and its folder, Vite Expert needs the command-line tools its instructions call (npm, npx, node, curl and tsx). Our summary lists: Node.js.
SKILL.md names 4 domains. As links in the text: vitejs.dev, github.com, web.dev and vitest.dev. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Vite Expert is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.2k tokens (SKILL.md is roughly 25k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Vite Expert: Vite Advanced (yonatangross/orchestkit, 290 stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars) and Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cin12211 (a GitHub user) maintains it in cin12211/orca-q, which has 224 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 21, 2026.
Source: cin12211/orca-q on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.