Agent skill

Vite Advanced

by yonatangross in yonatangross/orchestkit

Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization.

MITAuto-check: notesAgent Workflows

Install Vite Advanced

skills CLI
$ npx skills add yonatangross/orchestkit --skill vite-advanced -a claude-code

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

GitHub CLI
$ gh skill install yonatangross/orchestkit vite-advanced --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/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/vite-advanced .claude/skills/vite-advanced && 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/

Facts

Skill name
vite-advanced
GitHub stars
290
Token cost
~1.7k tokens
SKILL.md length
481 words
Files
13 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization.

  • Customizing build pipelines
  • SKILL.md covers Upstream coverage (do not…, House delta, House config and Rules, plus 3 more sections
  • Runs TypeScript scripts from its folder; calls npx
  • Creating plugins

What it does

Vite Advanced is an agent skill from yonatangross/orchestkit. Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization. Use when customizing build pipelines, creating plugins, or configuring multi-environment builds.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts and reference files (for example `references/library-mode.md`, `references/ork-delta.md` and `rules/_sections.md`). Compatibility notes: Claude Code 2.1.277+.

It sits in Agent Workflows, covering Hooks and plugins and CI/CD. It works with Vite. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.

When your agent uses it

  • Customizing build pipelines
  • Creating plugins
  • Configuring multi-environment builds

Example prompts

  • “/vite-advanced”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Claude Code 2.1.277+.
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • vite.dev

    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.

  • Compatibility

    Claude Code 2.1.277+.

    From compatibility in the SKILL.md frontmatter.

Context cost

Vite Advanced loads about 1.7k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 481 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:50
    | Env variables and modes, `.env` files, the `VITE_` prefix | https://vite.dev/guide/env-and-mode |
  • NoteMentions a .env fileSKILL.md:108
    ic bundle content, never secrets. Audit `.env.production` before deploy.

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); the scripts in this folder are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 02bbf9a, republished under its MIT licence (© yonatangross). 481 words, ~1,668 tokens.

Download SKILL.mdSave it as .claude/skills/vite-advanced/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
vite-advanced
description
Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization. Use when customizing build pipelines, creating plugins, or configuring multi-environment builds.
allowed-tools
Read, Glob, Grep, WebFetch, WebSearch
compatibility
Claude Code 2.1.277+.
license
MIT
user-invocable
false
disable-model-invocation
true
metadata.owner-agent
frontend-ui-developer
metadata.category
document-asset-creation
metadata.vite-version
8.0
metadata.version
2.0.0
metadata.author
OrchestKit
metadata.complexity
medium
metadata.tags
vite, vite8, rolldown, build, bundler, plugins, ssr, library-mode, environment-api, optimization, advancedchunks

Vite Advanced Patterns

A wrapper around Vite 8 (Rolldown-powered), not a copy of its documentation. Vite's own docs are the source of truth for config keys, API surface, and migration mechanics. This skill carries the house delta plus four enforceable rules.

Vite 8 replaces the esbuild+Rollup pipeline with Rolldown (Rust-based unified bundler) and is the default for new projects. advancedChunks supersedes manualChunks; build.rollupOptions becomes build.rolldownOptions.

Upstream coverage (do not restate)

Fetch these from Vite rather than expecting them here. Rows marked with a rule keep a narrower, enforceable house subset in that rule file: read the rule for the house position, fetch the doc for the full API.

