LangBot Core Development
langbot-app/LangBot
Covers developing the LangBot core backend and web UI: dev setup, repo layout, API auth types, adding endpoints, migrations and keeping the MCP server in step.
Creates devtools integrations for Vite using @vitejs/devtools-kit.
$ npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yuyinws/oxc-inspector writing-vite-devtools-integrations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yuyinws/oxc-inspector.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-vite-devtools-integrations .claude/skills/writing-vite-devtools-integrations && rm -rf skills-srcUse ~/.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/
Install the "writing-vite-devtools-integrations" agent skill from https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrations into .claude/skills/writing-vite-devtools-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-vite-devtools-integrations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yuyinws/oxc-inspector writing-vite-devtools-integrations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuyinws/oxc-inspector.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-vite-devtools-integrations .agents/skills/writing-vite-devtools-integrations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-vite-devtools-integrations" agent skill from https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrations into .agents/skills/writing-vite-devtools-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-vite-devtools-integrations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yuyinws/oxc-inspector writing-vite-devtools-integrations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuyinws/oxc-inspector.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-vite-devtools-integrations .cursor/skills/writing-vite-devtools-integrations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-vite-devtools-integrations" agent skill from https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrations into .cursor/skills/writing-vite-devtools-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-vite-devtools-integrations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yuyinws/oxc-inspector.git --path .agents/skills/writing-vite-devtools-integrations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yuyinws/oxc-inspector writing-vite-devtools-integrations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuyinws/oxc-inspector.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-vite-devtools-integrations .gemini/skills/writing-vite-devtools-integrations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-vite-devtools-integrations" agent skill from https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrations into .gemini/skills/writing-vite-devtools-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-vite-devtools-integrations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yuyinws/oxc-inspector writing-vite-devtools-integrationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yuyinws/oxc-inspector.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-vite-devtools-integrations .github/skills/writing-vite-devtools-integrations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-vite-devtools-integrations" agent skill from https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrations into .github/skills/writing-vite-devtools-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-vite-devtools-integrations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yuyinws/oxc-inspector writing-vite-devtools-integrations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuyinws/oxc-inspector.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-vite-devtools-integrations .opencode/skills/writing-vite-devtools-integrations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-vite-devtools-integrations" agent skill from https://github.com/yuyinws/oxc-inspector/tree/main/.agents/skills/writing-vite-devtools-integrations into .opencode/skills/writing-vite-devtools-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-vite-devtools-integrations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
writing-vite-devtools-integrationsCreates devtools integrations for Vite using @vitejs/devtools-kit.
Writing Vite Devtools Integrations is an agent skill from yuyinws/oxc-inspector. Creates devtools integrations for Vite using @vitejs/devtools-kit. Use when building Vite plugins with devtools panels, RPC functions, dock entries, shared state, or any devtools-related functionality. Applies to files importing from @vitejs/devtools-kit or containing devtools.setup hooks in Vite plugins.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/dock-entry-types.md`, `references/project-structure.md` and `references/rpc-patterns.md`).
It sits in Development. It works with Vite. The repository describes itself as: Inspect and understand the Oxc toolchain with ease. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d00072a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Writing Vite Devtools Integrations loads about 2k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 263 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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); files beside SKILL.md are not scanned.
The full file from yuyinws/oxc-inspector at commit d00072a, republished under its MIT licence (© yuyinws). 263 words, ~2,043 tokens.
.claude/skills/writing-vite-devtools-integrations/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Build custom developer tools that integrate with Vite DevTools using @vitejs/devtools-kit.
A DevTools plugin extends a Vite plugin with a devtools.setup(ctx) hook. The context provides:
| Property | Purpose |
|---|---|
ctx.docks | Register dock entries (iframe, action, custom-render) |
ctx.views | Host static files for UI |
ctx.rpc | Register RPC functions, broadcast to clients |
ctx.rpc.sharedState | Synchronized server-client state |
ctx.viteConfig | Resolved Vite configuration |
ctx.viteServer | Dev server instance (dev mode only) |
ctx.mode | 'dev' or 'build' |
/// <reference types="@vitejs/devtools-kit" />
import type { Plugin } from 'vite'
export default function myPlugin(): Plugin {
return {
name: 'my-plugin',
devtools: {
setup(ctx) {
ctx.docks.register({
id: 'my-plugin',
title: 'My Plugin',
icon: 'ph:puzzle-piece-duotone',
type: 'iframe',
url: 'https://example.com/devtools',
})
},
},
}
}/// <reference types="@vitejs/devtools-kit" />
import type { Plugin } from 'vite'
import { fileURLToPath } from 'node:url'
import { defineRpcFunction } from '@vitejs/devtools-kit'
export default function myAnalyzer(): Plugin {
const data = new Map<string, { size: number }>()
return {
name: 'my-analyzer',
// Collect data in Vite hooks
transform(code, id) {
data.set(id, { size: code.length })
},
devtools: {
setup(ctx) {
// 1. Host static UI
const clientPath = fileURLToPath(new URL('../dist/client', import.meta.url))
ctx.views.hostStatic('/.my-analyzer/', clientPath)
// 2. Register dock entry
ctx.docks.register({
id: 'my-analyzer',
title: 'Analyzer',
icon: 'ph:chart-bar-duotone',
type: 'iframe',
url: '/.my-analyzer/',
})
// 3. Register RPC function
ctx.rpc.register(
defineRpcFunction({
name: 'my-analyzer:get-data',
type: 'query',
setup: () => ({
handler: async () => Array.from(data.entries()),
}),
}),
)
},
},
}
}CRITICAL: Always prefix RPC functions, shared state keys, and dock IDs with your plugin name:
// Good - namespaced
'my-plugin:get-modules'
'my-plugin:state'
// Bad - may conflict
'get-modules'
'state'| Type | Use Case |
|---|---|
iframe | Full UI panels, dashboards (most common) |
action | Buttons that trigger client-side scripts (inspectors, toggles) |
custom-render | Direct DOM access in panel (framework mounting) |
ctx.docks.register({
id: 'my-plugin',
title: 'My Plugin',
icon: 'ph:house-duotone',
type: 'iframe',
url: '/.my-plugin/',
})ctx.docks.register({
id: 'my-inspector',
title: 'Inspector',
icon: 'ph:cursor-duotone',
type: 'action',
action: {
importFrom: 'my-plugin/devtools-action',
importName: 'default',
},
})ctx.docks.register({
id: 'my-custom',
title: 'Custom View',
icon: 'ph:code-duotone',
type: 'custom-render',
renderer: {
importFrom: 'my-plugin/devtools-renderer',
importName: 'default',
},
})import { defineRpcFunction } from '@vitejs/devtools-kit'
const getModules = defineRpcFunction({
name: 'my-plugin:get-modules',
type: 'query', // 'query' | 'action' | 'static'
setup: ctx => ({
handler: async (filter?: string) => {
// ctx has full DevToolsNodeContext
return modules.filter(m => !filter || m.includes(filter))
},
}),
})
// Register in setup
ctx.rpc.register(getModules)import { getDevToolsRpcClient } from '@vitejs/devtools-kit/client'
const rpc = await getDevToolsRpcClient()
const modules = await rpc.call('my-plugin:get-modules', 'src/')import type { DevToolsClientScriptContext } from '@vitejs/devtools-kit/client'
export default function setup(ctx: DevToolsClientScriptContext) {
ctx.current.events.on('entry:activated', async () => {
const data = await ctx.current.rpc.call('my-plugin:get-data')
})
}// Server broadcasts to all clients
ctx.rpc.broadcast({
method: 'my-plugin:on-update',
args: [{ changedFile: '/src/main.ts' }],
})Extend the DevTools Kit interfaces for full type checking:
// src/types.ts
import '@vitejs/devtools-kit'
declare module '@vitejs/devtools-kit' {
interface DevToolsRpcServerFunctions {
'my-plugin:get-modules': (filter?: string) => Promise<Module[]>
}
interface DevToolsRpcClientFunctions {
'my-plugin:on-update': (data: { changedFile: string }) => void
}
interface DevToolsRpcSharedStates {
'my-plugin:state': MyPluginState
}
}const state = await ctx.rpc.sharedState.get('my-plugin:state', {
initialValue: { count: 0, items: [] },
})
// Read
console.log(state.value())
// Mutate (auto-syncs to clients)
state.mutate(draft => {
draft.count += 1
draft.items.push('new item')
})const client = await getDevToolsRpcClient()
const state = await client.rpc.sharedState.get('my-plugin:state')
// Read
console.log(state.value())
// Subscribe to changes
state.on('updated', newState => {
console.log('State updated:', newState)
})For action buttons and custom renderers:
// src/devtools-action.ts
import type { DevToolsClientScriptContext } from '@vitejs/devtools-kit/client'
export default function setup(ctx: DevToolsClientScriptContext) {
ctx.current.events.on('entry:activated', () => {
console.log('Action activated')
// Your inspector/tool logic here
})
ctx.current.events.on('entry:deactivated', () => {
console.log('Action deactivated')
// Cleanup
})
}Export from package.json:
{
"exports": {
".": "./dist/index.mjs",
"./devtools-action": "./dist/devtools-action.mjs"
}
}DevToolsRpcServerFunctions for type-safe RPCmutate() call for multiple changesctx.views.hostStatic() for your UI assetsph:* (Phosphor) icons: icon: 'ph:chart-bar-duotone'© yuyinws, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in .agents/skills/writing-vite-devtools-integrations of yuyinws/oxc-inspector.
Open the folder on GitHubat commit d00072a
Writing Vite Devtools Integrations 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Vite Devtools Integrations this skillyuyinws/oxc-inspector | 169 | — | ~2k | Automated safety check: Pass | MIT | |
| LangBot Core Developmentlangbot-app/LangBot | 18k | — | ~1.4k | Automated safety check: Notes | Apache-2.0 | |
| Dev Serverlablup/backend.ai-webui | 133 | — | ~7.5k | Automated safety check: Notes | LGPL-3.0 | |
| Faasjs Project Workflowfaasjs/faasjs | 121 | — | ~577 | Automated safety check: Pass | MIT | |
| Claimable Postgreshenryalouf/ruflow | 157 | — | ~2.4k | Automated safety check: Notes | MIT | |
| Power Apps Code App Scaffoldgithub/awesome-copilot | 40k | 1 repos | ~1.8k | Automated safety check: Pass | MIT |
langbot-app/LangBot
Covers developing the LangBot core backend and web UI: dev setup, repo layout, API auth types, adding endpoints, migrations and keeping the MCP server in step.
lablup/backend.ai-webui
Start the project's development server (pnpm dev for backend.ai-webui; discovered from README/package.json elsewhere), deriving the header color, app name, default backend endpoint and login…
faasjs/faasjs
A skill your agent uses when creating, configuring, reviewing, or onboarding a FaasJS project; working with create-faas-app, vp CLI, TypeScript or Vite config, feature folders, file and naming…
henryalouf/ruflow
Provision instant temporary Postgres databases via Claimable Postgres by Neon (pg.new).
github/awesome-copilot
Scaffold a complete Power Apps Code App project with PAC CLI setup, SDK integration, and connector configuration
amir20/dozzle
Starts a Dozzle dev server on a port derived from the current worktree so you can test by hand in a browser, without disturbing instances started elsewhere.
Works with
Categories
Creates devtools integrations for Vite using @vitejs/devtools-kit. Writing Vite Devtools Integrations is an agent skill from yuyinws/oxc-inspector. Creates devtools integrations for Vite using @vitejs/devtools-kit.
Writing Vite Devtools Integrations fits situations like: building Vite plugins with devtools panels; any devtools-related functionality.
Run `npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a claude-code`. Or copy the skill folder (.agents/skills/writing-vite-devtools-integrations in yuyinws/oxc-inspector) into .claude/skills/writing-vite-devtools-integrations in your project. Claude Code loads it when a task matches its description.
Run `npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a codex`. Or copy the skill folder (.agents/skills/writing-vite-devtools-integrations in yuyinws/oxc-inspector) into .agents/skills/writing-vite-devtools-integrations in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yuyinws/oxc-inspector --skill writing-vite-devtools-integrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-vite-devtools-integrations, .gemini/skills/writing-vite-devtools-integrations, .github/skills/writing-vite-devtools-integrations and .opencode/skills/writing-vite-devtools-integrations in your project.
SKILL.md names no scripts, command-line tools or credentials: Writing Vite Devtools Integrations is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Writing Vite Devtools Integrations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.2k 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 5.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Writing Vite Devtools Integrations: LangBot Core Development (langbot-app/LangBot, 18k stars), Dev Server (lablup/backend.ai-webui, 133 stars), Faasjs Project Workflow (faasjs/faasjs, 121 stars) and Claimable Postgres (henryalouf/ruflow, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
yuyinws (a GitHub user) maintains it in yuyinws/oxc-inspector, which has 169 GitHub stars. The repository was last updated on July 15, 2026.
Source: yuyinws/oxc-inspector on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.