Create Vite Plugin

OrganizationPopular

videojs

create-vite-plugin

Create Vite plugins. Use for hooks.

Overview

Publisher	videojs
Repository	`v10`
Skill name	`create-vite-plugin`
Stars	1K
Forks	93
Bundled files	1
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by videojs on GitHub. Read the source before you install it.

Installation

Install the Create Vite Plugin AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/videojs/v10/tree/main/.agents/skills/create-vite-plugin
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/videojs/v10.git /tmp/v10
mkdir -p .claude/skills
cp -r /tmp/v10/.agents/skills/create-vite-plugin .claude/skills/create-vite-plugin

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Create Vite Plugin in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Create Vite Plugin on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Create Vite Plugin is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Vite plugin implementation

Inspect the installed Vite and Rolldown versions, application config, neighboring plugins, and serve/build tests before implementing. Vite 8's Plugin extends Rolldown's Plugin; keep generic resolution, loading, transforms, graph work, and output in a Rolldown plugin and add a Vite layer only for Vite-specific behavior.

Workflow

Classify the requirement. Use a Rolldown plugin directly for host-generic module/build behavior. Use a Vite plugin for config, environments, configureServer, HTML, HMR, preview, or behavior that intentionally differs between serve and build.
Decide activation explicitly. Use apply: 'serve' or apply: 'build' when only one command is valid. A generic build-only Rolldown plugin may instead live in build.rolldownOptions.plugins; do not initialize asset generation or destructive output logic during dev.
Enable build.rolldownOptions.experimental.nativeMagicString: true in repository-owned Vite builds and set build.sourcemap: true when production maps should be emitted. This affects Vite's production Rolldown build but does not add Rolldown AST or MagicString metadata to Vite transform hooks; use the VJSC Vite adapter for transforms that need it.
Use enforce only for a real Vite tier requirement. Prefer per-hook order for a specific Rolldown hook. Prove ordering with behavior tests rather than depending on array position.
Use config to return a partial Vite config that may be deeply merged. Do not attempt to inject plugins from that hook. Read final values in configResolved; keep environment-specific state out of global app hooks.
Treat resolve/load/transform hooks as per-environment. Use Vite's environment APIs or separate plugin instances when builds may run concurrently. Worker plugins must be created by worker.plugins and receive fresh instances.
Normalize paths before Vite-specific ID comparisons. For cross-host VJSC code, reuse package src/utils module-ID and path helpers instead of importing Vite utilities into the generic plugin.
Remember that aliases affect module resolution, not authored import text retained in generated source or JSON. Resolve dependencies through the host, then perform only the packaging rewrite required by the output format.
Test serve and build separately. Cover activation, resolved config, virtual modules, transform order, SSR/environment flags when relevant, HMR invalidation, HTML output, existing application entries, and emitted assets.

Read references/api-and-host-contracts.md when choosing between a raw Rolldown plugin, build.rolldownOptions.plugins, a top-level Vite plugin, or an environment-aware plugin.

Use packages/vjsc/src/vite/index.ts as the thin-adapter example, packages/vjsc/src/plugins/tests for direct Rolldown coverage, and packages/skins/build/tests/vite.test.ts as the Vite host test anchor.

Validation

Run focused programmatic Vite serve/build tests, the underlying Rolldown tests when shared, the owning package build, pnpm typecheck, and pnpm check:workspace. Avoid E2E coverage unless the requested behavior genuinely crosses the browser boundary.

Example

Input: “Make this source transform available in Vite and rebuild when its config changes.”

Output: A host-generic Rolldown transform reused by a thin Vite entry, Vite-only watch/config handling where needed, explicit serve/build activation, and tests proving identical transformed source through direct Rolldown and Vite.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/api-and-host-contracts.md5 KB

Frequently asked questions

What does the Create Vite Plugin AI skill do?

Create Vite plugins. Use for hooks.

Why use Create Vite Plugin on TypingMind?

Because you install it once and use it with any model. Create Vite Plugin is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Create Vite Plugin in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/videojs/v10/tree/main/.agents/skills/create-vite-plugin. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Create Vite Plugin?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Create Vite Plugin?

As many as you like. As long as a model supports skills, you can use Create Vite Plugin with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Create Vite Plugin AI skill free?

It is published on GitHub by videojs. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Discord E2e

Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and…

Openclaw Qa Testing

Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

Proof Video

Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Vite plugin implementation

Workflow

Validation

Example

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now