TopicFetch from
Vite 7 to 8 migration: rolldownOptions, transformWithOxc, moduleType: 'js', removed hooks and output formats, browser target bumpshttps://vite.dev/guide/migration
Rolldown adoption path, rolldown-vite, Oxc, advancedChunks group syntax (house subset stays in rules/vite-advanced-chunks.md)https://vite.dev/guide/rolldown
Build options: target, minify, sourcemap, cssCodeSplit, cssMinify, assetsInlineLimit, chunkSizeWarningLimithttps://vite.dev/config/build-options
Dependency pre-bundling and optimizeDeps include/exclude/forcehttps://vite.dev/guide/dep-pre-bundling
SSR: client and server entry points, middleware-mode dev server, production server wiring, streaminghttps://vite.dev/guide/ssr
Environment API config and per-environment build output (house subset stays in rules/vite-environments.md)https://vite.dev/guide/api-environment
Environment API for plugins: this.environment, perEnvironmentPlugin, applyToEnvironmenthttps://vite.dev/guide/api-environment-plugins
Environment API for frameworks: createBuilder, buildApp, ModuleRunnerhttps://vite.dev/guide/api-environment-frameworks
Plugin hook reference, virtual modules, enforce/apply, handleHotUpdate (house subset stays in rules/vite-plugin-hooks.md)https://vite.dev/guide/api-plugin
Env variables and modes, .env files, the VITE_ prefixhttps://vite.dev/guide/env-and-mode
Deploying a static site and verifying with vite previewhttps://vite.dev/guide/static-deploy

Library mode is not in the table: references/library-mode.md and rules/vite-lib-config.md still carry it in full.

House delta

Read references/ork-delta.md for the rules Vite's docs do not state: the Vite 8 adoption path for existing production apps, the VITE_ secrets rule, the production sourcemap setting, the house build budget, the vite preview gate, chunk-name stability across the advancedChunks migration, the visualizer diff requirement, and the node_modules/.vite cache-clearing step.

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

House config

Not a Vite tutorial: these are the settings the delta above makes non-negotiable, in the shape we actually ship them.

ts
// vite.config.ts
import { defineConfig } from 'vite';

export default defineConfig({
  build: {
    // 'hidden' emits maps for the error reporter without publishing source.
    // Never true (publishes source) and never 'inline' (inflates every JS file).
    sourcemap: 'hidden',
    rollupOptions: {
      output: {
        // Carry existing chunk NAMES across the manualChunks to advancedChunks
        // migration. A renamed group changes its filename and invalidates that
        // chunk for every returning visitor, even with identical contents.
        advancedChunks: {
          groups: [
            { name: 'vendor', test: /node_modules/, priority: 10 },
            { name: 'app', priority: 0 },
          ],
        },
      },
    },
  },
});
bash
# Prove the build. `vite build` exiting 0 means the bundler finished, not that the
# app runs: base-path mistakes and dev-only env vars survive a green build.
vite build && vite preview      # then walk the routes, console must be clean

# Diff the chunk graph before and after any chunk-config change.
npx vite-bundle-visualizer

# Stale pre-bundle cache mimics a broken plugin. Clear it BEFORE editing plugin code.
rm -rf node_modules/.vite && vite --force

VITE_-prefixed variables are inlined into the client bundle at build time. They are public bundle content, never secrets. Audit .env.production before deploy.

Rules

RuleCovers
rules/vite-advanced-chunks.mdChunk splitting: advancedChunks groups, priority, maxSize, minShareCount
rules/vite-environments.mdenvironments config for client, SSR, and edge; per-environment outDir
rules/vite-lib-config.mdLibrary mode externals, dual ESM/CJS output, exports map, type declarations
rules/vite-plugin-hooks.mdHook order, virtual modules via resolveId + load, enforce and apply

Key Decisions

DecisionRecommendation
New projectsVite 8 (default)
Existing production appsStage the upgrade through rolldown-vite before committing
Multi-env buildsEnvironment API (environments config)
Plugin scopeUse this.environment for env-aware plugins
SSRMiddleware mode for dev, separate builds for prod
ChunksadvancedChunks for Vite 8, manualChunks for Vite 7 compat
  • ork:react-server-components-framework - SSR integration
  • ork:storybook-testing - Component testing with Vitest
  • ork:performance - Core Web Vitals targets behind the build budget

References

Load on demand with Read("references/<file>"):

FileContent
ork-delta.mdHouse rules that Vite's docs do not state
library-mode.mdBuilding publishable npm packages

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (scripts, references) in src/skills/vite-advanced of yonatangross/orchestkit.

  • SKILL.md
  • references/library-mode.md
  • references/ork-delta.md
  • rules/_sections.md
  • rules/_template.md
  • rules/vite-advanced-chunks.md
  • rules/vite-environments.md
  • rules/vite-lib-config.md
  • rules/vite-plugin-hooks.md
  • scripts/custom-plugin.ts
  • scripts/library-config.ts
  • scripts/multi-environment-config.ts
  • test-cases.json

