Agent skill

Vite

Vite performance optimization guidelines. An agent skill from pproenca/dot-skills.

MITAuto-check passedDevelopment

Install Vite

skills CLI

$ npx skills add pproenca/dot-skills --skill vite -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills vite --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/vite .claude/skills/vite && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "vite" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite into .claude/skills/vite/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite", 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

$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite

Type 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.

skills CLI

$ npx skills add pproenca/dot-skills --skill vite -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills vite --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/vite .agents/skills/vite && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "vite" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite into .agents/skills/vite/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite", 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.

skills CLI

$ npx skills add pproenca/dot-skills --skill vite -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills vite --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/vite .cursor/skills/vite && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "vite" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite into .cursor/skills/vite/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite", 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

$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/vite

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pproenca/dot-skills --skill vite -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills vite --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/vite .gemini/skills/vite && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "vite" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite into .gemini/skills/vite/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite", 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.

GitHub CLI

$ gh skill install pproenca/dot-skills vite

Installs 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).

skills CLI

$ npx skills add pproenca/dot-skills --skill vite -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/vite .github/skills/vite && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "vite" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite into .github/skills/vite/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite", 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.

skills CLI

$ npx skills add pproenca/dot-skills --skill vite -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pproenca/dot-skills vite --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/vite .opencode/skills/vite && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "vite" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/vite into .opencode/skills/vite/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vite", 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.

Facts

Skill name: vite
GitHub stars: 214
Token cost: ~1.6k tokens
SKILL.md length: 453 words
Files: 48 (incl. references, assets)
Skills in repo: 182
Repo updated: Aug 15, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Vite performance optimization guidelines. An agent skill from pproenca/dot-skills.

Works in 8 steps: Dependency Pre-bundling (CRITICAL) → Plugin Performance (CRITICAL) → Bundle Optimization (CRITICAL) → …
Tasks involving Vite config
SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vite is an agent skill from pproenca/dot-skills. Vite performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring Vite configuration and projects to ensure optimal performance patterns. Triggers on tasks involving Vite config, build optimization, dependency pre-bundling, plugin development, bundle analysis, or HMR issues.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 50 other files, including reference files and assets (for example `AGENTS.md`, `README.md` and `assets/templates/_template.md`).

It sits in Development, covering Hooks and plugins, Performance optimization and Refactoring. It works with Vite. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.

When your agent uses it

Tasks involving Vite config
Build optimization
Dependency pre-bundling
Plugin development

Example prompts

“/vite”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Dependency Pre-bundling (CRITICAL)
Plugin Performance (CRITICAL)
Bundle Optimization (CRITICAL)
Import Resolution (HIGH)
Build Configuration (HIGH)
Development Server (MEDIUM-HIGH)
CSS Optimization (MEDIUM)
Advanced Patterns (LOW-MEDIUM)

What it can do on your machine

Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.

Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vite loads about 1.6k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 453 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~17k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 453 words, ~1,615 tokens.

