Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

stack-vite

Étoiles3

Forks0

Mis à jour27 juin 2026 à 14:53

Vite frontend build tool — configuration, plugins, asset loading

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Snakeblack

Snakeblack/ospec-workflow

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	stack-vite
description	Vite frontend build tool — configuration, plugins, asset loading
license	Apache-2.0
metadata	{"author":"manuel-retamozo-garcia","version":"1.0"}
capabilities	["vite"]

Vite Patterns

Build tool and dev server patterns for Vite 8+ projects. Covers configuration, environment variables, proxy setup, library mode, dependency pre-bundling, and common production pitfalls.

When to Use

Configuring vite.config.ts or vite.config.js
Setting up environment variables or .env files
Configuring dev server proxy for API backends
Optimizing build output (chunks, minification, assets)
Publishing libraries with build.lib
Troubleshooting dependency pre-bundling or CJS/ESM interop

Core Rules

Dev vs Build Engines: Dev serves files as native ESM (transpiled on demand via esbuild). Production builds use Rolldown/Rollup. Always smoke-test with vite preview before deploying.
Type Checking Gap: Vite build transpiles but does NOT type-check. You must run tsc --noEmit in CI or use vite-plugin-checker.
Environment Security: Only VITE_-prefixed environment variables are exposed to the client. Secrets must NEVER use the prefix. Never pass empty string loadEnv(mode, cwd, '') as it leaks server secrets.
Performance Aliases: Avoid hand-rolling aliases. Use vite-tsconfig-paths to reuse tsconfig.json configurations.
Barrel Files: Avoid importing from index/barrel files in the dev server hot-path as it triggers loading of all re-exported files.

References

For full code examples, plugin configurations, manual chunk setups, and server proxy details, refer to:

Vite Configuration & Build Optimization Patterns

Plus depuis ce dépôt

même dépôt

sdd-document

Snakeblack/ospec-workflow

Generate repository wiki pages mapping architecture, specs, and status. Trigger: orchestrator launches sdd-document.

2026-07-183

shared

Snakeblack/ospec-workflow

Shared SDD references for installed skills. Not invokable.

2026-07-183

review-change

Snakeblack/ospec-workflow

Read-only generalist screening contract for selective 4R review.

2026-07-173

review-correction

Snakeblack/ospec-workflow

Read-only targeted correction validator for a bounded review lineage.

2026-07-173

sdd-spec

Snakeblack/ospec-workflow

Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.

2026-07-143

branch-pr

Snakeblack/ospec-workflow

Create pull requests with branch, validation, and publication checks. Trigger: creating, opening, or preparing PRs for review.

2026-07-143

name	stack-vite
description	Vite frontend build tool — configuration, plugins, asset loading
license	Apache-2.0
metadata	{"author":"manuel-retamozo-garcia","version":"1.0"}
capabilities	["vite"]

Vite Patterns

Build tool and dev server patterns for Vite 8+ projects. Covers configuration, environment variables, proxy setup, library mode, dependency pre-bundling, and common production pitfalls.

When to Use

Configuring vite.config.ts or vite.config.js
Setting up environment variables or .env files
Configuring dev server proxy for API backends
Optimizing build output (chunks, minification, assets)
Publishing libraries with build.lib
Troubleshooting dependency pre-bundling or CJS/ESM interop

Core Rules

Dev vs Build Engines: Dev serves files as native ESM (transpiled on demand via esbuild). Production builds use Rolldown/Rollup. Always smoke-test with vite preview before deploying.
Type Checking Gap: Vite build transpiles but does NOT type-check. You must run tsc --noEmit in CI or use vite-plugin-checker.
Environment Security: Only VITE_-prefixed environment variables are exposed to the client. Secrets must NEVER use the prefix. Never pass empty string loadEnv(mode, cwd, '') as it leaks server secrets.
Performance Aliases: Avoid hand-rolling aliases. Use vite-tsconfig-paths to reuse tsconfig.json configurations.
Barrel Files: Avoid importing from index/barrel files in the dev server hot-path as it triggers loading of all re-exported files.

References

For full code examples, plugin configurations, manual chunk setups, and server proxy details, refer to:

Vite Configuration & Build Optimization Patterns