void 0.10.13 → 0.20.1

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/markdown-it-footnote/README.md

@@ -1,135 +0,0 @@
-# markdown-it-footnote
-
-[![CI](https://github.com/markdown-it/markdown-it-footnote/actions/workflows/ci.yml/badge.svg)](https://github.com/markdown-it/markdown-it-footnote/actions/workflows/ci.yml)
-[![NPM version](https://img.shields.io/npm/v/markdown-it-footnote.svg?style=flat)](https://www.npmjs.org/package/markdown-it-footnote)
-[![Coverage Status](https://img.shields.io/coveralls/markdown-it/markdown-it-footnote/master.svg?style=flat)](https://coveralls.io/r/markdown-it/markdown-it-footnote?branch=master)
-
-> Footnotes plugin for [markdown-it](https://github.com/markdown-it/markdown-it) markdown parser.
-
-__v2.+ requires `markdown-it` v5.+, see changelog.__
-
-Markup is based on [pandoc](http://johnmacfarlane.net/pandoc/README.html#footnotes) definition.
-
-__Normal footnote__:
-
-```
-Here is a footnote reference,[^1] and another.[^longnote]
-
-[^1]: Here is the footnote.
-
-[^longnote]: Here's one with multiple blocks.
-
-    Subsequent paragraphs are indented to show that they
-belong to the previous footnote.
-```
-
-html:
-
-```html
-<p>Here is a footnote reference,<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup> and another.<sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup></p>
-<p>This paragraph won’t be part of the note, because it
-isn’t indented.</p>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1"  class="footnote-item"><p>Here is the footnote. <a href="#fnref1" class="footnote-backref">↩</a></p>
-</li>
-<li id="fn2"  class="footnote-item"><p>Here’s one with multiple blocks.</p>
-<p>Subsequent paragraphs are indented to show that they
-belong to the previous footnote. <a href="#fnref2" class="footnote-backref">↩</a></p>
-</li>
-</ol>
-</section>
-```
-
-__Inline footnote__:
-
-```
-Here is an inline note.^[Inlines notes are easier to write, since
-you don't have to pick an identifier and move down to type the
-note.]
-```
-
-html:
-
-```html
-<p>Here is an inline note.<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup></p>
-<hr class="footnotes-sep">
-<section class="footnotes">
-<ol class="footnotes-list">
-<li id="fn1"  class="footnote-item"><p>Inlines notes are easier to write, since
-you don’t have to pick an identifier and move down to type the
-note. <a href="#fnref1" class="footnote-backref">↩</a></p>
-</li>
-</ol>
-</section>
-```
-
-
-## Install
-
-node.js, browser:
-
-```bash
-npm install markdown-it-footnote --save
-bower install markdown-it-footnote --save
-```
-
-## Use
-
-```js
-var md = require('markdown-it')()
-            .use(require('markdown-it-footnote'));
-
-md.render(/*...*/) // See examples above
-```
-
-_Differences in browser._ If you load script directly into the page, without
-package system, module will add itself globally as `window.markdownitFootnote`.
-
-
-### Customize
-
-If you want to customize the output, you'll need to replace the template
-functions. To see which templates exist and their default implementations,
-look in [`index.js`](index.js). The API of these template functions is out of
-scope for this plugin's documentation; you can read more about it [in the
-markdown-it
-documentation](https://github.com/markdown-it/markdown-it/blob/master/docs/architecture.md#renderer).
-
-To demonstrate with an example, here is how you might replace the `<hr>` that
-this plugin emits by default with an `<h4>` emitted by your own template
-function override:
-
-```js
-const md = require('markdown-it')().use(require('markdown-it-footnote'));
-
-md.renderer.rules.footnote_block_open = () => (
-  '<h4 class="mt-3">Footnotes</h4>\n' +
-  '<section class="footnotes">\n' +
-  '<ol class="footnotes-list">\n'
-);
-```
-
-Here's another example that customizes footnotes for epub books:
-
-```js
-const backrefLabel = 'back to text';
-
-const epubRules = {
-  footnote_ref: ['<a', '<a epub:type="noteref"'],
-  footnote_open: ['<li', '<li epub:type="footnote"'],
-  footnote_anchor: ['<a', `<a aria-label="${backrefLabel}"`],
-}
-
-Object.keys(epubRules).map(rule => {
-  let defaultRender = md.renderer.rules[rule];
-  md.renderer.rules[rule] = (tokens, idx, options, env, self) => {
-    return defaultRender(tokens, idx, options, env, self).replace(...epubRules[rule]);
-  }
-})
-```
-
-## License
-
-[MIT](https://github.com/markdown-it/markdown-it-footnote/blob/master/LICENSE)

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/pathslash/README.md

@@ -1,64 +0,0 @@
-# pathslash
-
-> `node:path`, platform-correct, with forward-slash output.
-
-`pathslash` is a tiny wrapper around `node:path` that always outputs forward slashes (`/`) while keeping the correct per-platform semantics. It never reimplements path logic. Every function delegates to `node:path` and only flips the separators in the result.
-
-## Why
-
-- **Forward slashes everywhere.** On Windows, the `win32` functions output `/` instead of `\`, which is what bundlers, route maps, and URLs expect.
-- **Correct semantics for free.** Drive letters, UNC paths, and case-insensitive `relative` behave exactly as in `node:path`, because they _are_ `node:path`.
-- **POSIX-safe.** On POSIX, a backslash is a valid filename character, so it is never rewritten there.
-- **A typed drop-in.** Same API and types as `node:path`.
-
-## Install
-
-```sh
-npm i pathslash
-```
-
-## Usage
-
-The default export and the top-level named exports follow the host platform, exactly like `node:path`:
-
-```ts
-import path, { join } from "pathslash";
-
-join("src", "a.ts"); // 'src/a.ts'
-path.sep; // '/'
-```
-
-To force a specific platform, use the `win32` and `posix` namespaces. They work on any host OS:
-
-```ts
-import { win32, posix } from "pathslash";
-
-win32.join("C:\\a", "b"); // 'C:/a/b'  (forward slashes)
-win32.normalize("C:\\a\\..\\b"); // 'C:/b'
-win32.relative("C:/Foo/Bar", "C:/foo/baz"); // '../baz'  (case-insensitive)
-
-posix.join("a", "b\\c"); // 'a/b\\c'  (backslash kept)
-```
-
-### `toSlash(path)`
-
-Safely normalizes separators to `/`. On Windows it converts `\` to `/`. On POSIX it returns the path unchanged, because a backslash is a valid filename character there and rewriting it would corrupt the path. Use it for paths that come from outside this package, such as `process.cwd()`:
-
-```ts
-import { toSlash } from "pathslash";
-
-toSlash("C:\\a\\b"); // 'C:/a/b' on Windows, unchanged on POSIX
-```
-
-## Notes
-
-- `win32.sep` is `"/"` instead of `"\\"`, and `win32.delimiter` stays `";"`.
-- `\\?\` (extended-length) paths stay verbatim. `toSlash` and every `win32.*` function leave them untouched, because a forward slash is a literal character there, not a separator.
-- `toNamespacedPath` always returns a native, backslash path, since `\\?\` paths are only valid with backslashes.
-- `matchesGlob` mirrors `node:path`. It exists only on Node versions that ship it (22.5+) and is `undefined` on older ones.
-- The types are a drop-in too: `import type { ParsedPath, FormatInputPathObject, PlatformPath } from "pathslash"`.
-- Everything else matches `node:path`, separators aside.
-
-## License
-
-[MIT](./LICENSE)

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/shiki/README.md

@@ -1,15 +0,0 @@
-<img src="https://raw.githubusercontent.com/shikijs/shiki/main/docs/public/logo.svg" width="150" alt="Shiki Logo" />
-
-# Shiki 式
-
-[![NPM version](https://img.shields.io/npm/v/shiki?color=32A9C3&labelColor=1B3C4A&label=npm)](https://www.npmjs.com/package/shiki)
-[![NPM downloads](https://img.shields.io/npm/dm/shiki?color=32A9C3&labelColor=1B3C4A&label=downloads)](https://www.npmjs.com/package/shiki)
-[![Codecov](https://img.shields.io/codecov/c/github/shikijs/shiki?token=B85J0E2I7I&style=flat&labelColor=1B3C4A&color=32A9C3&precision=1)](https://app.codecov.io/gh/shikijs/shiki)
-
-A beautiful syntax highlighter based on TextMate grammars, accurate and powerful.
-
-[📚 **Documentation**](https://shiki.style)
-
-## License
-
-[MIT](./LICENSE)

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/tinyglobby/README.md

@@ -1,25 +0,0 @@
-# tinyglobby
-
-[![npm version](https://img.shields.io/npm/v/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
-[![weekly downloads](https://img.shields.io/npm/dw/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
-
-A fast and minimal alternative to globby and fast-glob, meant to behave the same way.
-
-Both globby and fast-glob present some behavior no other globbing lib has,
-which makes it hard to manually replace with something smaller and better.
-
-This library uses only two subdependencies, compared to `globby`'s [23](https://npmgraph.js.org/?q=globby@16.2.0)
-and `fast-glob`'s [17](https://npmgraph.js.org/?q=fast-glob@3.3.3).
-
-## Usage
-
-```js
-import { glob, globSync } from 'tinyglobby';
-
-await glob(['files/*.ts', '!**/*.d.ts'], { cwd: 'src' });
-globSync('src/**/*.ts', { ignore: '**/*.d.ts' });
-```
-
-## Documentation
-
-Visit https://superchupu.dev/tinyglobby to read the full documentation.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/AGENTS.md

@@ -1,16 +0,0 @@
-<!--VITE PLUS START-->
-
-# Using Vite+, the Unified Toolchain for the Web
-
-This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, and it invokes Vite through `vp dev` and `vp build`. Run `vp help` to print a list of commands and `vp <command> --help` for information about a specific command.
-
-Docs are local at `node_modules/vite-plus/docs` or online at https://viteplus.dev/guide/.
-
-## Review Checklist
-
-- [ ] Run `vp install` after pulling remote changes and before getting started.
-- [ ] Run `vp check` and `vp test` to format, lint, type check and test changes.
-- [ ] Check if there are `vite.config.ts` tasks or `package.json` scripts necessary for validation, run via `vp run <script>`.
-- [ ] If setup, runtime, or package-manager behavior looks wrong, run `vp env doctor` and include its output when asking for help.
-
-<!--VITE PLUS END-->

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/README.md

@@ -1,220 +0,0 @@
-# VITE+(⚡︎) Local CLI
-
-**The Unified Toolchain for the Web**
-_runtime and package management, create, dev, check, test, build, pack, and monorepo task caching in a single dependency_
-
-This package provides the project-local version of Vite+. The global `vp` command automatically delegates to this package for all project-specific tasks.
-
----
-
-Vite+ is the unified entry point for local web development. It combines [Vite](https://vite.dev/), [Vitest](https://vitest.dev/), [Oxlint](https://oxc.rs/docs/guide/usage/linter.html), [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), [Rolldown](https://rolldown.rs/), [tsdown](https://tsdown.dev/), and [Vite Task](https://github.com/voidzero-dev/vite-task) into one zero-config toolchain that also manages runtime and package manager workflows:
-
-- **`vp env`:** Manage Node.js globally and per project
-- **`vp install`:** Install dependencies with automatic package manager detection
-- **`vp dev`:** Run Vite's fast native ESM dev server with instant HMR
-- **`vp check`:** Run formatting, linting, and type checks in one command
-- **`vp test`:** Run tests through bundled Vitest
-- **`vp build`:** Build applications for production with Vite + Rolldown
-- **`vp run`:** Execute monorepo tasks with caching and dependency-aware scheduling
-- **`vp pack`:** Build libraries for npm publishing or standalone app binaries
-- **`vp create` / `vp migrate`:** Scaffold new projects and migrate existing ones
-
-All of this is configured from your project root and works across Vite's framework ecosystem.
-Vite+ is fully open-source under the MIT license.
-
-## Getting Started
-
-Install Vite+ globally as `vp`:
-
-For Linux or macOS:
-
-```bash
-curl -fsSL https://vite.plus | bash
-```
-
-For Windows:
-
-```bash
-irm https://viteplus.dev/install.ps1 | iex
-```
-
-`vp` handles the full development lifecycle such as package management, development servers, linting, formatting, testing and building for production.
-
-## Configuring Vite+
-
-Vite+ can be configured using a single `vite.config.ts` at the root of your project:
-
-```ts
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  // Standard Vite configuration for dev/build/preview.
-  plugins: [],
-
-  // Vitest configuration.
-  test: {
-    include: ['src/**/*.test.ts'],
-  },
-
-  // Oxlint configuration.
-  lint: {
-    ignorePatterns: ['dist/**'],
-  },
-
-  // Oxfmt configuration.
-  fmt: {
-    semi: true,
-    singleQuote: true,
-  },
-
-  // Vite Task configuration.
-  run: {
-    tasks: {
-      'generate:icons': {
-        command: 'node scripts/generate-icons.js',
-        envs: ['ICON_THEME'],
-      },
-    },
-  },
-
-  // `vp staged` configuration.
-  staged: {
-    '*': 'vp check --fix',
-  },
-});
-```
-
-This lets you keep the configuration for your development server, build, test, lint, format, task runner, and staged-file workflow in one place with type-safe config and shared defaults.
-
-Use `vp migrate` to migrate to Vite+. It merges tool-specific config files such as `.oxlintrc*`, `.oxfmtrc*`, and lint-staged config into `vite.config.ts`.
-
-### CLI Workflows (`vp help`)
-
-#### Start
-
-- **create** - Create a new project from a template
-- **migrate** - Migrate an existing project to Vite+
-- **config** - Configure hooks and agent integration
-- **staged** - Run linters on staged files
-- **install** (`i`) - Install dependencies
-- **env** - Manage Node.js versions
-
-#### Develop
-
-- **dev** - Run the development server
-- **check** - Run format, lint, and type checks
-- **lint** - Lint code
-- **fmt** - Format code
-- **test** - Run tests
-
-#### Execute
-
-- **run** - Run monorepo tasks
-- **exec** - Execute a command from local `node_modules/.bin`
-- **node** - Run a Node.js script with the resolved Vite+ environment
-- **dlx** - Execute a package binary without installing it as a dependency
-- **cache** - Manage the task cache
-
-#### Build
-
-- **build** - Build for production
-- **pack** - Build libraries
-- **preview** - Preview production build
-
-#### Manage Dependencies
-
-Vite+ automatically wraps your package manager (pnpm, npm, Yarn, or Bun) based on `packageManager` and lockfiles:
-
-- **add** - Add packages to dependencies
-- **remove** (`rm`, `un`, `uninstall`) - Remove packages from dependencies
-- **update** (`up`) - Update packages to latest versions
-- **dedupe** - Deduplicate dependencies
-- **outdated** - Check outdated packages
-- **list** (`ls`) - List installed packages
-- **why** (`explain`) - Show why a package is installed
-- **info** (`view`, `show`) - View package metadata from the registry
-- **link** (`ln`) / **unlink** - Manage local package links
-- **rebuild** - Rebuild native modules
-- **pm** - Forward a command to the package manager
-
-#### Maintain
-
-- **upgrade** - Update `vp` itself to the latest version
-- **implode** - Remove `vp` and all related data
-
-### Scaffolding your first Vite+ project
-
-Use `vp create` to create a new project:
-
-```bash
-vp create
-```
-
-You can run `vp create` inside of a project to add new apps or libraries to your project.
-
-Organizations can expose a curated set of templates under their npm scope by
-publishing `@org/create` with a `createConfig.templates` manifest in its `package.json`.
-Once published, `vp create @org` opens an interactive picker over those
-templates, and setting `create: { defaultTemplate: '@org' }` in
-`vite.config.ts` makes it the default for bare `vp create`. See the
-[Organization Templates guide](https://viteplus.dev/guide/create#organization-templates)
-for the authoring workflow and
-[`create.defaultTemplate`](https://viteplus.dev/config/create) for the
-config reference.
-
-### Migrating an existing project
-
-You can migrate an existing project to Vite+:
-
-```bash
-vp migrate
-```
-
-### GitHub Actions
-
-Use the official [`setup-vp`](https://github.com/voidzero-dev/setup-vp) action to install Vite+ in GitHub Actions:
-
-```yaml
-- uses: voidzero-dev/setup-vp@v1
-  with:
-    node-version: '22'
-    cache: true
-```
-
-#### Manual Installation & Migration
-
-If you are manually migrating a project to Vite+, install these dev dependencies first:
-
-```bash
-npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
-```
-
-You need to add overrides to your package manager so that other packages resolve the Vite+ versions: alias `vite` to `@voidzero-dev/vite-plus-core`, and pin `vitest` to the version Vite+ bundles (run `vp --version`) so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):
-
-```json
-"overrides": {
-  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "4.1.9"
-}
-```
-
-If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
-
-```yaml
-overrides:
-  vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: 4.1.9
-```
-
-Or, if you are using Yarn:
-
-```json
-"resolutions": {
-  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "4.1.9"
-}
-```
-
-## Sponsors
-
-Thanks to [namespace.so](https://namespace.so) for powering our CI/CD pipelines with fast, free macOS and Linux runners.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/build.md

@@ -1,21 +0,0 @@
-# Build Config
-
-`vp dev`, `vp build`, and `vp preview` use the standard [Vite configuration](https://vite.dev/config/), including [plugins](https://vite.dev/guide/using-plugins), [aliases](https://vite.dev/config/shared-options#resolve-alias), [`server`](https://vite.dev/config/server-options), [`build`](https://vite.dev/config/build-options) and [`preview`](https://vite.dev/config/preview-options) fields.
-
-## Example
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  server: {
-    port: 3000,
-  },
-  build: {
-    sourcemap: true,
-  },
-  preview: {
-    port: 4173,
-  },
-});
-```

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/check.md

@@ -1,35 +0,0 @@
-# Check Config
-
-`vp check` runs format, lint, and type checks together. The `check` block in `vite.config.ts` sets defaults for the composite command, mirroring the `--no-fmt` and `--no-lint` CLI flags.
-
-This is useful when a project wants to keep most of the toolchain but skip one step by default. For example, a team that lints but does not format can disable `check.fmt` so a plain `vp check` (the command agents and contributors run most) only lints, without anyone needing to remember `--no-fmt`.
-
-## Example
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  check: {
-    // Skip the format step in `vp check`. Defaults to true.
-    fmt: false,
-    // Skip lint rules in `vp check`. Type-check still runs when both
-    // `lint.options.typeAware` and `lint.options.typeCheck` are enabled.
-    // Defaults to true.
-    lint: true,
-  },
-});
-```
-
-When a step is disabled here, `vp check` prints a short `note:` line so it is clear why the step did not run. With the `check.fmt: false` config above:
-
-```bash
-$ vp check
-note: Format skipped (check.fmt: false in vite.config.ts)
-pass: Found no warnings or lint errors in 1 file (12ms, 8 threads)
-```
-
-## Scope and precedence
-
-- These options only affect the composite `vp check`. Standalone [`vp fmt`](/config/fmt) and [`vp lint`](/config/lint) are unaffected, so you can still run a disabled tool directly when you need it once. Note that any `vp check` invocation honors these defaults, including one run from a pre-commit hook: if your [`staged`](/config/staged) tasks call `vp check`, that step is skipped there too.
-- A step is skipped if the config disables it **or** the matching CLI flag is passed. There is no flag to re-enable a step disabled in config; run `vp fmt` or `vp lint` directly instead.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/create.md

@@ -1,70 +0,0 @@
-# Create Config
-
-`vp create` reads the `create` block in `vite.config.ts` to set per-repo defaults. See the [Creating a Project guide](/guide/create#organization-templates) for the full `@org` template workflow.
-
-## `create.defaultTemplate`
-
-When `vp create` is invoked with no `TEMPLATE` argument, Vite+ uses this value as if the user had typed it. Typically set to an npm scope whose `@scope/create` package publishes a `createConfig.templates` manifest — so bare `vp create` drops into the org picker.
-
-```ts
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  create: {
-    defaultTemplate: '@your-org',
-  },
-});
-```
-
-Any value accepted by `vp create` as a first argument works here: `@your-org` for an org picker, `@your-org:web` for a direct manifest entry, `vite:application` for a built-in, or the `name` of a local `create.templates` entry (see below).
-
-## `create.templates`
-
-Declare local templates available to `vp create` inside a monorepo. Each entry is listed in the `vp create` picker, and selecting it (or passing its `name` as the template argument) runs the resolved `template`.
-
-```ts
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  create: {
-    templates: [
-      {
-        name: 'component',
-        description: 'Internal UI component',
-        template: './tools/create-component',
-      },
-      { name: 'service', description: 'Backend service', template: 'service-generator' },
-    ],
-  },
-});
-```
-
-Each entry has:
-
-| Field         | Required | Notes                                                                                                                                                                                                                                            |
-| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `name`        | yes      | Identifier shown in the picker and accepted as `vp create <name>`. Must be unique within the array. The `vite:` prefix is reserved for built-in templates.                                                                                       |
-| `description` | yes      | One-line description shown in the picker.                                                                                                                                                                                                        |
-| `template`    | yes      | A workspace package name, a relative `./path` to a local package's directory (resolved against the workspace root), a `vite:*` built-in, a GitHub URL, or a full npm package name (e.g. `create-foo`). It is run as-is (not shorthand-expanded). |
-
-`create.templates` is the source of truth for local templates: only entries listed here appear in the picker. Vite+ does not infer templates from package.json keywords. A `create.templates` entry whose `template` does not match any workspace package, or resolves to a local package without a `bin`, is reported as an error rather than falling through to an unrelated npm package.
-
-[`vp create vite:generator`](/guide/create#code-generators) adds an entry here automatically (idempotently, preserving `defaultTemplate`); you can also edit the list by hand.
-
-`create.defaultTemplate` can name a local entry, so bare `vp create` opens it directly.
-
-## Precedence
-
-CLI argument > `create.defaultTemplate` > the standard built-in picker.
-
-Explicit specifiers always win, so scripts and CI can bypass the configured default:
-
-```bash
-# Uses create.defaultTemplate
-vp create
-
-# Explicitly ignores the default
-vp create vite:library
-```
-
-The org picker also appends a trailing "Vite+ built-in templates" entry — selecting it routes to the `vite:monorepo` / `vite:application` / `vite:library` / `vite:generator` flow, so built-ins stay reachable interactively even when a default is configured.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/fmt.md

@@ -1,20 +0,0 @@
-# Format Config
-
-`vp fmt` and `vp check` read Oxfmt settings from the `fmt` block in `vite.config.ts`. See [Oxfmt's configuration](https://oxc.rs/docs/guide/usage/formatter/config.html) for details.
-
-## Example
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  fmt: {
-    ignorePatterns: ['dist/**'],
-    singleQuote: true,
-    semi: true,
-    sortPackageJson: true,
-  },
-});
-```
-
-For package-specific formatting settings in a workspace, use [`fmt.overrides`](/guide/monorepo#format-overrides) from the root `vite.config.ts`.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/index.md

@@ -1,35 +0,0 @@
-# Configuring Vite+
-
-Vite+ keeps project configuration in one place: `vite.config.ts`, allowing you to consolidate many top-level configuration files in a single file. You can keep using your Vite configuration such as `server` or `build`, and add Vite+ blocks for the rest of your workflow:
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  server: {},
-  build: {},
-  preview: {},
-
-  create: {},
-  run: {},
-  fmt: {},
-  lint: {},
-  check: {},
-  test: {},
-  pack: {},
-  staged: {},
-});
-```
-
-## Vite+ Specific Configuration
-
-Vite+ extends the basic Vite configuration with these additions:
-
-- [`create`](/config/create) for project and template scaffolding defaults
-- [`run`](/config/run) for Vite Task
-- [`fmt`](/config/fmt) for Oxfmt
-- [`lint`](/config/lint) for Oxlint
-- [`check`](/config/check) for `vp check` defaults
-- [`test`](/config/test) for Vitest
-- [`pack`](/config/pack) for tsdown
-- [`staged`](/config/staged) for staged-file checks