Download SKILL.mdSave it as .claude/skills/vite/SKILL.md (or your agent's skills folder). This skill also uses 47 other files; get the full folder from GitHub.

name: vite
description: Vite performance optimization guidelines. This skill should be used when writing, reviewing, or refactoring Vite configuration and projects to ensure optimal performance patterns. Triggers on tasks involving Vite config, build optimization, dependency pre-bundling, plugin development, bundle analysis, or HMR issues.

Vite Best Practices

Comprehensive performance optimization guide for Vite applications. Contains 42 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

Reference these guidelines when:

Configuring Vite for a new project
Troubleshooting slow dev server startup
Optimizing production bundle size
Debugging HMR issues
Writing or evaluating Vite plugins
Migrating from Webpack or other bundlers

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Dependency Pre-bundling	CRITICAL	`deps-`
2	Plugin Performance	CRITICAL	`plugin-`
3	Bundle Optimization	CRITICAL	`bundle-`
4	Import Resolution	HIGH	`import-`
5	Build Configuration	HIGH	`build-`
6	Development Server	MEDIUM-HIGH	`dev-`
7	CSS Optimization	MEDIUM	`css-`
8	Advanced Patterns	LOW-MEDIUM	`advanced-`

Quick Reference

1. Dependency Pre-bundling (CRITICAL)

deps-include-large-cjs - Include large dependencies with many modules
deps-exclude-esm - Exclude small ESM dependencies
deps-force-rebundle - Use --force flag for dependency changes
deps-hold-until-crawl - Configure holdUntilCrawlEnd for startup behavior
deps-entries - Configure custom entry points for discovery
deps-linked-packages - Handle linked dependencies in monorepos

2. Plugin Performance (CRITICAL)

plugin-lazy-imports - Use dynamic imports in plugin code
plugin-avoid-long-hooks - Avoid long operations in startup hooks
plugin-transform-early-return - Early return in transform hooks
plugin-audit-community - Audit community plugins for performance
plugin-swc-over-babel - Use SWC instead of Babel for React

3. Bundle Optimization (CRITICAL)

bundle-manual-chunks - Use manualChunks for vendor splitting
bundle-dynamic-imports - Use dynamic imports for route-level splitting
bundle-analyze - Analyze bundle composition
bundle-tree-shaking - Enable effective tree-shaking
bundle-chunk-warning - Address large chunk warnings
bundle-compression - Disable compressed size reporting for large projects
bundle-asset-inlining - Configure asset inlining threshold

4. Import Resolution (HIGH)

import-avoid-barrel - Avoid barrel file imports
import-explicit-extensions - Use explicit file extensions
import-path-aliases - Configure path aliases for clean imports
import-svg-strings - Import SVGs as strings instead of components
import-glob-patterns - Use glob imports carefully

Show full SKILL.md (184 more words)Show less

5. Build Configuration (HIGH)

build-modern-target - Target modern browsers
build-minification - Use esbuild for minification
build-sourcemaps - Disable source maps in production
build-css-code-split - Enable CSS code splitting
build-rolldown - Consider Rolldown for faster builds
build-output-dir - Configure output directory and caching

6. Development Server (MEDIUM-HIGH)

dev-server-warmup - Warm up frequently used files
dev-browser-cache - Keep browser cache enabled in DevTools
dev-fs-limits - Increase file descriptor limits on Linux
dev-wsl-polling - Use polling for WSL file watching
dev-https-proxy - Configure HTTPS and proxy for development

7. CSS Optimization (MEDIUM)

css-lightning - Use Lightning CSS instead of PostCSS
css-avoid-preprocessors - Prefer CSS over preprocessors when possible
css-modules - Use CSS Modules for component styles
css-inline-critical - Extract critical CSS for initial paint

8. Advanced Patterns (LOW-MEDIUM)

advanced-ssr-externalize - Externalize dependencies for SSR
advanced-env-static - Use static environment variables
advanced-profiling - Profile build performance
advanced-lib-mode - Configure library mode for package development

How to Use

Read individual reference files for detailed explanations and code examples:

Section definitions - Category structure and impact levels
Rule template - Template for adding new rules

Reference Files

File	Description
AGENTS.md	Complete compiled guide with all rules
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

Files

SKILL.md and 47 other files (references, assets) in skills/.experimental/vite of pproenca/dot-skills.

SKILL.md
AGENTS.md
README.md
assets/templates/_template.md
metadata.json
references/_sections.md
references/advanced-env-static.md
references/advanced-lib-mode.md
references/advanced-profiling.md
references/advanced-ssr-externalize.md
references/build-css-code-split.md
references/build-minification.md
references/build-modern-target.md
references/build-output-dir.md
references/build-rolldown.md
references/build-sourcemaps.md
references/bundle-analyze.md
references/bundle-asset-inlining.md
… and 30 more

Open the folder on GitHubat commit cf93c57

Compare with similar skills

Vite 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.

Vite compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Vite this skillpproenca/dot-skills	214	—	~1.6k	Automated safety check: Pass	MIT	1 mo ago
React Best Practicesryokun6/ryos	1.3k	—	~2k	Automated safety check: Pass	MIT	today
Svelte5 Best PracticesSikandarJODD/cnblocks	430	1 repos	~810	Automated safety check: Pass	MIT	3 mo ago
React Best Practicesshapeshift/web	206	1 repos	~2k	Automated safety check: Pass	MIT	today
Performance ProfilingLiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator	1.8k	—	~1.8k	Automated safety check: Pass	GPL-3.0	3 days ago
Nuxt Best Practicesvinayakkulkarni/nxui	212	—	~1.5k	Automated safety check: Pass	MIT	today

Similar skills

React Best Practices
ryokun6/ryos
React performance optimization guidelines from Vercel Engineering (vercel-labs/agent-skills).
1.3k GitHub stars~2k tokensUpdated today
Frontend & DesignAuto-check passed
Svelte5 Best Practices
SikandarJODD/cnblocks
Svelte 5 runes, snippets, SvelteKit patterns, and modern best practices for TypeScript and component development.
430 GitHub starsUsed in 1 repo~810 tokens
DevelopmentAuto-check passed
React Best Practices
shapeshift/web
Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering.
206 GitHub starsUsed in 1 repo~2k tokens
DevelopmentAuto-check passed
Performance Profiling
LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator
Run the headless app, catalog-load, and ZIP profilers and interpret the JSON the way a human would from window.profiler.report(), profile:load, and the ZIP console table.
1.8k GitHub stars~1.8k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Nuxt Best Practices
vinayakkulkarni/nxui
Nuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications.
212 GitHub stars~1.5k tokensUpdated today
DevelopmentAuto-check passed
Swift Concurrency
supabitapp/supaterm
Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration.
173 GitHub stars~3.3k tokensUpdated 13 days ago
DevelopmentAuto-check passed

Questions about Vite

What does Vite do?

Vite performance optimization guidelines. An agent skill from pproenca/dot-skills. Vite is an agent skill from pproenca/dot-skills. Vite performance optimization guidelines.

When should I use Vite?

Vite fits situations like: tasks involving Vite config; build optimization; dependency pre-bundling; plugin development.

How do I install Vite in Claude Code?

Run `npx skills add pproenca/dot-skills --skill vite -a claude-code`. Or copy the skill folder (skills/.experimental/vite in pproenca/dot-skills) into .claude/skills/vite in your project. Claude Code loads it when a task matches its description.

How do I install Vite in Codex?

Run `npx skills add pproenca/dot-skills --skill vite -a codex`. Or copy the skill folder (skills/.experimental/vite in pproenca/dot-skills) into .agents/skills/vite in your project. Codex loads it when a task matches its description.

Can I use Vite in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill vite -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, .gemini/skills/vite, .github/skills/vite and .opencode/skills/vite in your project.

What does Vite need to run?

SKILL.md names no scripts, command-line tools or credentials: Vite is instructions for the agent only.

Does Vite access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vite safe to install?

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.

What licence does Vite use?

Vite is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vite use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Vite?

Skills that share tags, products or a category with Vite: React Best Practices (ryokun6/ryos, 1.3k stars), Svelte5 Best Practices (SikandarJODD/cnblocks, 430 stars), React Best Practices (shapeshift/web, 206 stars) and Performance Profiling (LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vite?

pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.

Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Vite

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Vite Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Dependency Pre-bundling (CRITICAL)

2. Plugin Performance (CRITICAL)

3. Bundle Optimization (CRITICAL)

4. Import Resolution (HIGH)

5. Build Configuration (HIGH)

6. Development Server (MEDIUM-HIGH)

7. CSS Optimization (MEDIUM)

8. Advanced Patterns (LOW-MEDIUM)

How to Use

Reference Files

Files

Compare with similar skills

Similar skills

More from pproenca/dot-skills

Related

Questions about Vite