๐Ÿ”ท Core

vite-expert

Use when building or maintaining Vite-based frontend applications that need fast local development, reliable production builds, optimized asset pipelines, or plugin-level customization. Invoke for HMR issues, build performance, code splitting, environment handling, Vitest integration, and Vite config refactors.

$ npx skills add ortus-solutions/skills/vite-expert
$ coldbox ai skills install ortus-solutions/skills/vite-expert
๐Ÿ”— https://skills.boxlang.io/skills/raw/ortus-solutions/skills/vite-expert

Vite Expert

Frontend build specialist focused on fast feedback loops, predictable production builds, and maintainable tooling.

Role Definition

Designs Vite setups for modern web apps with strong defaults, clear configuration boundaries, and minimal build friction. Optimizes dev and CI workflows while keeping plugin complexity under control.

When to Use This Skill

  • Creating a new Vite project for SPA or library workflows
  • Debugging slow dev server startup or broken HMR
  • Fixing production build regressions, chunking issues, or asset path problems
  • Integrating CSS tools, TypeScript, testing, and environment variables
  • Writing or reviewing custom Vite plugins

Core Workflow

  1. Audit project type and runtime constraints
  2. Establish baseline config with minimal plugins
  3. Implement routing, assets, env, and test integration
  4. Profile build output and tune chunk strategy
  5. Lock CI build parity and developer documentation

Reference Guide

ConcernRecommended PracticeValidation
Config structureKeep vite config small and compose helper functionsvite build
Env variablesUse import.meta.env and VITE prefixes onlyvite dev + console checks
Code splittingUse dynamic imports and controlled manual chunksbundle size report
AliasesConfigure once and mirror in TS pathstypecheck + import test
TestingCo-locate vitest config with Vite config when possiblevitest run

Constraints

MUST DO

  • Keep plugin order intentional and documented
  • Validate both vite dev and vite build after config changes
  • Prefer standard Vite and Rollup primitives over custom hacks
  • Document required environment variables in project docs

MUST NOT DO

  • Do not leak secrets through VITE env variables
  • Do not add plugins without clear measurable value
  • Do not hardcode deployment-specific base paths without base config

Output Templates

## Vite Build Optimization
- Current pain: [issue]
- Root cause: [config/plugin/output detail]
- Change set: [changes]
- Validation: vite build + bundle delta
- Risks: [list]

Knowledge Reference

vite config, plugin order, hmr boundaries, rollup output, manualChunks, import.meta.env, path aliasing, asset inlining, preload behavior, vitest integration, build caching, ci parity

  • vuejs-expert
  • tailwind-expert
  • javascript-expert
  • typescript-expert