mcpField
V
vite

vite

github.com/partme-aiDevelopment727140 installsUpdated 5w ago
Repository

About vite

vite is a documentation-focused skill for developers working with Vite. It maps user questions to guide, configuration, and plugin references, covering development, build, SSR, deployment, and APIs.

Key features

  1. 01Guide topic reference mapping
  2. 02Vite configuration references
  3. 03Plugin selection guidance
  4. 04CLI and API coverage
  5. 05SSR and deployment topics

Use cases

  1. 01Finding guidance for Vite configuration
  2. 02Choosing a Vite plugin
  3. 03Working with HMR or JavaScript APIs
  4. 04Investigating SSR or deployment setups

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/partme-ai/full-stack-skills --skill vite

After installing, type/vitein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

api/
cli.md
config.md
plugin-api.md
examples/config/
build-options.md
configuring-vite.md
dep-optimization-options.md
preview-options.md
server-options.md
shared-options.md
ssr-options.md
worker-options.md
examples/guide/
api-environment-frameworks.md
api-environment-instances.md
api-environment-plugins.md
api-environment-runtimes.md
api-environment.md
api-hmr.md
api-javascript.md
api-plugin.md
assets.md
backend-integration.md
build.md
cli.md
dep-pre-bundling.md
env-and-mode.md
features.md
getting-started.md
migration.md
performance.md
philosophy.md

Details

From the project README

When to use this skill

Use this skill whenever the user wants to:

  • Follow Vite Guide topics from getting started to performance
  • Configure Vite using the official config reference
  • Select or understand Vite plugins from the official plugins page
  • Use Vite CLI, HMR API, or JavaScript API
  • Handle SSR, backend integration, or deployment scenarios in Vite

How to use this skill

  1. Identify the topic from the user request.
  2. Open the matching guide example file in examples/guide/.
  3. If configuration is needed, open the matching file in examples/config/.
  4. If plugin selection is needed, open examples/plugins.md.
  5. Follow official docs verbatim and keep output consistent with the referenced page.
  6. Validate: Run npm run build to verify config changes compile; npm run preview to test production output.
Guide mapping (one-to-one with https://cn.vitejs.dev/guide/)

Introduction

Guide

APIs

Environment API

Config mapping (one-to-one with https://cn.vitejs.dev/config/)
Plugins mapping (one-to-one with https://cn.vitejs.dev/plugins/)
Inline Quick Start
# Create a new Vite project
npm create vite@latest my-app -- --template react-ts

# Install and run
cd my-app && npm install
npm run dev      # Dev server with HMR
npm run build    # Production build
npm run preview  # Preview production build

// vite.config.ts
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

export default defineConfig({
  plugins: [react()],
  server: {
    port: 3000,
    proxy: {
      '/api': 'http://localhost:8080',
    },
  },
  build: {
    sourcemap: true,
    rollupOptions: {
      output: {
        manualChunks: { vendor: ['react', 'react-dom'] },
      },
    },
  },
});

Best Practices

  • Use defineConfig for TypeScript type hints and autocomplete
  • Configure proxy in server.proxy for API calls during development
  • Use build.rollupOptions.output.manualChunks for vendor splitting
  • Enable source maps in development; disable in production for smaller builds
  • Use import.meta.env for environment variables (prefix with VITE_)

Resources

Keywords

Vite, build tool, dev server, HMR, config, plugins, SSR, CLI, dependency pre-bundling, assets

Comments

Markdown supported