Skip to main content
Agent skill

Configure Vite Plus

Configure Vite+. Use for tasks, cache, migration, or CI.

Get started

Get the complete skill folder, including its scripts and reference files.

This page is available to readers but is excluded from the public index, because it does not yet meet the evaluation standard.

When to use this skill

Use Configure Vite Plus when an AI agent needs a reusable SKILL.md workflow for this job: Configure Vite+. Use for tasks, cache, migration, or CI.

When not to use it

Skip Configure Vite Plus when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/configure-vite-plus
# Save SKILL.md to ~/.claude/skills/configure-vite-plus/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/configure-vite-plus/SKILL.md. For a shared project, commit the folder at .claude/skills/configure-vite-plus/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Configure Vite Plus skill for this task: Classify each operation: vp build for applications, vp pack for libraries, and vp run for orchestration and caching. Invoke a script or configured task as vp run <name>; bare vp <name> selects a built-in command. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
69/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Configure Vite+ workflows

Inspect the installed `vite-plus` version, root and owning-package manifests and `vite.config.ts` files, `build/pack.ts`, relevant CI workflows, and the command's current clean-run behavior before editing. Use `pnpm exec vp <command> --help` and installed types when they differ from online documentation.

Read [references/official-guide.md](references/official-guide.md) only for the sections that match the work: task graphs, cache diagnosis, GitHub Actions cache, Pack, or migration.

## Workflow

1. Classify each operation: `vp build` for applications, `vp pack` for libraries, and `vp run` for orchestration and caching. Invoke a script or configured task as `vp run <name>`; bare `vp <name>` selects a built-in command. 2. Preserve build boundaries. Keep historically separate packaging workflows in separate Vite+ configs unless they are genuinely variants of one build. A named `pack` array supports `vp pack --filter <name>` within one workflow; a nested `vite.config.ts` supports an independent workflow via `vp -C <dir> pack`. 3. Define ordering in `run.tasks`, not in serial shell pipelines. Every configured task needs `command` and cannot duplicate a same-named `package.json` script. Use `{ task: 'build', from: ['dependencies', 'devDependencies'] }` for declared direct workspace edges and `package#task` for synthetic edges such as generated CDN assets. `-r` selects workspace tasks; it does not replace missing task dependencies. 4. Let the graph expose independent work to Vite+'s scheduler. Do not lower concurrency to repair missing edges. Reserve `--parallel`, which ignores dependencies, for independent persistent tasks such as development servers. 5. Keep root scripts as thin selectors. Put package-specific commands, inputs, outputs, environment, and dependencies in the owning package's config. 6. Prove local cache stability before configuring cross-run cache. Only `vp run` uses Vite Task caching. Run the exact task twice and require the second run to hit. Prefer automatic tracking, then add `input`, `output`, `env`, or `untrackedEnv` only from observed misses. Avoid generators that rewrite unchanged inputs. 7. In GitHub Actions, install first, restore `node_modules/.vite/task-cache`, run the same `vp run` tasks used locally, and save only after success. Keep source and lockfile hashes out of the Actions cache key because Vite Task fingerprints task inputs.

## Repository gotchas

- Reuse packaging defaults from `build/pack.ts`; keep package entries, platform, and exceptional plugins local. - Top-level Vite `resolve.alias` and Pack's `pack.alias` serve different consumers. Do not assume one configures the other; share alias constants when both commands need identical mappings and test both paths. - Vite+ loads a package config before it can schedule that package's dependencies. Config-time imports from private workspace packages must be available without relying on their built output. - `vp pack` uses file-system cache tracking rather than `vp build`'s cooperative Vite metadata. Diagnose its observed reads and writes before adding manual globs.

## Example

Input: The sandbox build consumes normal workspace packages and generated HTML CDN files.

Output: A configured build task with declared workspace and generated-artifact dependencies.

```ts build: { command: 'vp build', dependsOn: [ { task: 'build', from: ['dependencies', 'devDependencies'] }, '@videojs/html#build:cdn', ], } ```

## Validation

Run the narrow target from a clean output state, inspect `vp run -v` ordering, and run it immediately again to verify cache hits and restored outputs. Then run the affected package tests/build, `pnpm typecheck` when types or configs changed, and `pnpm check:workspace`. For CI changes, verify restore occurs after install, save uses the restore step's primary key, and logs show both an Actions cache restore and Vite Task cache hits.

Intended uses

  • Classify each operation: vp build for applications, vp pack for libraries, and vp run for orchestration and caching. Invoke a script or configured task as vp run <name>; bare vp <name> selects a built-in command.
  • Preserve build boundaries. Keep historically separate packaging workflows in separate Vite+ configs unless they are genuinely variants of one build. A named pack array supports vp pack --filter <name> within one workflow; a nested vite.config.ts supports an independent workflow via vp -C <dir> pack.
  • Define ordering in run.tasks, not in serial shell pipelines. Every configured task needs command and cannot duplicate a same-named package.json script. Use { task: 'build', from: ['dependencies', 'devDependencies'] } for declared direct workspace edges and package#task for synthetic edges such as generated CDN assets. -r selects workspace tasks; it does not replace missing task dependencies.
  • Let the graph expose independent work to Vite+'s scheduler. Do not lower concurrency to repair missing edges. Reserve --parallel, which ignores dependencies, for independent persistent tasks such as development servers.
  • Keep root scripts as thin selectors. Put package-specific commands, inputs, outputs, environment, and dependencies in the owning package's config.
  • Prove local cache stability before configuring cross-run cache. Only vp run uses Vite Task caching. Run the exact task twice and require the second run to hit. Prefer automatic tracking, then add input, output, env, or untrackedEnv only from observed misses. Avoid generators that rewrite unchanged inputs.
  • In GitHub Actions, install first, restore nodemodules/.vite/task-cache, run the same vp run tasks used locally, and save only after success. Keep source and lockfile hashes out of the Actions cache key because Vite Task fingerprints task inputs.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.