vite-workspace-performance

Diagnose and optimize Vite dev and build performance across the Afenda monorepo.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-vite-react --skill vite-workspace-performance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite-workspace-performance
Source: https://github.com/pohlai88/afenda-vite-react/tree/main/.cursor/skills/vite-workspace-performance
Command: npx skills add https://github.com/pohlai88/afenda-vite-react --skill vite-workspace-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and optimizes Vite dev and build performance across the Afenda monorepo, reducing latency, improving cold/warm start times, and stabilizing the development experience.

Core Features & Use Cases

  • Profiling and baseline normalization for Vite projects in apps/web and workspace packages.
  • Targeted optimizations (server warmup, optimizeDeps, chunking, and plugin ordering) with repeatable workflows.
  • Guidance for common scenarios like slow first paint, long HMR cycles, or after dependency upgrades.

Quick Start

Execute the profiling and optimization workflow from the repo root to measure and improve Vite performance in apps/web.

Frequently Asked Questions about vite-workspace-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize Vite dev server performance in a monorepo?

To optimize Vite dev server performance in a monorepo, normalize profiling baselines and apply targeted optimizations like server warmup, configure optimizeDeps, chunking, and adjust plugin ordering across workspace packages to reduce latency and stabilize startup times.

Why does Vite HMR latency increase after upgrading dependencies?

Vite HMR latency often increases after upgrading dependencies due to shifted module graphs or invalidated optimizeDeps caches. Re-establish baseline profiling and tune dependency pre-bundling and plugin ordering to restore fast hot module replacement cycles.

What is the best way to profile slow Vite production builds?

The best way to profile slow Vite production builds is to enforce baseline warmup and profiling steps from the repository root, measuring first paint and build times to identify bottlenecks in chunking and plugin ordering before applying optimizations.

How do I reduce slow first paint time in a Vite workspace?

To reduce slow first paint time in a Vite workspace, execute the profiling workflow to measure current metrics, then apply server warmup and optimizeDeps configurations to improve cold and warm start times across your applications.

Does Vite workspace performance tuning require specific plugin configurations?

Vite workspace performance tuning requires specific plugin configurations because plugin ordering directly impacts build and dev server speed. Enforcing baselines for plugin ordering ensures repeatable optimizations and prevents regression after dependency changes.