Open the folder on GitHubat commit 02bbf9a

Compare with similar skills

Vite Advanced 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 Advanced compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vite Advanced this skillyonatangross/orchestkit290—~1.7kAutomated safety check: NotesMIT
Vite Expertcin12211/orca-q224—~6.2kAutomated safety check: PassMIT
Avotokyo Workflowsheyq02/simpleicons.dev171—~1.5kAutomated safety check: PassApache-2.0
Check Deps SyncHyk260/PureChat546—~594Automated safety check: PassMIT
Benchmark Readme Syncrstackjs/build-tools-performance115—~1.6kAutomated safety check: PassMIT
Upgrade Runtime StackPackmindHub/packmind317—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • Vite Expert

    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.

    224 GitHub stars~6.2k tokensUpdated 18 days ago
    Agent WorkflowsAuto-check passed
  • Avotokyo Workflows

    heyq02/simpleicons.dev

    Use avotokyo/workflows reusable GitHub Actions for TypeScript/Vite+ projects.

    171 GitHub stars~1.5k tokensUpdated 19 days ago
    DevOps & CloudAuto-check passed
  • Check Deps Sync

    Hyk260/PureChat

    Check if package.json files are in sync with pnpm-lock.yaml.

    546 GitHub stars~594 tokensUpdated 23 days ago
    DevOps & CloudAuto-check passed
  • Benchmark Readme Sync

    rstackjs/build-tools-performance

    Refresh README benchmark results from a successful GitHub Actions Benchmark run, preserving data provenance and separate development, build, and memory tables.

    115 GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Upgrade Runtime Stack

    PackmindHub/packmind

    Check whether newer stable versions of Node.js (24.x line), Nx, or Vite are available and, if so, generate a detailed upgrade plan markdown file at the repo root.

    317 GitHub stars~2.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • GitHub Actions CD for Cloudflare Workers through cf with automatic traffic rollback on smoke failure, including JSON deployment snapshots, D1 migrations and prebuilt artifacts.

    359 GitHub stars~1.2k tokensUpdated 7 days ago
    DevOps & CloudAuto-check: notes

More from yonatangross/orchestkit

All 108 skills in this repo
  • API Design

    yonatangross/orchestkit

    API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.

    290 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    290 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    290 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    290 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    290 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    290 GitHub stars~3.9k tokensUpdated today
    Auto-check: notes

Works with

Questions about Vite Advanced

What does Vite Advanced do?

Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization. Vite Advanced is an agent skill from yonatangross/orchestkit. Advanced Vite 8 patterns including Rolldown-powered builds, advancedChunks, Environment API, plugin development, SSR configuration, library mode, and build optimization.

When should I use Vite Advanced?

Vite Advanced fits situations like: customizing build pipelines; creating plugins; configuring multi-environment builds.

How do I install Vite Advanced in Claude Code?

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

How do I install Vite Advanced in Codex?

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

Can I use Vite Advanced 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 yonatangross/orchestkit --skill vite-advanced -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-advanced, .gemini/skills/vite-advanced, .github/skills/vite-advanced and .opencode/skills/vite-advanced in your project.

What does Vite Advanced need to run?

Going by SKILL.md and its folder, Vite Advanced needs TypeScript for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+..

Does Vite Advanced access the network?

SKILL.md names 1 domain. As links in the text: vite.dev. This is read from the text; nothing was executed.

Is Vite Advanced safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Vite Advanced use?

Vite Advanced is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vite Advanced use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 2.4k tokens, read only when the agent opens those files.

What are the alternatives to Vite Advanced?

Skills that share tags, products or a category with Vite Advanced: Vite Expert (cin12211/orca-q, 224 stars), Avotokyo Workflows (heyq02/simpleicons.dev, 171 stars), Check Deps Sync (Hyk260/PureChat, 546 stars) and Benchmark Readme Sync (rstackjs/build-tools-performance, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vite Advanced?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 290 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

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