diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index be7ce2c369..db66190d19 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -250,11 +250,11 @@ jobs:
       - name: Create release body
         run: |
           if [[ "${{ inputs.npm_tag }}" == "latest" ]]; then
-            INSTALL_BASH="curl -fsSL https://viteplus.dev/install.sh | bash"
-            INSTALL_PS1="irm https://viteplus.dev/install.ps1 | iex"
+            INSTALL_BASH="curl -fsSL https://vite.plus | bash"
+            INSTALL_PS1="irm https://vite.plus/ps1 | iex"
           else
-            INSTALL_BASH="curl -fsSL https://viteplus.dev/install.sh | VITE_PLUS_VERSION=${{ env.VERSION }} bash"
-            INSTALL_PS1="\\\$env:VITE_PLUS_VERSION=\\\"${{ env.VERSION }}\\\"; irm https://viteplus.dev/install.ps1 | iex"
+            INSTALL_BASH="curl -fsSL https://vite.plus | VITE_PLUS_VERSION=${{ env.VERSION }} bash"
+            INSTALL_PS1="\\\$env:VITE_PLUS_VERSION=\\\"${{ env.VERSION }}\\\"; irm https://vite.plus/ps1 | iex"
           fi
           cat > ./RELEASE_BODY.md <<EOF
           ## vite-plus v${{ env.VERSION }}
@@ -307,6 +307,6 @@ jobs:
             • vite-plus@${{ env.VERSION }}
 
             **Install:**
-            • macOS/Linux: `curl -fsSL https://viteplus.dev/install.sh | bash`
-            • Windows: `irm https://viteplus.dev/install.ps1 | iex`
+            • macOS/Linux: `curl -fsSL https://vite.plus | bash`
+            • Windows: `irm https://vite.plus/ps1 | iex`
           embed-url: https://github.com/${{ github.repository }}/releases/tag/v${{ env.VERSION }}
diff --git a/.vscode/extensions.json b/.vscode/extensions.json
index 99e2f7ddf7..46cef3bd96 100644
--- a/.vscode/extensions.json
+++ b/.vscode/extensions.json
@@ -1,3 +1,3 @@
 {
-  "recommendations": ["oxc.oxc-vscode"]
+  "recommendations": ["VoidZero.vite-plus-extension-pack"]
 }
diff --git a/.vscode/settings.json b/.vscode/settings.json
index e291954cfc..34259a1533 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -17,6 +17,5 @@
   "typescript.preferences.importModuleSpecifierEnding": "js",
   "typescript.reportStyleChecksAsWarnings": false,
   "typescript.updateImportsOnFileMove.enabled": "always",
-  "typescript.tsdk": "node_modules/typescript/lib",
   "typescript.experimental.useTsgo": true
 }
diff --git a/README.md b/README.md
index 947ff6b178..621b325c4d 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ Install Vite+ globally as `vp`:
 For Linux or macOS:
 
 ```bash
-curl -fsSL https://viteplus.dev/install.sh | bash
+curl -fsSL https://vite.plus | bash
 ```
 
 For Windows:
@@ -140,6 +140,7 @@ Vite+ automatically wraps your package manager (pnpm, npm, or Yarn) based on `pa
 #### Maintain
 
 - **upgrade** - Update `vp` itself to the latest version
+- **implode** - Remove `vp` and all related data
 
 ### Scaffolding your first Vite+ project
 
diff --git a/crates/vite_global_cli/src/help.rs b/crates/vite_global_cli/src/help.rs
index 6b26c08097..3998212d82 100644
--- a/crates/vite_global_cli/src/help.rs
+++ b/crates/vite_global_cli/src/help.rs
@@ -10,6 +10,7 @@ pub struct HelpDoc {
     pub usage: &'static str,
     pub summary: Vec<&'static str>,
     pub sections: Vec<HelpSection>,
+    pub documentation_url: Option<&'static str>,
 }
 
 #[derive(Clone, Debug)]
@@ -29,6 +30,7 @@ struct OwnedHelpDoc {
     usage: String,
     summary: Vec<String>,
     sections: Vec<OwnedHelpSection>,
+    documentation_url: Option<String>,
 }
 
 #[derive(Clone, Debug)]
@@ -55,6 +57,33 @@ fn section_lines(title: &'static str, lines: Vec<&'static str>) -> HelpSection {
     HelpSection::Lines { title, lines }
 }
 
+fn documentation_url_for_command_path(command_path: &[&str]) -> Option<&'static str> {
+    match command_path {
+        [] => Some("https://viteplus.dev/guide/"),
+        ["create"] => Some("https://viteplus.dev/guide/create"),
+        ["migrate"] => Some("https://viteplus.dev/guide/migrate"),
+        ["config"] | ["staged"] => Some("https://viteplus.dev/guide/commit-hooks"),
+        [
+            "install" | "add" | "remove" | "update" | "dedupe" | "outdated" | "list" | "ls" | "why"
+            | "info" | "view" | "show" | "link" | "unlink" | "pm",
+            ..,
+        ] => Some("https://viteplus.dev/guide/install"),
+        ["dev"] => Some("https://viteplus.dev/guide/dev"),
+        ["check"] => Some("https://viteplus.dev/guide/check"),
+        ["lint"] => Some("https://viteplus.dev/guide/lint"),
+        ["fmt"] => Some("https://viteplus.dev/guide/fmt"),
+        ["test"] => Some("https://viteplus.dev/guide/test"),
+        ["run"] => Some("https://viteplus.dev/guide/run"),
+        ["exec" | "dlx"] => Some("https://viteplus.dev/guide/vpx"),
+        ["cache"] => Some("https://viteplus.dev/guide/cache"),
+        ["build" | "preview"] => Some("https://viteplus.dev/guide/build"),
+        ["pack"] => Some("https://viteplus.dev/guide/pack"),
+        ["env", ..] => Some("https://viteplus.dev/guide/env"),
+        ["upgrade"] => Some("https://viteplus.dev/guide/upgrade"),
+        _ => None,
+    }
+}
+
 pub fn render_heading(title: &str) -> String {
     let heading = format!("{title}:");
     if !should_style_help() {
@@ -73,21 +102,12 @@ fn render_usage_value(usage: &str) -> String {
 }
 
 fn should_accent_heading(title: &str) -> bool {
-    matches!(
-        title,
-        "Start"
-            | "Develop"
-            | "Execute"
-            | "Build"
-            | "Manage Dependencies"
-            | "Maintain"
-            | "Setup"
-            | "Manage"
-            | "Inspect"
-            | "Examples"
-            | "Options"
-            | "Related Commands"
-    )
+    title != "Usage"
+}
+
+fn write_documentation_footer(output: &mut String, documentation_url: &str) {
+    let _ = writeln!(output);
+    let _ = writeln!(output, "{} {documentation_url}", render_heading("Documentation"));
 }
 
 pub fn should_style_help() -> bool {
@@ -189,6 +209,10 @@ pub fn render_help_doc(doc: &HelpDoc) -> String {
         }
     }
 
+    if let Some(documentation_url) = doc.documentation_url {
+        write_documentation_footer(&mut output, documentation_url);
+    }
+
     output
 }
 
@@ -222,6 +246,10 @@ fn render_owned_help_doc(doc: &OwnedHelpDoc) -> String {
         }
     }
 
+    if let Some(documentation_url) = &doc.documentation_url {
+        write_documentation_footer(&mut output, documentation_url);
+    }
+
     output
 }
 
@@ -386,7 +414,7 @@ fn parse_clap_help_to_doc(raw_help: &str) -> Option<OwnedHelpDoc> {
         }
     }
 
-    Some(OwnedHelpDoc { usage, summary, sections })
+    Some(OwnedHelpDoc { usage, summary, sections, documentation_url: None })
 }
 
 pub fn top_level_help_doc() -> HelpDoc {
@@ -459,6 +487,7 @@ pub fn top_level_help_doc() -> HelpDoc {
                 ],
             ),
         ],
+        documentation_url: documentation_url_for_command_path(&[]),
     }
 }
 
@@ -546,6 +575,7 @@ fn env_help_doc() -> HelpDoc {
                 ],
             ),
         ],
+        documentation_url: documentation_url_for_command_path(&["env"]),
     }
 }
 
@@ -577,6 +607,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     vec!["  vp dev", "  vp dev --open", "  vp dev --host localhost --port 5173"],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["dev"]),
         }),
         "build" => Some(HelpDoc {
             usage: "vp build [ROOT] [OPTIONS]",
@@ -604,6 +635,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     vec!["  vp build", "  vp build --watch", "  vp build --sourcemap"],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["build"]),
         }),
         "preview" => Some(HelpDoc {
             usage: "vp preview [ROOT] [OPTIONS]",
@@ -628,6 +660,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                 ),
                 section_lines("Examples", vec!["  vp preview", "  vp preview --port 4173"]),
             ],
+            documentation_url: documentation_url_for_command_path(&["preview"]),
         }),
         "test" => Some(HelpDoc {
             usage: "vp test [COMMAND] [FILTERS] [OPTIONS]",
@@ -666,6 +699,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     ],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["test"]),
         }),
         "lint" => Some(HelpDoc {
             usage: "vp lint [PATH]... [OPTIONS]",
@@ -692,6 +726,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     ],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["lint"]),
         }),
         "fmt" => Some(HelpDoc {
             usage: "vp fmt [PATH]... [OPTIONS]",
@@ -714,6 +749,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     vec!["  vp fmt", "  vp fmt src --check", "  vp fmt . --write"],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["fmt"]),
         }),
         "check" => Some(HelpDoc {
             usage: "vp check [OPTIONS] [PATHS]...",
@@ -737,6 +773,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     ],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["check"]),
         }),
         "pack" => Some(HelpDoc {
             usage: "vp pack [...FILES] [OPTIONS]",
@@ -759,6 +796,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     vec!["  vp pack", "  vp pack src/index.ts --dts", "  vp pack --watch"],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["pack"]),
         }),
         "run" => Some(HelpDoc {
             usage: "vp run [OPTIONS] [TASK_SPECIFIER] [ADDITIONAL_ARGS]...",
@@ -809,6 +847,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     ],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["run"]),
         }),
         "exec" => Some(HelpDoc {
             usage: "vp exec [OPTIONS] [COMMAND]...",
@@ -862,6 +901,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                     ],
                 ),
             ],
+            documentation_url: documentation_url_for_command_path(&["exec"]),
         }),
         "cache" => Some(HelpDoc {
             usage: "vp cache <COMMAND>",
@@ -870,6 +910,7 @@ fn delegated_help_doc(command: &str) -> Option<HelpDoc> {
                 section_rows("Commands", vec![row("clean", "Clean up all the cache")]),
                 section_rows("Options", vec![row("-h, --help", "Print help")]),
             ],
+            documentation_url: documentation_url_for_command_path(&["cache"]),
         }),
         _ => None,
     }
@@ -1010,6 +1051,11 @@ pub fn print_unified_clap_help_for_path(command_path: &[&str]) -> bool {
     let Some(doc) = parse_clap_help_to_doc(&raw_help) else {
         return false;
     };
+    let doc = OwnedHelpDoc {
+        documentation_url: documentation_url_for_command_path(command_path)
+            .map(ToString::to_string),
+        ..doc
+    };
 
     println!("{}", vite_shared::header::vite_plus_header());
     println!();
@@ -1020,8 +1066,8 @@ pub fn print_unified_clap_help_for_path(command_path: &[&str]) -> bool {
 #[cfg(test)]
 mod tests {
     use super::{
-        has_help_flag_before_terminator, parse_clap_help_to_doc, parse_rows, split_comment_suffix,
-        strip_ansi,
+        HelpDoc, documentation_url_for_command_path, has_help_flag_before_terminator,
+        parse_clap_help_to_doc, parse_rows, render_help_doc, split_comment_suffix, strip_ansi,
     };
 
     #[test]
@@ -1110,4 +1156,32 @@ Options:
     fn split_comment_suffix_returns_none_without_comment() {
         assert!(split_comment_suffix("  vp env list").is_none());
     }
+
+    #[test]
+    fn docs_url_is_mapped_for_grouped_commands() {
+        assert_eq!(
+            documentation_url_for_command_path(&["add"]),
+            Some("https://viteplus.dev/guide/install")
+        );
+        assert_eq!(
+            documentation_url_for_command_path(&["env", "list"]),
+            Some("https://viteplus.dev/guide/env")
+        );
+        assert_eq!(
+            documentation_url_for_command_path(&["config"]),
+            Some("https://viteplus.dev/guide/commit-hooks")
+        );
+    }
+
+    #[test]
+    fn render_help_doc_appends_documentation_footer() {
+        let output = render_help_doc(&HelpDoc {
+            usage: "vp demo",
+            summary: vec![],
+            sections: vec![],
+            documentation_url: Some("https://viteplus.dev/guide/demo"),
+        });
+
+        assert!(output.contains("Documentation: https://viteplus.dev/guide/demo"));
+    }
 }
diff --git a/docs/.vitepress/config.mts b/docs/.vitepress/config.mts
index f531d60c2c..84d1cc9bd9 100644
--- a/docs/.vitepress/config.mts
+++ b/docs/.vitepress/config.mts
@@ -4,7 +4,76 @@ import type { VoidZeroThemeConfig } from '@voidzero-dev/vitepress-theme';
 import { extendConfig } from '@voidzero-dev/vitepress-theme/config';
 import { defineConfig, type HeadConfig } from 'vitepress';
 
-// https://vitepress.dev/reference/site-config
+const taskRunnerGuideItems = [
+  {
+    text: 'Run',
+    link: '/guide/run',
+  },
+  {
+    text: 'Task Caching',
+    link: '/guide/cache',
+  },
+  {
+    text: 'Running Binaries',
+    link: '/guide/vpx',
+  },
+];
+
+const guideSidebar = [
+  {
+    text: 'Introduction',
+    items: [
+      { text: 'Getting Started', link: '/guide/' },
+      { text: 'Creating a Project', link: '/guide/create' },
+      { text: 'Migrate to Vite+', link: '/guide/migrate' },
+      { text: 'Installing Dependencies', link: '/guide/install' },
+      { text: 'Environment', link: '/guide/env' },
+    ],
+  },
+  {
+    text: 'Develop',
+    items: [
+      { text: 'Dev', link: '/guide/dev' },
+      {
+        text: 'Check',
+        link: '/guide/check',
+        items: [
+          { text: 'Lint', link: '/guide/lint' },
+          { text: 'Format', link: '/guide/fmt' },
+        ],
+      },
+      { text: 'Test', link: '/guide/test' },
+    ],
+  },
+  {
+    text: 'Execute',
+    items: taskRunnerGuideItems,
+  },
+  {
+    text: 'Build',
+    items: [
+      { text: 'Build', link: '/guide/build' },
+      { text: 'Pack', link: '/guide/pack' },
+    ],
+  },
+  {
+    text: 'Maintain',
+    items: [
+      { text: 'Upgrading Vite+', link: '/guide/upgrade' },
+      { text: 'Removing Vite+', link: '/guide/implode' },
+    ],
+  },
+  {
+    text: 'Workflow',
+    items: [
+      { text: 'IDE Integration', link: '/guide/ide-integration' },
+      { text: 'CI', link: '/guide/ci' },
+      { text: 'Commit Hooks', link: '/guide/commit-hooks' },
+      { text: 'Troubleshooting', link: '/guide/troubleshooting' },
+    ],
+  },
+];
+
 export default extendConfig(
   defineConfig({
     title: 'Vite+',
@@ -35,7 +104,6 @@ export default extendConfig(
           defer: '',
         },
       ],
-      // ["script", {}, "document.documentElement.setAttribute('data-theme', 'light')"],
     ],
     vite: {
       resolve: {
@@ -51,665 +119,62 @@ export default extendConfig(
       nav: [
         {
           text: 'Guide',
-          activeMatch: '/vite/guide/',
-          items: [
-            { text: 'Vite Core', link: '/vite/guide/' },
-            { text: 'Test', link: '/vite/guide/test/getting-started' },
-            { text: 'Lint', link: '/vite/guide/lint/getting-started' },
-            { text: 'Format', link: '/vite/guide/format/getting-started' },
-            { text: 'Task Runner', link: '/vite/guide/task/getting-started' },
-            { text: 'Library Bundler', link: '/lib/guide/getting-started' },
-            { text: 'DevTools', link: '/guide/devtools/getting-started' },
-            { text: 'Package Manager', link: '/guide/package-manager/getting-started' },
-          ],
+          link: '/guide/',
+          activeMatch: '^/guide/',
         },
         {
           text: 'Config',
-          activeMatch: '/config/',
-          items: [
-            { text: 'Vite Core', link: '/config/' },
-            { text: 'Test', link: '/config/test' },
-            { text: 'Lint', link: '/config/lint' },
-            { text: 'Format', link: '/config/format' },
-            { text: 'Task Runner', link: '/vite/guide/task/config' },
-            { text: 'Package Manager', link: '/config/package-manager' },
-          ],
+          link: '/config/',
+          activeMatch: '^/config/',
         },
-        {
-          text: 'APIs',
-          activeMatch: '/apis/',
-          items: [
-            { text: 'Vite API', link: '/apis/' },
-            { text: 'Environment API', link: '/apis/environment' },
-            { text: 'Test API', link: '/apis/test' },
-            { text: 'Lint API', link: '/apis/lint' },
-            { text: 'Format API', link: '/apis/format' },
-            { text: 'Task Runner API', link: '/apis/task-runner' },
-          ],
-        },
-        {
-          text: 'Plugins',
-          activeMatch: '/plugins/',
-          items: [
-            { text: 'Vite Plugins', link: '/plugins/' },
-            { text: 'Test Plugins', link: '/plugins/test' },
-            { text: 'Lint Plugins', link: '/plugins/lint' },
-            { text: 'Format Plugins', link: '/plugins/format' },
-            { text: 'Task Runner Plugins', link: '/plugins/task-runner' },
-          ],
-        },
-        // {
-        //   text: 'Test',
-        //   activeMatch: '/plugins/',
-        //   items: [
-        //     { text: 'Guide & API', link: '/test/guide/' },
-        //     { text: 'Config', link: '/test/config/' },
-        //     { text: 'Browser Mode', link: '/test/browser-mode/' },
-        //   ],
-        // },
-        // {
-        //   text: 'Format',
-        //   activeMatch: '/plugins/',
-        //   items: [
-        //     { text: 'Guide & API', link: '/test/guide/' },
-        //     { text: 'Config', link: '/test/config/' },
-        //     { text: 'Browser Mode', link: '/test/browser-mode/' },
-        //   ],
-        // },
         {
           text: 'Resources',
           items: [
-            { text: 'Team', link: 'https://voidzero.dev/team' },
-            { text: 'Blog', link: 'https://voidzero.dev/blog' },
+            { text: 'GitHub', link: 'https://github.com/voidzero-dev/vite-plus' },
             { text: 'Releases', link: 'https://github.com/voidzero-dev/vite-plus/releases' },
             {
-              items: [
-                {
-                  text: 'Awesome Vite+',
-                  link: 'https://github.com/voidzero-dev/awesome-vite-plus',
-                },
-                {
-                  text: 'ViteConf',
-                  link: 'https://viteconf.org',
-                },
-                {
-                  text: 'DEV Community',
-                  link: 'https://dev.to/t/vite',
-                },
-                {
-                  text: 'Changelog',
-                  link: 'https://github.com/voidzero-dev/vite-plus/releases',
-                },
-                {
-                  text: 'Contributing',
-                  link: 'https://github.com/voidzero-dev/vite-plus/blob/main/CONTRIBUTING.md',
-                },
-              ],
-            },
-          ],
-        },
-      ],
-
-      sidebar: {
-        '/vite/guide/': {
-          base: '/vite/guide/',
-          items: [
-            {
-              text: 'Introduction',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: 'index',
-                },
-                {
-                  text: 'Monorepo',
-                  link: 'monorepo',
-                },
-                {
-                  text: 'Philosophy',
-                  link: 'philosophy',
-                },
-                {
-                  text: 'Why Vite+',
-                  link: 'why',
-                },
-                {
-                  text: 'Migration',
-                  link: 'migration',
-                },
-              ],
-            },
-            {
-              text: 'Vite Core',
-              items: [
-                {
-                  text: 'Features',
-                  link: 'features',
-                },
-                {
-                  text: 'CLI',
-                  link: 'cli',
-                },
-                {
-                  text: 'Using Plugins',
-                  link: 'using-plugins',
-                },
-                {
-                  text: 'Dependency Pre-Bundling',
-                  link: 'dependency-pre-bundling',
-                },
-                {
-                  text: 'Static Asset Handling',
-                  link: 'static-asset-handling',
-                },
-                {
-                  text: 'Building for Production',
-                  link: 'building-for-production',
-                },
-                {
-                  text: 'Deploying a Static Site',
-                  link: 'deploying-a-static-site',
-                },
-                {
-                  text: 'Env Variables and Modes',
-                  link: 'env-variables-and-modes',
-                },
-                {
-                  text: 'Server-Side Rendering',
-                  link: 'server-side-rendering',
-                },
-                {
-                  text: 'Backend Integration',
-                  link: 'backend-integration',
-                },
-                {
-                  text: 'Troubleshooting',
-                  link: 'troubleshooting',
-                },
-                {
-                  text: 'Performance',
-                  link: 'performance',
-                },
-                {
-                  text: 'Migration from vite@7+',
-                  link: 'migration',
-                },
-              ],
-            },
-            {
-              text: 'Test',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: '/guide/test/getting-started',
-                },
-                {
-                  text: 'Features',
-                  link: '/guide/test/features',
-                },
-                {
-                  text: 'CLI',
-                  link: '/guide/test/cli',
-                },
-                {
-                  text: 'Test Filtering',
-                  link: '/guide/test/test-filtering',
-                },
-                {
-                  text: '...',
-                  link: '/guide/test/dependency-pre-bundling',
-                },
-                {
-                  text: 'Migration from vitest',
-                  link: '/guide/test/migration-from-vitest',
-                },
-              ],
-            },
-            {
-              text: 'Lint',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: '/guide/lint/getting-started',
-                },
-                {
-                  text: 'Features',
-                  link: '/guide/lint/features',
-                },
-                {
-                  text: 'CLI',
-                  link: '/guide/lint/cli',
-                },
-                {
-                  text: '...',
-                  link: '/guide/test/dependency-pre-bundling',
-                },
-                {
-                  text: 'Migration from oxlint',
-                  link: '/guide/test/migration-from-oxlint',
-                },
-                {
-                  text: 'Migration from ESLint',
-                  link: '/guide/test/migration-from-eslint',
-                },
-              ],
-            },
-            {
-              text: 'Format',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: '/guide/format/getting-started',
-                },
-                {
-                  text: 'Features',
-                  link: '/guide/format/features',
-                },
-                {
-                  text: 'CLI',
-                  link: '/guide/format/cli',
-                },
-                {
-                  text: 'Migration from oxfmt',
-                  link: '/guide/format/migration-from-oxfmt',
-                },
-                {
-                  text: 'Migration from Prettier',
-                  link: '/guide/format/migration-from-prettier',
-                },
-              ],
-            },
-            {
-              text: 'Task Runner',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: 'task/getting-started',
-                },
-                {
-                  text: 'Running Tasks',
-                  link: 'task/running-tasks',
-                },
-                {
-                  text: 'Caching',
-                  link: 'task/caching',
-                },
-                {
-                  text: 'CLI',
-                  link: 'task/cli',
-                },
-                {
-                  text: 'Config',
-                  link: 'task/config',
-                },
-              ],
-            },
-            {
-              text: 'Library Bundler',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: '/guide/library/getting-started',
-                },
-                {
-                  text: 'Features',
-                  link: '/guide/library/features',
-                },
-                {
-                  text: 'CLI',
-                  link: '/guide/library/cli',
-                },
-                {
-                  text: 'Migration from tsdown',
-                  link: '/guide/library/migration-from-tsdown',
-                },
-                {
-                  text: 'Migration from tsup',
-                  link: '/guide/library/migration-from-tsup',
-                },
-                {
-                  text: 'Migration from esbuild',
-                  link: '/guide/library/migration-from-esbuild',
-                },
-              ],
-            },
-            {
-              text: 'DevTools',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: '/guide/devtools/getting-started',
-                },
-                {
-                  text: 'Features',
-                  link: '/guide/library/features',
-                },
-                {
-                  text: 'CLI',
-                  link: '/guide/devtools/cli',
-                },
-              ],
-            },
-            {
-              text: 'Package Manager',
-              items: [
-                {
-                  text: 'Getting Started',
-                  link: '/guide/package-manager/getting-started',
-                },
-                {
-                  text: 'Features',
-                  link: '/guide/package-manager/features',
-                },
-                {
-                  text: 'CLI',
-                  link: '/guide/package-manager/cli',
-                },
-              ],
-            },
-          ],
-        },
-        '/lib/guide/': {
-          base: '/lib/guide/',
-          items: [
-            {
-              text: 'Library Bundler',
-              items: [
-                {
-                  text: 'Introduction',
-                  link: 'introduction',
-                },
-                {
-                  text: 'Getting Started',
-                  link: 'getting-started',
-                },
-                {
-                  text: 'Migration from tsdown',
-                  link: '/guide/library/migration-from-tsdown',
-                },
-                {
-                  text: 'Migration from tsup',
-                  link: '/guide/library/migration-from-tsup',
-                },
-                {
-                  text: 'Migration from esbuild',
-                  link: '/guide/library/migration-from-esbuild',
-                },
-              ],
-            },
-            {
-              text: 'Options',
-              items: [
-                {
-                  text: 'Entry',
-                  link: 'entry',
-                },
-                {
-                  text: 'Config File',
-                  link: 'config-file',
-                },
-                {
-                  text: 'Declaration Files (dts)',
-                  link: 'dts',
-                },
-              ],
-            },
-            {
-              text: 'Recipes',
-              items: [
-                {
-                  text: 'Vue Support',
-                  link: 'vue-support',
-                },
-                {
-                  text: 'React Support',
-                  link: 'react-support',
-                },
-                {
-                  text: 'Svelte Support',
-                  link: 'svelte-support',
-                },
-              ],
-            },
-            {
-              text: 'Advanced',
-              items: [
-                {
-                  text: 'Plugins',
-                  link: 'plugins',
-                },
-                {
-                  text: 'Hooks',
-                  link: 'hooks',
-                },
-                {
-                  text: 'Rolldown Options',
-                  link: 'rolldown-options',
-                },
-                {
-                  text: 'Programmatic Usage',
-                  link: 'programmatic-usage',
-                },
-              ],
+              text: 'Announcement',
+              link: 'https://voidzero.dev/posts/announcing-vite-plus-alpha',
             },
             {
-              text: 'API Reference',
-              items: [
-                {
-                  text: 'Command Line Interface',
-                  link: 'command-line-interface',
-                },
-                {
-                  text: 'Config Options',
-                  link: 'config-options',
-                },
-                {
-                  text: 'Type Definitions',
-                  items: [
-                    {
-                      text: 'AttwOptions',
-                      link: 'attributes-options',
-                    },
-                    {
-                      text: 'BuildContext',
-                      link: 'build-context',
-                    },
-                  ],
-                },
-              ],
+              text: 'Contributing',
+              link: 'https://github.com/voidzero-dev/vite-plus/blob/main/CONTRIBUTING.md',
             },
           ],
         },
+      ],
+      sidebar: {
+        '/guide/': guideSidebar,
         '/config/': [
           {
-            text: 'Vite Core',
-            items: [
-              {
-                text: 'Configuring Vite+',
-                link: '/config/',
-              },
-              {
-                text: 'Shared Options',
-                link: '/config/shared-options',
-              },
-              {
-                text: 'Server Options',
-                link: '/config/server-options',
-              },
-              {
-                text: 'Build Options',
-                link: '/config/build-options',
-              },
-              {
-                text: 'Preview Options',
-                link: '/config/preview-options',
-              },
-              {
-                text: 'Dep Optimization Options',
-                link: '/config/dep-optimization-options',
-              },
-              {
-                text: 'SSR Options',
-                link: '/config/ssr-options',
-              },
-              {
-                text: 'Worker Options',
-                link: '/config/worker-options',
-              },
-            ],
-          },
-          {
-            text: 'Test',
+            text: 'Configuration',
             items: [
-              {
-                text: 'Configuring Test',
-                link: '/config/test',
-              },
-              {
-                text: 'Test Options',
-                link: '/config/test-options',
-              },
-            ],
-          },
-          {
-            text: 'Lint',
-            items: [
-              {
-                text: 'Configuring Lint',
-                link: '/config/lint',
-              },
-              {
-                text: 'Lint Options',
-                link: '/config/lint-options',
-              },
-            ],
-          },
-          {
-            text: 'Task Runner',
-            items: [
-              {
-                text: 'Configuring Task Runner',
-                link: '/vite/guide/task/config',
-              },
+              { text: 'Configuring Vite+', link: '/config/' },
+              { text: 'Run', link: '/config/run' },
+              { text: 'Format', link: '/config/fmt' },
+              { text: 'Lint', link: '/config/lint' },
+              { text: 'Test', link: '/config/test' },
+              { text: 'Build', link: '/config/build' },
+              { text: 'Pack', link: '/config/pack' },
+              { text: 'Staged', link: '/config/staged' },
             ],
           },
         ],
-        '/apis/': [
-          {
-            text: 'Vite Core API',
-            items: [
-              {
-                text: 'Plugin API',
-                link: '/apis/vite/plugin',
-              },
-              {
-                text: 'HMR API',
-                link: '/apis/vite/hmr',
-              },
-              {
-                text: 'JavaScript API',
-                link: '/apis/vite/javascript',
-              },
-            ],
-          },
-          {
-            text: 'Environment API',
-            items: [
-              {
-                text: 'Introduction',
-                link: '/apis/environment/introduction',
-              },
-              {
-                text: 'Environment Instances',
-                link: '/apis/environment/instances',
-              },
-              {
-                text: 'Plugins',
-                link: '/apis/environment/plugins',
-              },
-              {
-                text: 'Frameworks',
-                link: '/apis/environment/frameworks',
-              },
-              {
-                text: 'Runtimes',
-                link: '/apis/environment/runtimes',
-              },
-            ],
-          },
-          {
-            text: 'Test API',
-            items: [
-              {
-                text: 'Introduction',
-                link: '/apis/test/introduction',
-              },
-              {
-                text: 'Plugin API',
-                link: '/apis/test/plugin',
-              },
-            ],
-          },
-          {
-            text: 'Lint API',
-            items: [
-              {
-                text: 'Introduction',
-                link: '/apis/lint/introduction',
-              },
-              {
-                text: 'Plugin API',
-                link: '/apis/lint/plugin',
-              },
-            ],
-          },
-          {
-            text: 'Format API',
-            items: [
-              {
-                text: 'Introduction',
-                link: '/apis/format/introduction',
-              },
-              {
-                text: 'Plugin API',
-                link: '/apis/format/plugin',
-              },
-            ],
-          },
-          {
-            text: 'Task Runner API',
-            items: [
-              {
-                text: 'Introduction',
-                link: '/apis/task-runner/introduction',
-              },
-              {
-                text: 'Plugin API',
-                link: '/apis/task-runner/plugin',
-              },
-            ],
-          },
-        ],
-        '/changes/': [],
       },
-
       socialLinks: [
         { icon: 'github', link: 'https://github.com/voidzero-dev/vite-plus' },
         { icon: 'x', link: 'https://x.com/voidzerodev' },
         { icon: 'discord', link: 'https://discord.gg/cC6TEVFKSx' },
         { icon: 'bluesky', link: 'https://bsky.app/profile/voidzero.dev' },
       ],
-
       outline: {
         level: [2, 3],
       },
-
       search: {
         provider: 'local',
       },
     },
     transformHead({ page, pageData }) {
-      // Remove .md suffix and replace index with empty string (to cover index.md)
       const url = 'https://viteplus.dev/' + page.replace(/\.md$/, '').replace(/index$/, '');
 
       const canonicalUrlEntry: HeadConfig = [
diff --git a/docs/.vitepress/theme/components/Footer.vue b/docs/.vitepress/theme/components/Footer.vue
index 4bb367932c..f3298acd2f 100644
--- a/docs/.vitepress/theme/components/Footer.vue
+++ b/docs/.vitepress/theme/components/Footer.vue
@@ -13,15 +13,7 @@
           Take your team's productivity to the next level with Vite+
         </h2>
         <div class="flex items-center gap-5">
-          <a href="/vite/guide" target="_self" class="button button--white">Get started</a>
-          <!-- <a
-            href="https://voidzero.dev/posts/announcing-vite-plus?utm_source=viteplusdev&utm_content=bottom_learn_more"
-            target="_blank"
-            rel="noopener noreferrer"
-            class="button button--white"
-          >
-            Learn more
-          </a> -->
+          <a href="/guide" target="_self" class="button button--white">Get started</a>
         </div>
       </div>
       <div
@@ -66,7 +58,6 @@
                 >Rolldown</a
               >
             </li>
-
             <li>
               <a
                 href="https://oxc.rs/"
diff --git a/docs/.vitepress/theme/components/Header.vue b/docs/.vitepress/theme/components/Header.vue
index 6f4b778b46..d7f64b4bef 100644
--- a/docs/.vitepress/theme/components/Header.vue
+++ b/docs/.vitepress/theme/components/Header.vue
@@ -1,14 +1,12 @@
 <script setup lang="ts">
 import { Icon } from '@iconify/vue';
-import { ref, onMounted, onUnmounted } from 'vue';
+import { onMounted, onUnmounted, ref } from 'vue';
 
-const nav = [{ text: 'Docs', link: '/vite/guide' }];
+const nav = [{ text: 'Docs', link: '/guide' }];
 
-// Mobile menu state
 const mobileMenuOpen = ref(false);
 const expandedMobileItem = ref<string | null>(null);
 
-// Body scroll lock for mobile menu
 const lockBodyScroll = () => {
   const scrollbarWidth = window.innerWidth - document.documentElement.clientWidth;
   document.body.style.overflow = 'hidden';
@@ -28,23 +26,18 @@ const unlockBodyScroll = () => {
   document.body.style.paddingRight = '';
 };
 
-// Close mobile menu
 const closeMobileMenu = () => {
   mobileMenuOpen.value = false;
   expandedMobileItem.value = null;
   unlockBodyScroll();
 };
 
-// Handle keyboard navigation
 const handleKeydown = (e: KeyboardEvent) => {
-  if (e.key === 'Escape') {
-    if (mobileMenuOpen.value) {
-      closeMobileMenu();
-    }
+  if (e.key === 'Escape' && mobileMenuOpen.value) {
+    closeMobileMenu();
   }
 };
 
-// Toggle mobile menu
 const toggleMobileMenu = () => {
   mobileMenuOpen.value = !mobileMenuOpen.value;
   if (mobileMenuOpen.value) {
@@ -67,20 +60,20 @@ onUnmounted(() => {
 </script>
 
 <template>
-  <header class="wrapper px-6 py-7 flex items-center justify-between">
-    <div class="flex items-center gap-10">
-      <a href="/">
+  <header class="wrapper px-6 py-5 flex items-center justify-between relative">
+    <div class="flex gap-10 self-stretch">
+      <a href="/" class="flex flex-col items-start justify-center -mx-2 px-2">
         <img class="h-4" src="/logo.svg" alt="Vite+" />
       </a>
 
-      <!-- Desktop navigation - hidden on mobile -->
-      <nav class="nav-container hidden md:block">
-        <ul class="nav">
-          <li v-for="navItem in nav" :key="navItem.link" class="inline-block px-5">
+      <nav class="nav-container hidden lg:flex items-center gap-4">
+        <ul class="nav flex items-center gap-1">
+          <li v-for="navItem in nav" :key="navItem.link">
             <a
               :href="navItem.link"
               :target="navItem.link?.startsWith('http') ? '_blank' : '_self'"
               :rel="navItem.link?.startsWith('http') ? 'noopener noreferrer' : undefined"
+              class="flex items-center gap-1 px-3 py-2 text-base font-heading text-primary hover:opacity-85 transition-opacity whitespace-nowrap"
             >
               {{ navItem.text }}
               <svg
@@ -115,15 +108,14 @@ onUnmounted(() => {
           <img class="h-3" src="@assets/logos/voidzero-dark.svg" alt="VoidZero" />
         </a>
       </span>
-      <a href="/vite/guide" target="_self" class="button hidden md:block"> Get started </a>
+      <a href="/guide" target="_self" class="button hidden lg:block"> Get started </a>
 
-      <!-- Mobile hamburger/close button - Right aligned -->
       <button
         @click="toggleMobileMenu"
         :aria-expanded="mobileMenuOpen"
         aria-controls="mobile-menu"
         aria-label="Toggle navigation menu"
-        class="md:hidden p-2 -mr-2 text-primary dark:text-white hover:opacity-70 transition-opacity cursor-pointer"
+        class="lg:hidden p-2 -mr-2 text-primary dark:text-white hover:opacity-70 transition-opacity cursor-pointer"
         type="button"
       >
         <svg
@@ -148,7 +140,6 @@ onUnmounted(() => {
     </div>
   </header>
 
-  <!-- Mobile Menu Overlay - Full Screen -->
   <div
     v-if="mobileMenuOpen"
     id="mobile-menu"
@@ -156,10 +147,9 @@ onUnmounted(() => {
     aria-modal="true"
     aria-label="Mobile navigation menu"
     data-theme="dark"
-    class="md:hidden fixed inset-0 z-[1001] bg-primary"
+    class="lg:hidden fixed inset-0 z-[1001] bg-primary"
   >
     <section class="wrapper animate-fade-in">
-      <!-- Internal Header with Logo and Close Button -->
       <div class="w-full pl-5 pr-7 py-5 lg:py-7 flex items-center justify-between">
         <a href="/">
           <img class="h-4" src="@assets/logos/viteplus-light.svg" alt="Vite+" />
@@ -188,16 +178,13 @@ onUnmounted(() => {
         </button>
       </div>
 
-      <!-- Scrollable content container -->
       <div
         class="overflow-y-auto flex flex-col [scrollbar-width:none] [-ms-overflow-style:none] [&::-webkit-scrollbar]:hidden"
         style="height: calc(100vh - 88px)"
       >
-        <!-- Navigation Items - Top Section -->
         <nav class="flex-1 w-full pt-6 pb-8">
           <ul class="space-y-1">
             <li v-for="navItem in nav" :key="navItem.link">
-              <!-- :class="{ 'bg-white/10': route.path === navItem.link }" -->
               <a
                 :href="navItem.link"
                 @click="closeMobileMenu"
@@ -230,13 +217,11 @@ onUnmounted(() => {
           </ul>
         </nav>
 
-        <!-- Bottom Section - CTA and Social -->
         <div class="w-full py-12 border-t border-nickel relative tick-left tick-right mt-auto">
           <div class="space-y-12">
-            <!-- CTA Button -->
             <div class="px-6">
               <a
-                href="/vite/guide"
+                href="/guide"
                 target="_self"
                 class="button button--primary button--white block text-center bg-white text-primary hover:bg-white/90"
                 @click="closeMobileMenu"
@@ -245,10 +230,8 @@ onUnmounted(() => {
               </a>
             </div>
 
-            <!-- Divider -->
             <div class="border-t border-nickel tick-left tick-right relative"></div>
 
-            <!-- Social Icons -->
             <div class="flex items-center justify-center gap-4 pb-12">
               <a
                 href="https://github.com/voidzero-dev"
@@ -318,9 +301,4 @@ onUnmounted(() => {
     opacity: 1;
   }
 }
-
-.animate-fade-in {
-  animation: fadeIn 300ms ease-out 100ms forwards;
-  opacity: 0;
-}
 </style>
diff --git a/docs/.vitepress/theme/components/home/Hero.vue b/docs/.vitepress/theme/components/home/Hero.vue
index 4b9dbe4a37..4f42426625 100644
--- a/docs/.vitepress/theme/components/home/Hero.vue
+++ b/docs/.vitepress/theme/components/home/Hero.vue
@@ -13,7 +13,7 @@
         <p class="text-sm text-grey">Free and open source under the MIT license.</p>
       </div>
       <div class="flex items-center gap-5">
-        <a href="/vite/guide" target="_self" class="button button--primary"> Get started </a>
+        <a href="/guide" target="_self" class="button button--primary"> Get started </a>
         <a
           href="https://voidzero.dev/posts/announcing-vite-plus-alpha"
           target="_blank"
diff --git a/docs/.vitepress/theme/components/home/InstallCommand.vue b/docs/.vitepress/theme/components/home/InstallCommand.vue
index 025f10e07d..9773e94115 100644
--- a/docs/.vitepress/theme/components/home/InstallCommand.vue
+++ b/docs/.vitepress/theme/components/home/InstallCommand.vue
@@ -12,12 +12,12 @@ const commandCards: CommandCard[] = [
   {
     id: 'unix',
     label: 'macOS / Linux',
-    command: 'curl -fsSL https://viteplus.dev/install.sh | bash',
+    command: 'curl -fsSL https://vite.plus | bash',
   },
   {
     id: 'windows',
     label: 'Windows (PowerShell)',
-    command: 'irm https://viteplus.dev/install.ps1 | iex',
+    command: 'irm https://vite.plus/ps1 | iex',
   },
 ];
 
diff --git a/docs/apis/index.md b/docs/apis/index.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/config/build.md b/docs/config/build.md
new file mode 100644
index 0000000000..403d0b799a
--- /dev/null
+++ b/docs/config/build.md
@@ -0,0 +1,21 @@
+# 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
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  server: {
+    port: 3000,
+  },
+  build: {
+    sourcemap: true,
+  },
+  preview: {
+    port: 4173,
+  },
+});
+```
diff --git a/docs/config/fmt.md b/docs/config/fmt.md
new file mode 100644
index 0000000000..3b958179fb
--- /dev/null
+++ b/docs/config/fmt.md
@@ -0,0 +1,18 @@
+# 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
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  fmt: {
+    ignorePatterns: ['dist/**'],
+    singleQuote: true,
+    semi: true,
+    experimentalSortPackageJson: true,
+  },
+});
+```
diff --git a/docs/config/index.md b/docs/config/index.md
index e69de29bb2..78807ce104 100644
--- a/docs/config/index.md
+++ b/docs/config/index.md
@@ -0,0 +1,31 @@
+# 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
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  server: {},
+  build: {},
+  preview: {},
+
+  test: {},
+  lint: {},
+  fmt: {},
+  run: {},
+  pack: {},
+  staged: {},
+});
+```
+
+## Vite+ Specific Configuration
+
+Vite+ extends the basic Vite configuration with these additions:
+
+- [`lint`](/config/lint) for Oxlint
+- [`fmt`](/config/fmt) for Oxfmt
+- [`test`](/config/test) for Vitest
+- [`run`](/config/run) for Vite Task
+- [`pack`](/config/pack) for tsdown
+- [`staged`](/config/staged) for staged-file checks
diff --git a/docs/config/lint.md b/docs/config/lint.md
new file mode 100644
index 0000000000..a2e74a8f05
--- /dev/null
+++ b/docs/config/lint.md
@@ -0,0 +1,24 @@
+# Lint Config
+
+`vp lint` and `vp check` read Oxlint settings from the `lint` block in `vite.config.ts`. See [Oxlint's configuration](https://oxc.rs/docs/guide/usage/linter/config.html) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  lint: {
+    ignorePatterns: ['dist/**'],
+    options: {
+      typeAware: true,
+      typeCheck: true,
+    },
+    rules: {
+      'no-console': ['error', { allow: ['error'] }],
+    },
+  },
+});
+```
+
+We recommend enabling both `options.typeAware` and `options.typeCheck` so `vp lint` and `vp check` can use the full type-aware path.
diff --git a/docs/config/pack.md b/docs/config/pack.md
new file mode 100644
index 0000000000..fc8341c13f
--- /dev/null
+++ b/docs/config/pack.md
@@ -0,0 +1,17 @@
+# Pack Config
+
+`vp pack` reads tsdown settings from the `pack` block in `vite.config.ts`. See [tsdown's configuration](https://tsdown.dev/options/config-file) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  pack: {
+    dts: true,
+    format: ['esm', 'cjs'],
+    sourcemap: true,
+  },
+});
+```
diff --git a/docs/vite/guide/task/config.md b/docs/config/run.md
similarity index 60%
rename from docs/vite/guide/task/config.md
rename to docs/config/run.md
index 02070916f7..48b6cad8a3 100644
--- a/docs/vite/guide/task/config.md
+++ b/docs/config/run.md
@@ -1,8 +1,8 @@
-# Task Runner Config
+# Run Config
 
-The task runner is configured under the `run` field in your `vite.config.ts`:
+You can configure Vite Task under the `run` field in `vite.config.ts`. Check out [`vp run`](/guide/run) to learn more about running scripts and tasks with Vite+.
 
-```ts [vite.config.ts]
+```ts
 import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
@@ -17,14 +17,14 @@ export default defineConfig({
 });
 ```
 
-## `run.cache` {#run-cache}
+## `run.cache`
 
 - **Type:** `boolean | { scripts?: boolean, tasks?: boolean }`
 - **Default:** `{ scripts: false, tasks: true }`
 
-Global cache settings. Controls whether task results are cached and replayed on subsequent runs.
+Controls whether task results are cached and replayed on subsequent runs.
 
-```ts [vite.config.ts]
+```ts
 export default defineConfig({
   run: {
     cache: {
@@ -35,40 +35,20 @@ export default defineConfig({
 });
 ```
 
-Shorthands: `cache: true` enables both, `cache: false` disables both.
+`cache: true` enables both task and script caching, `cache: false` disables both.
 
-Tasks defined in `vite.config.ts` are cached by default. Plain `package.json` scripts (without a matching task entry) are **not** cached by default. See [When Is Caching Enabled?](./caching#when-is-caching-enabled) for the full resolution order including CLI overrides.
-
-## `run.tasks` {#run-tasks}
+## `run.tasks`
 
 - **Type:** `Record<string, TaskConfig>`
 
-Defines named tasks. Each key is a task name that can be run with `vp run <name>`.
+Defines tasks that can be run with `vp run <task>`.
 
-```ts [vite.config.ts]
-export default defineConfig({
-  run: {
-    tasks: {
-      build: {
-        command: 'vp build',
-        dependsOn: ['lint'],
-      },
-      lint: {
-        command: 'vp lint',
-      },
-    },
-  },
-});
-```
-
-If a task name matches a script in `package.json`, the script is used automatically when `command` is omitted. See [Getting Started](./getting-started#task-definitions) for details.
-
-### `command` {#command}
+### `command`
 
 - **Type:** `string`
 - **Default:** matching `package.json` script
 
-Shell command to run. If omitted, uses the script with the same name from `package.json`.
+The shell command to run.
 
 ```ts
 tasks: {
@@ -78,11 +58,11 @@ tasks: {
 }
 ```
 
-You cannot define a command in both `vite.config.ts` and `package.json` for the same task name — it's one or the other.
+You cannot define a command in both `vite.config.ts` and `package.json` with the same task name.
 
-Commands joined with `&&` are automatically split into independently cached sub-tasks. See [Compound Commands](./running-tasks#compound-commands).
+Commands joined with `&&` are automatically split into independently cached sub-tasks. See [Compound Commands](/guide/run#compound-commands).
 
-### `dependsOn` {#depends-on}
+### `dependsOn`
 
 - **Type:** `string[]`
 - **Default:** `[]`
@@ -104,9 +84,9 @@ Dependencies can reference tasks in other packages using the `package#task` form
 dependsOn: ['@my/core#build', '@my/utils#lint'];
 ```
 
-See [Task Dependencies](./getting-started#task-dependencies) for details on how explicit and topological dependencies interact.
+See [Task Dependencies](/guide/run#task-dependencies) for details on how explicit and topological dependencies interact.
 
-### `cache` {#cache}
+### `cache`
 
 - **Type:** `boolean`
 - **Default:** `true`
@@ -122,7 +102,7 @@ tasks: {
 }
 ```
 
-### `envs` {#envs}
+### `envs`
 
 - **Type:** `string[]`
 - **Default:** `[]`
@@ -140,12 +120,12 @@ tasks: {
 
 Wildcard patterns are supported: `VITE_*` matches all variables starting with `VITE_`.
 
-```
+```bash
 $ NODE_ENV=development vp run build    # first run
-$ NODE_ENV=production vp run build     # cache miss: envs changed
+$ NODE_ENV=production vp run build     # cache miss: variable changed
 ```
 
-### `passThroughEnvs` {#pass-through-envs}
+### `passThroughEnvs`
 
 - **Type:** `string[]`
 - **Default:** see below
@@ -168,12 +148,12 @@ A set of common environment variables are automatically passed through to all ta
 - **CI/CD:** `CI`, `VERCEL_*`, `NEXT_*`
 - **Terminal:** `TERM`, `COLORTERM`, `FORCE_COLOR`, `NO_COLOR`
 
-### `inputs` {#inputs}
+### `inputs`
 
 - **Type:** `Array<string | { auto: boolean }>`
 - **Default:** `[{ auto: true }]` (auto-inferred)
 
-Files to track for cache invalidation. By default, the task runner automatically detects which files a command reads. See [Automatic File Tracking](./caching#automatic-file-tracking) for how this works.
+Vite Task automatically detects which files are used by a command (see [Automatic File Tracking](/guide/cache#automatic-file-tracking)). The `inputs` option can be used to explicitly include or exclude certain files.
 
 **Exclude files** from automatic tracking:
 
@@ -181,12 +161,13 @@ Files to track for cache invalidation. By default, the task runner automatically
 tasks: {
   build: {
     command: 'vp build',
+    // Use `{ auto: true }` to use automatic fingerprinting (default).
     inputs: [{ auto: true }, '!**/*.tsbuildinfo', '!dist/**'],
   },
 }
 ```
 
-**Specify explicit files** only (disables automatic tracking):
+**Specify explicit files** only without automatic tracking:
 
 ```ts
 tasks: {
@@ -197,7 +178,7 @@ tasks: {
 }
 ```
 
-**Disable file tracking** entirely (cache only on command/env changes):
+**Disable file tracking** entirely and cache only on command/env changes:
 
 ```ts
 tasks: {
@@ -212,7 +193,7 @@ tasks: {
 Glob patterns are resolved relative to the package directory, not the task's `cwd`.
 :::
 
-### `cwd` {#cwd}
+### `cwd`
 
 - **Type:** `string`
 - **Default:** package root
diff --git a/docs/config/shared-options.md b/docs/config/shared-options.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/config/staged.md b/docs/config/staged.md
new file mode 100644
index 0000000000..c6f3199b58
--- /dev/null
+++ b/docs/config/staged.md
@@ -0,0 +1,15 @@
+# Staged Config
+
+`vp staged` and `vp config` read staged-file rules from the `staged` block in `vite.config.ts`. See the [Commit hooks guide](/guide/commit-hooks).
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    '*.{js,ts,tsx,vue,svelte}': 'vp check --fix',
+  },
+});
+```
diff --git a/docs/config/test.md b/docs/config/test.md
new file mode 100644
index 0000000000..eedcbb6a2c
--- /dev/null
+++ b/docs/config/test.md
@@ -0,0 +1,18 @@
+# Test Config
+
+`vp test` reads Vitest settings from the `test` block in `vite.config.ts`. See [Vitest's configuration](https://vitest.dev/config/) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  test: {
+    include: ['src/**/*.test.ts'],
+    coverage: {
+      reporter: ['text', 'html'],
+    },
+  },
+});
+```
diff --git a/docs/guide/build.md b/docs/guide/build.md
new file mode 100644
index 0000000000..93f15d9947
--- /dev/null
+++ b/docs/guide/build.md
@@ -0,0 +1,40 @@
+# Build
+
+`vp build` builds Vite applications for production.
+
+## Overview
+
+`vp build` runs the standard Vite production build through Vite+. Since it is directly based on Vite, the build pipeline and configuration model are the same as Vite. For more information about how Vite production builds work, see the [Vite guide](https://vite.dev/guide/build). Note that Vite+ uses Vite 8 and [Rolldown](https://rolldown.rs/) for builds.
+
+::: info
+`vp build` always runs the built-in Vite production build. If your project also has a `build` script in `package.json`, run `vp run build` when you want to run that script instead.
+:::
+
+## Usage
+
+```bash
+vp build
+vp build --watch
+vp build --sourcemap
+```
+
+## Configuration
+
+Use standard Vite configuration in `vite.config.ts`. For the full configuration reference, see the [Vite config docs](https://vite.dev/config/).
+
+Use it for:
+
+- [plugins](https://vite.dev/guide/using-plugins)
+- [aliases](https://vite.dev/config/shared-options#resolve-alias)
+- [`build`](https://vite.dev/config/build-options)
+- [`preview`](https://vite.dev/config/preview-options)
+- [environment modes](https://vite.dev/guide/env-and-mode)
+
+## Preview
+
+Use `vp preview` to serve the production build locally after `vp build`.
+
+```bash
+vp build
+vp preview
+```
diff --git a/docs/guide/cache.md b/docs/guide/cache.md
new file mode 100644
index 0000000000..8bde6745af
--- /dev/null
+++ b/docs/guide/cache.md
@@ -0,0 +1,119 @@
+# Task Caching
+
+Vite Task can automatically track dependencies and cache tasks run through `vp run`.
+
+## Overview
+
+When a task runs successfully (exit code 0), its terminal output (stdout/stderr) is saved. On the next run, Vite Task checks if anything changed:
+
+1. **Arguments:** did the [additional arguments](/guide/run#additional-arguments) passed to the task change?
+2. **Environment variables:** did any [fingerprinted env vars](/config/run#envs) change?
+3. **Input files:** did any file that the command reads change?
+
+If everything matches, the cached output is replayed instantly, and the command does not run.
+
+::: info
+Currently, only terminal output is cached and replayed. Output files such as `dist/` are not cached. If you delete them, use `--no-cache` to force a re-run. Output file caching is planned for a future release.
+:::
+
+When a cache miss occurs, Vite Task tells you exactly why:
+
+```
+$ vp lint ✗ cache miss: 'src/utils.ts' modified, executing
+$ vp build ✗ cache miss: envs changed, executing
+$ vp test ✗ cache miss: args changed, executing
+```
+
+## When Is Caching Enabled?
+
+A command run by `vp run` is either a **task** (has an entry in `vite.config.ts`) or a **script** (only exists in `package.json` with no corresponding task entry). By default, **tasks are cached and scripts are not.**
+
+There are three types of controls for task caching, in order:
+
+### 1. Per-task `cache: false`
+
+A task can set [`cache: false`](/config/run#cache) to opt out. This cannot be overridden by any other cache control flag.
+
+### 2. CLI flags
+
+`--no-cache` disables caching for everything. `--cache` enables caching for both tasks and scripts, which is equivalent to setting [`run.cache: true`](/config/run#run-cache) for that invocation.
+
+### 3. Workspace config
+
+The [`run.cache`](/config/run#run-cache) option in your root `vite.config.ts` controls the default for each category:
+
+| Setting         | Default | Effect                                |
+| --------------- | ------- | ------------------------------------- |
+| `cache.tasks`   | `true`  | Cache commands that have a task entry |
+| `cache.scripts` | `false` | Cache plain `package.json` scripts    |
+
+## Automatic File Tracking
+
+Vite Task tracks which files each command reads during execution. When a task runs, it records which files the process opens, such as your `.ts` source files, `vite.config.ts`, and `package.json`, and records their content hashes. On the next run, it re-checks those hashes to determine if anything changed.
+
+This means caching works out of the box for most commands without any configuration. Vite Task also records:
+
+- **Missing files:** if a command probes for a file that doesn't exist, such as `utils.ts` during module resolution, creating that file later correctly invalidates the cache.
+- **Directory listings:** if a command scans a directory, such as a test runner looking for `*.test.ts`, adding or removing files in that directory invalidates the cache.
+
+### Avoiding Overly Broad Input Tracking
+
+Automatic tracking can sometimes include more files than necessary, causing unnecessary cache misses:
+
+- **Tool cache files:** some tools maintain their own cache, such as TypeScript's `.tsbuildinfo` or Cargo's `target/`. These files may change between runs even when your source code has not, causing unnecessary cache invalidation.
+- **Directory listings:** when a command scans a directory, such as when globbing for `**/*.js`, Vite Task sees the directory read but not the glob pattern. Any file added or removed in that directory, even unrelated ones, invalidates the cache.
+
+Use the [`inputs`](/config/run#inputs) option to exclude files or to replace automatic tracking with explicit file patterns:
+
+```ts
+tasks: {
+  build: {
+    command: 'tsc',
+    inputs: [{ auto: true }, '!**/*.tsbuildinfo'],
+  },
+}
+```
+
+## Environment Variables
+
+By default, tasks run in a clean environment. Only a small set of common variables, such as `PATH`, `HOME`, and `CI`, are passed through. Other environment variables are neither visible to the task nor included in the cache fingerprint.
+
+To add an environment variable to the cache key, add it to [`envs`](/config/run#envs). Changing its value then invalidates the cache:
+
+```ts
+tasks: {
+  build: {
+    command: 'webpack --mode production',
+    envs: ['NODE_ENV'],
+  },
+}
+```
+
+To pass a variable to the task **without** affecting cache behavior, use [`passThroughEnvs`](/config/run#pass-through-envs). This is useful for variables like `CI` or `GITHUB_ACTIONS` that should be available in the task, but do not generally affect caching behavior.
+
+See [Run Config](/config/run#envs) for details on wildcard patterns and the full list of automatically passed-through variables.
+
+## Cache Sharing
+
+Vite Task's cache is content-based. If two tasks run the same command with the same inputs, they share the cache entry. This happens naturally when multiple tasks include a common step, either as standalone tasks or as parts of [compound commands](/guide/run#compound-commands):
+
+```json [package.json]
+{
+  "scripts": {
+    "check": "vp lint && vp build",
+    "release": "vp lint && deploy-script"
+  }
+}
+```
+
+With caching enabled, for example through `--cache` or [`run.cache.scripts: true`](/config/run#run-cache), running `check` first means the `vp lint` step in `release` is an instant cache hit, since both run the same command against the same files.
+
+## Cache Commands
+
+Use `vp cache clean` when you need to clear cached task results:
+
+```bash
+vp cache clean
+```
+
+The task cache is stored in `node_modules/.vite/task-cache` at the project root. `vp cache clean` deletes that cache directory.
diff --git a/docs/guide/check.md b/docs/guide/check.md
new file mode 100644
index 0000000000..1f5b984e1c
--- /dev/null
+++ b/docs/guide/check.md
@@ -0,0 +1,41 @@
+# Check
+
+`vp check` runs format, lint, and type checks together.
+
+## Overview
+
+`vp check` is the default command for fast static checks in Vite+. It brings together formatting through [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), linting through [Oxlint](https://oxc.rs/docs/guide/usage/linter.html), and TypeScript type checks through [tsgolint](https://github.com/oxc-project/tsgolint). By merging all of these tasks into a single command, `vp check` is faster than running formatting, linting, and type checking as separate tools in separate commands.
+
+When `typeCheck` is enabled in the `lint.options` block in `vite.config.ts`, `vp check` also runs TypeScript type checks through the Oxlint type-aware path powered by the TypeScript Go toolchain and [tsgolint](https://github.com/oxc-project/tsgolint). `vp create` and `vp migrate` enable both `typeAware` and `typeCheck` by default.
+
+We recommend turning `typeCheck` on so `vp check` becomes the single command for static checks during development.
+
+## Usage
+
+```bash
+vp check
+vp check --fix # Format and run autofixers.
+```
+
+## Configuration
+
+`vp check` uses the same configuration you already define for linting and formatting:
+
+- [`lint`](/guide/lint#configuration) block in `vite.config.ts`
+- [`fmt`](/guide/fmt#configuration) block in `vite.config.ts`
+- TypeScript project structure and tsconfig files for type-aware linting
+
+Recommended base `lint` config:
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  lint: {
+    options: {
+      typeAware: true,
+      typeCheck: true,
+    },
+  },
+});
+```
diff --git a/docs/guide/ci.md b/docs/guide/ci.md
new file mode 100644
index 0000000000..3e64009e40
--- /dev/null
+++ b/docs/guide/ci.md
@@ -0,0 +1,64 @@
+# Continuous Integration
+
+You can use `voidzero-dev/setup-vp` to use Vite+ in CI environments.
+
+## Overview
+
+For GitHub Actions, the recommended setup is [`voidzero-dev/setup-vp`](https://github.com/voidzero-dev/setup-vp). It installs Vite+, sets up the required Node.js version and package manager, and can cache package installs automatically.
+
+That means you usually do not need separate `setup-node`, package-manager setup, and manual dependency-cache steps in your workflow.
+
+## GitHub Actions
+
+```yaml
+- uses: voidzero-dev/setup-vp@v1
+  with:
+    node-version: '22'
+    cache: true
+- run: vp install
+- run: vp check
+- run: vp test
+- run: vp build
+```
+
+With `cache: true`, `setup-vp` handles dependency caching for you automatically.
+
+## Simplifying Existing Workflows
+
+If you are migrating an existing GitHub Actions workflow, you can often replace large blocks of Node, package-manager, and cache setup with a single `setup-vp` step.
+
+#### Before:
+
+```yaml
+- uses: actions/setup-node@v4
+  with:
+    node-version: '24'
+
+- uses: pnpm/action-setup@v4
+  with:
+    version: 10
+
+- name: Get pnpm store path
+  run: pnpm store path
+
+- uses: actions/cache@v4
+  with:
+    path: ~/.pnpm-store
+    key: ${{ runner.os }}-pnpm-${{ hashFiles('pnpm-lock.yaml') }}
+
+- run: pnpm install && pnpm dev:setup
+- run: pnpm test
+```
+
+#### After:
+
+```yaml
+- uses: voidzero-dev/setup-vp@v1
+  with:
+    node-version: '24'
+    cache: true
+
+- run: vp install && vp run dev:setup
+- run: vp check
+- run: vp test
+```
diff --git a/docs/guide/commit-hooks.md b/docs/guide/commit-hooks.md
new file mode 100644
index 0000000000..d6afa313d2
--- /dev/null
+++ b/docs/guide/commit-hooks.md
@@ -0,0 +1,51 @@
+# Commit Hooks
+
+Use `vp config` to install commit hooks, and `vp staged` to run checks on staged files.
+
+## Overview
+
+Vite+ supports commit hooks and staged-file checks without additional tooling.
+
+Use:
+
+- `vp config` to set up project hooks and related integrations
+- `vp staged` to run checks against the files currently staged in Git
+
+If you use [`vp create`](/guide/create) or [`vp migrate`](/guide/migrate), Vite+ prompts you to set this up for your project automatically.
+
+## Commands
+
+### `vp config`
+
+`vp config` configures Vite+ for the current project. It installs Git hooks, sets up the hook directory, and can also handle related project integration such as agent setup. By default, hooks are written to `.vite-hooks`:
+
+```bash
+vp config
+vp config --hooks-dir .vite-hooks
+```
+
+### `vp staged`
+
+`vp staged` runs staged-file checks using the `staged` config from `vite.config.ts`. If you set up Vite+ to handle your commit hooks, it will automatically run when you commit your local changes.
+
+```bash
+vp staged
+vp staged --verbose
+vp staged --fail-on-changes
+```
+
+## Configuration
+
+Define staged-file checks in the `staged` block in `vite.config.ts`:
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    '*.{js,ts,tsx,vue,svelte}': 'vp check --fix',
+  },
+});
+```
+
+This is the default Vite+ approach and should replace separate `lint-staged` configuration in most projects. Because `vp staged` reads from `vite.config.ts`, your staged-file checks stay in the same place as your lint, format, test, build, and task-runner config.
diff --git a/docs/guide/create.md b/docs/guide/create.md
new file mode 100644
index 0000000000..0985cd56a3
--- /dev/null
+++ b/docs/guide/create.md
@@ -0,0 +1,87 @@
+# Creating a Project
+
+`vp create` interactively scaffolds new Vite+ projects, monorepos, and apps inside existing workspaces.
+
+## Overview
+
+The `create` command is the fastest way to start with Vite+. It can be used in a few different ways:
+
+- Start a new Vite+ monorepo
+- Create a new standalone application or library
+- Add a new app or library inside an existing project
+
+This command can be used with built-in templates, community templates, or remote GitHub templates.
+
+## Usage
+
+```bash
+vp create
+vp create <template>
+vp create <template> -- <template-options>
+```
+
+## Built-in Templates
+
+Vite+ ships with these built-in templates:
+
+- `vite:monorepo` creates a new monorepo
+- `vite:application` creates a new application
+- `vite:library` creates a new library
+- `vite:generator` creates a new generator
+
+## Template Sources
+
+`vp create` is not limited to the built-in templates.
+
+- Use shorthand templates like `vite`, `@tanstack/start`, `next-app`, `nuxt`, `react-router`, and `vue`
+- Use full package names like `create-vite` or `create-next-app`
+- Use local templates such as `./tools/create-ui-component` or `@acme/generator-*`
+- Use remote templates such as `github:user/repo` or `https://github.com/user/template-repo`
+
+Run `vp create --list` to see the built-in templates and the common shorthand templates Vite+ recognizes.
+
+## Options
+
+- `--directory <dir>` writes the generated project into a specific target directory
+- `--agent <name>` creates agent instructions files during scaffolding
+- `--editor <name>` writes editor config files
+- `--hooks` enables pre-commit hook setup
+- `--no-hooks` skips hook setup
+- `--no-interactive` runs without prompts
+- `--verbose` shows detailed scaffolding output
+- `--list` prints the available built-in and popular templates
+
+## Template Options
+
+Arguments after `--` are passed directly to the selected template.
+
+This matters when the template itself accepts flags. For example, you can forward Vite template selection like this:
+
+```bash
+vp create vite -- --template react-ts
+```
+
+## Examples
+
+```bash
+# Interactive mode
+vp create
+
+# Create a Vite+ monorepo, application, library, or generator
+vp create vite:monorepo
+vp create vite:application
+vp create vite:library
+vp create vite:generator
+
+# Use shorthand community templates
+vp create vite
+vp create @tanstack/start
+
+# Use full package names
+vp create create-vite
+vp create create-next-app
+
+# Use remote templates
+vp create github:user/repo
+vp create https://github.com/user/template-repo
+```
diff --git a/docs/guide/dev.md b/docs/guide/dev.md
new file mode 100644
index 0000000000..947764f992
--- /dev/null
+++ b/docs/guide/dev.md
@@ -0,0 +1,24 @@
+# Dev
+
+`vp dev` starts the Vite development server.
+
+## Overview
+
+`vp dev` runs the standard Vite development server through Vite+, so you keep the normal Vite dev experience while using the same CLI entry point as the rest of the toolchain. For more information about using and configuring the dev server, see the [Vite guide](https://vite.dev/guide/).
+
+## Usage
+
+```bash
+vp dev
+```
+
+## Configuration
+
+Use standard Vite config in `vite.config.ts`. For the full configuration reference, see the [Vite config docs](https://vite.dev/config/).
+
+Use it for:
+
+- [plugins](https://vite.dev/guide/using-plugins)
+- [aliases](https://vite.dev/config/shared-options#resolve-alias)
+- [`server`](https://vite.dev/config/server-options)
+- [environment modes](https://vite.dev/guide/env-and-mode)
diff --git a/docs/guide/env.md b/docs/guide/env.md
new file mode 100644
index 0000000000..e58f93a40e
--- /dev/null
+++ b/docs/guide/env.md
@@ -0,0 +1,84 @@
+# Environment
+
+`vp env` manages Node.js versions globally and per project.
+
+## Overview
+
+Managed mode is on by default, so `node`, `npm`, and related shims resolve through Vite+ and pick the right Node.js version for the current project.
+
+By default, Vite+ stores its managed runtime and related files in `~/.vite-plus`. If needed, you can override that location with `VITE_PLUS_HOME`.
+
+If you want to keep that behavior, run:
+
+```bash
+vp env on
+```
+
+This enables managed mode, where the shims always use the Vite+-managed Node.js installation.
+
+If you do not want Vite+ to manage Node.js first, run:
+
+```bash
+vp env off
+```
+
+This switches to system-first mode, where the shims prefer your system Node.js and only fall back to the Vite+-managed runtime when needed.
+
+## Commands
+
+### Setup
+
+- `vp env setup` creates or updates shims in `VITE_PLUS_HOME/bin`
+- `vp env on` enables managed mode so shims always use Vite+-managed Node.js
+- `vp env off` enables system-first mode so shims prefer system Node.js first
+- `vp env print` prints the shell snippet for the current session
+
+### Manage
+
+- `vp env default` sets or shows the global default Node.js version
+- `vp env pin` pins a Node.js version in the current directory
+- `vp env unpin` removes `.node-version` from the current directory
+- `vp env use` sets a Node.js version for the current shell session
+- `vp env install` installs a Node.js version
+- `vp env uninstall` removes an installed Node.js version
+- `vp env exec` runs a command with a specific Node.js version
+
+### Inspect
+
+- `vp env current` shows the current resolved environment
+- `vp env doctor` runs environment diagnostics
+- `vp env which` shows which tool path will be used
+- `vp env list` shows locally installed Node.js versions
+- `vp env list-remote` shows available Node.js versions from the registry
+
+## Project Setup
+
+- Pin a project version with `.node-version`
+- Use `vp install`, `vp dev`, and `vp build` normally
+- Let Vite+ pick the right runtime for the project
+
+## Examples
+
+```bash
+# Setup
+vp env setup                  # Create shims for node, npm, npx
+vp env on                     # Use Vite+ managed Node.js
+vp env print                  # Print shell snippet for this session
+
+# Manage
+vp env pin lts                # Pin the project to the latest LTS release
+vp env install                # Install the version from .node-version or package.json
+vp env default lts            # Set the global default version
+vp env use 20                 # Use Node.js 20 for the current shell session
+vp env use --unset            # Remove the session override
+
+# Inspect
+vp env current                # Show current resolved environment
+vp env current --json         # JSON output for automation
+vp env which node             # Show which node binary will be used
+vp env list-remote --lts      # List only LTS versions
+
+# Execute
+vp env exec --node lts npm i  # Execute npm with latest LTS
+vp env exec node -v           # Use shim mode with automatic version resolution
+```
diff --git a/docs/guide/fmt.md b/docs/guide/fmt.md
new file mode 100644
index 0000000000..eb6418f681
--- /dev/null
+++ b/docs/guide/fmt.md
@@ -0,0 +1,33 @@
+# Format
+
+`vp fmt` formats code with Oxfmt.
+
+## Overview
+
+`vp fmt` is built on [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), the Oxc formatter. Oxfmt has full Prettier compatibility and is designed as a fast drop-in replacement for Prettier.
+
+Use `vp fmt` to format your project, and `vp check` to format, lint and type-check all at once.
+
+## Usage
+
+```bash
+vp fmt
+vp fmt --check
+vp fmt . --write
+```
+
+## Configuration
+
+Put formatting configuration directly in the `fmt` block in `vite.config.ts` so all your configuration stays in one place. We do not recommend using `.oxfmtrc.json` with Vite+.
+
+For the upstream formatter behavior and configuration reference, see the [Oxfmt docs](https://oxc.rs/docs/guide/usage/formatter.html).
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  fmt: {
+    singleQuote: true,
+  },
+});
+```
diff --git a/docs/guide/ide-integration.md b/docs/guide/ide-integration.md
new file mode 100644
index 0000000000..d6b0befcfe
--- /dev/null
+++ b/docs/guide/ide-integration.md
@@ -0,0 +1,35 @@
+# IDE Integration
+
+Vite+ supports VS Code through the [Vite Plus Extension Pack](https://marketplace.visualstudio.com/items?itemName=VoidZero.vite-plus-extension-pack) and the VS Code settings that `vp create` and `vp migrate` can automatically write into your project.
+
+## VS Code
+
+For the best VS Code experience with Vite+, install the [Vite Plus Extension Pack](https://marketplace.visualstudio.com/items?itemName=VoidZero.vite-plus-extension-pack). It currently includes:
+
+- `Oxc` for formatting and linting via `vp check`
+- `Vitest` for test runs via `vp test`
+
+When you create or migrate a project, Vite+ prompts whether you want editor config written for VS Code. You can also manually set up the VS Code config:
+
+`.vscode/extensions.json`
+
+```json
+{
+  "recommendations": ["VoidZero.vite-plus-extension-pack"]
+}
+```
+
+`.vscode/settings.json`
+
+```json
+{
+  "editor.defaultFormatter": "oxc.oxc-vscode",
+  "editor.formatOnSave": true,
+  "editor.formatOnSaveMode": "file",
+  "editor.codeActionsOnSave": {
+    "source.fixAll.oxc": "explicit"
+  }
+}
+```
+
+This gives the project a shared default formatter and enables Oxc-powered fix actions on save. Vite+ uses `formatOnSaveMode: "file"` because Oxfmt does not support partial formatting.
diff --git a/docs/guide/implode.md b/docs/guide/implode.md
new file mode 100644
index 0000000000..02a019f5f6
--- /dev/null
+++ b/docs/guide/implode.md
@@ -0,0 +1,23 @@
+# Removing Vite+
+
+Use `vp implode` to remove `vp` and all related Vite+ data from your machine.
+
+## Overview
+
+`vp implode` is the cleanup command for removing a Vite+ installation and its managed data. Use it if you no longer want Vite+ to manage your runtime, package manager, and related local tooling state.
+
+::: info
+If you decide Vite+ is not for you, please [share your feedback with us](https://discord.gg/cAnsqHh5PX).
+:::
+
+## Usage
+
+```bash
+vp implode
+```
+
+Skip the confirmation prompt with:
+
+```bash
+vp implode --yes
+```
diff --git a/docs/guide/index.md b/docs/guide/index.md
new file mode 100644
index 0000000000..d2568d0847
--- /dev/null
+++ b/docs/guide/index.md
@@ -0,0 +1,93 @@
+# Getting Started
+
+Vite+ is the unified toolchain and entry point for web development. It manages your runtime, package manager, and frontend toolchain in one place by combining [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).
+
+Vite+ ships in two parts: `vp`, the global command-line tool, and `vite-plus`, the local package installed in each project. If you already have a Vite project, use [`vp migrate`](/guide/migrate) to migrate it to Vite+, or paste our [migration prompt](/guide/migrate#migration-prompt) into your coding agent.
+
+## Install `vp`
+
+### macOS / Linux
+
+```bash
+curl -fsSL https://vite.plus | bash
+```
+
+### Windows
+
+```powershell
+irm https://vite.plus/ps1 | iex
+```
+
+After installation, open a new shell and run:
+
+```bash
+vp help
+```
+
+::: info
+Vite+ will manage your global Node.js runtime and package manager. If you'd like to opt out of this behavior, run `vp env off`. If you realize Vite+ is not for you, type `vp implode`, but please [share your feedback with us](https://discord.gg/cAnsqHh5PX).
+:::
+
+## Quick Start
+
+Create a project, install dependencies, and use the default commands:
+
+```bash
+vp create # Create a new project
+vp install # Install dependencies
+vp dev # Start the dev server
+vp check # Format, lint, type-check
+vp test # Run JavaScript tests
+vp build # Build for production
+```
+
+You can also just run `vp` on its own and use the interactive command line.
+
+## Core Commands
+
+Vite+ can handle the entire local frontend development cycle from starting a project, developing it, checking & testing, and building it for production.
+
+### Start
+
+- [`vp create`](/guide/create) creates new apps, packages, and monorepos.
+- [`vp migrate`](/guide/migrate) moves existing projects onto Vite+.
+- [`vp config`](/guide/commit-hooks) configures commit hooks and agent integration.
+- [`vp staged`](/guide/commit-hooks) runs checks on staged files.
+- [`vp install`](/guide/install) installs dependencies with the right package manager.
+- [`vp env`](/guide/env) manages Node.js versions.
+
+### Develop
+
+- [`vp dev`](/guide/dev) starts the dev server powered by Vite.
+- [`vp check`](/guide/check) runs format, lint, and type checks together.
+- [`vp lint`](/guide/lint), [`vp fmt`](/guide/fmt), and [`vp test`](/guide/test) let you run those tools directly.
+
+### Execute
+
+- [`vp run`](/guide/run) runs tasks across workspaces with caching.
+- [`vp cache`](/guide/cache) clears task cache entries.
+- [`vpx`](/guide/vpx) runs binaries globally.
+- [`vp exec`](/guide/vpx) runs local project binaries.
+- [`vp dlx`](/guide/vpx) runs package binaries without adding them as dependencies.
+
+### Build
+
+- [`vp build`](/guide/build) builds apps.
+- [`vp pack`](/guide/pack) builds libraries or standalone artifacts.
+- [`vp preview`](/guide/build) previews the production build locally.
+
+### Manage Dependencies
+
+- [`vp add`](/guide/install), [`vp remove`](/guide/install), [`vp update`](/guide/install), [`vp dedupe`](/guide/install), [`vp outdated`](/guide/install), [`vp why`](/guide/install), and [`vp info`](/guide/install) wrap package-manager workflows.
+- [`vp pm <command>`](/guide/install) calls other package manager commands directly.
+
+### Maintain
+
+- [`vp upgrade`](/guide/upgrade) updates the `vp` installation itself.
+- [`vp implode`](/guide/implode) removes `vp` and related Vite+ data from your machine.
+
+::: info
+Vite+ ships with many predefined commands such as `vp build`, `vp test`, and `vp dev`. These commands are built in and cannot be changed. If you want to run a command from your `package.json` scripts, use `vp run <command>`.
+
+[Learn more about `vp run`.](/guide/run)
+:::
diff --git a/docs/guide/install.md b/docs/guide/install.md
new file mode 100644
index 0000000000..20423d2358
--- /dev/null
+++ b/docs/guide/install.md
@@ -0,0 +1,130 @@
+# Installing Dependencies
+
+`vp install` installs dependencies using the current workspace's package manager.
+
+## Overview
+
+Use Vite+ to manage dependencies across pnpm, npm, and Yarn. Instead of switching between `pnpm install`, `npm install`, and `yarn install`, you can keep using `vp install`, `vp add`, `vp remove`, and the rest of the Vite+ package-management commands.
+
+Vite+ detects the package manager from the workspace root in this order:
+
+1. `packageManager` in `package.json`
+2. `pnpm-workspace.yaml`
+3. `pnpm-lock.yaml`
+4. `yarn.lock` or `.yarnrc.yml`
+5. `package-lock.json`
+6. `.pnpmfile.cjs` or `pnpmfile.cjs`
+7. `yarn.config.cjs`
+
+If none of those files are present, `vp` falls back to `pnpm` by default. Vite+ automatically downloads the matching package manager and uses it for the command you ran.
+
+## Usage
+
+```bash
+vp install
+```
+
+Common install flows:
+
+```bash
+vp install
+vp install --frozen-lockfile
+vp install --lockfile-only
+vp install --filter web
+vp install -w
+```
+
+`vp install` maps to the correct underlying install behavior for the detected package manager, including the right lockfile flags for pnpm, npm, and Yarn.
+
+## Global Packages
+
+Use the `-g` flag for installing, updating or removing globally installed packages:
+
+- `vp install -g <pkg>` installs a package globally
+- `vp uninstall -g <pkg>` removes a global package
+- `vp update -g [pkg]` updates one global package or all of them
+- `vp list -g [pkg]` lists global packages
+
+## Managing Dependencies
+
+Vite+ provides all the familiar package management commands:
+
+- `vp install` installs the current dependency graph for the project
+- `vp add <pkg>` adds packages to `dependencies`, use `-D` for `devDependencies`
+- `vp remove <pkg>` removes packages
+- `vp update` updates dependencies
+- `vp dedupe` reduces duplicate dependency entries where the package manager supports it
+- `vp outdated` shows available updates
+- `vp list` shows installed packages
+- `vp why <pkg>` explains why a package is present
+- `vp info <pkg>` shows registry metadata for a package
+- `vp link` and `vp unlink` manage local package links
+- `vp dlx <pkg>` runs a package binary without adding it to the project
+- `vp pm <command>` forwards a raw package-manager-specific command when you need behavior outside the normalized `vp` command set
+
+### Command Guide
+
+#### Install
+
+Use `vp install` when you want to install exactly what the current `package.json` and lockfile describe.
+
+- `vp install` is the standard install command
+- `vp install --frozen-lockfile` fails if the lockfile would need changes
+- `vp install --no-frozen-lockfile` allows lockfile updates explicitly
+- `vp install --lockfile-only` updates the lockfile without performing a full install
+- `vp install --prefer-offline` and `vp install --offline` prefer or require cached packages
+- `vp install --ignore-scripts` skips lifecycle scripts
+- `vp install --filter <pattern>` scopes install work in monorepos
+- `vp install -w` installs in the workspace root
+
+#### Global Install
+
+Use these commands when you want package-manager-managed tools available outside a single project.
+
+- `vp install -g typescript`
+- `vp uninstall -g typescript`
+- `vp update -g`
+- `vp list -g`
+
+#### Add and Remove
+
+Use `vp add` and `vp remove` for day-to-day dependency edits instead of editing `package.json` by hand.
+
+- `vp add react`
+- `vp add -D typescript vitest`
+- `vp add -O fsevents`
+- `vp add --save-peer react`
+- `vp remove react`
+- `vp remove --filter web react`
+
+#### Update, Dedupe, and Outdated
+
+Use these commands to maintain the dependency graph over time.
+
+- `vp update` refreshes packages to newer versions
+- `vp outdated` shows which packages have newer versions available
+- `vp dedupe` asks the package manager to collapse duplicates where possible
+
+#### Inspect
+
+Use these when you need to understand the current state of dependencies.
+
+- `vp list` shows installed packages
+- `vp why react` explains why `react` is installed
+- `vp info react` shows registry metadata such as versions and dist-tags
+
+#### Advanced
+
+Use these when you need lower-level package-manager behavior.
+
+- `vp link` and `vp unlink` manage local development links
+- `vp dlx create-vite` runs a package binary without saving it as a dependency
+- `vp pm <command>` forwards directly to the resolved package manager
+
+Examples:
+
+```bash
+vp pm config get registry
+vp pm cache clean --force
+vp pm exec tsc --version
+```
diff --git a/docs/guide/lint.md b/docs/guide/lint.md
new file mode 100644
index 0000000000..b551e1712f
--- /dev/null
+++ b/docs/guide/lint.md
@@ -0,0 +1,50 @@
+# Lint
+
+`vp lint` lints code with Oxlint.
+
+## Overview
+
+`vp lint` is built on [Oxlint](https://oxc.rs/docs/guide/usage/linter.html), the Oxc linter. Oxlint is designed as a fast replacement for ESLint for most frontend projects and ships with built-in support for core ESLint rules and many popular community rules.
+
+Use `vp lint` to lint your project, and `vp check` to format, lint and type-check all at once.docs/guide/fmt.md
+
+## Usage
+
+```bash
+vp lint
+vp lint --fix
+vp lint --type-aware
+```
+
+## Configuration
+
+Put lint configuration directly in the `lint` block in `vite.config.ts` so all your configuration stays in one place. We do not recommend using `oxlint.config.ts` or `.oxlintrc.json` with Vite+.
+
+For the upstream rule set, options, and compatibility details, see the [Oxlint docs](https://oxc.rs/docs/guide/usage/linter.html).
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  lint: {
+    ignorePatterns: ['dist/**'],
+    options: {
+      typeAware: true,
+      typeCheck: true,
+    },
+  },
+});
+```
+
+## Type-Aware Linting
+
+We recommend enabling both `typeAware` and `typeCheck` in the `lint` block:
+
+- `typeAware: true` enables rules that require TypeScript type information
+- `typeCheck: true` enables full type checking during linting
+
+This path is powered by [tsgolint](https://github.com/oxc-project/tsgolint) on top of the TypeScript Go toolchain. It gives Oxlint access to type information and allows type checking directly via `vp lint` and `vp check`.
+
+## JS Plugins
+
+If you are migrating from ESLint and still depend on a few critical JavaScript-based ESLint plugins, Oxlint has [JS plugin support](https://oxc.rs/docs/guide/usage/linter/js-plugins) that can help you keep those plugins running while you complete the migration.
diff --git a/docs/guide/migrate.md b/docs/guide/migrate.md
new file mode 100644
index 0000000000..6f1e8c8665
--- /dev/null
+++ b/docs/guide/migrate.md
@@ -0,0 +1,109 @@
+# Migrate to Vite+
+
+`vp migrate` helps move existing projects onto Vite+.
+
+## Overview
+
+This command is the starting point for consolidating separate Vite, Vitest, Oxlint, Oxfmt, ESLint, and Prettier setups into Vite+.
+
+Use it when you want to take an existing project and move it onto the Vite+ defaults instead of wiring each tool by hand.
+
+## Usage
+
+```bash
+vp migrate
+vp migrate <path>
+vp migrate --no-interactive
+```
+
+## Target Path
+
+The positional `PATH` argument is optional.
+
+- If omitted, `vp migrate` migrates the current directory
+- If provided, it migrates that target directory instead
+
+```bash
+vp migrate
+vp migrate my-app
+```
+
+## Options
+
+- `--agent <name>` writes agent instructions into the project
+- `--no-agent` skips agent instruction setup
+- `--editor <name>` writes editor config files into the project
+- `--no-editor` skips editor config setup
+- `--hooks` sets up pre-commit hooks
+- `--no-hooks` skips hook setup
+- `--no-interactive` runs the migration without prompts
+
+## Migration Flow
+
+The `migrate` command is designed to move existing projects onto Vite+ quickly. Here is what the command does:
+
+- Updates project dependencies
+- Rewrites imports where needed
+- Merges tool-specific config into `vite.config.ts`
+- Updates scripts to the Vite+ command surface
+- Can set up commit hooks
+- Can write agent and editor configuration files
+
+Most projects will require further manual adjustments after running `vp migrate`.
+
+## Recommended Workflow
+
+Before running the migration:
+
+- Upgrade to Vite 8+ and Vitest 4.1+ first
+- Make sure you understand any existing lint, format, or test setup that should be preserved
+
+After running the migration:
+
+- Run `vp install`
+- Run `vp check`
+- Run `vp test`
+- Run `vp build`
+
+## Migration Prompt
+
+If you want to hand this work to a coding agent (or the reader is a coding agent!), use this migration prompt:
+
+```md
+Migrate this project to Vite+. Vite+ replaces the current split tooling around runtime management, package management, dev/build/test commands, linting, formatting, and packaging. Run `vp help` to understand Vite+ capabilities and `vp help migrate` before making changes. Use `vp migrate --no-interactive` in the workspace root. Make sure the project is using Vite 8+ and Vitest 4.1+ before migrating.
+
+After the migration:
+
+- Confirm `vite` imports were rewritten to `vite-plus` where needed
+- Confirm `vitest` imports were rewritten to `vite-plus/test` where needed
+- Remove old `vite` and `vitest` dependencies only after those rewrites are confirmed
+- Move remaining tool-specific config into the appropriate blocks in `vite.config.ts`
+
+Command mapping to keep in mind:
+
+- `vp run <script>` is the equivalent of `pnpm run <script>`
+- `vp test` runs the built-in test command, while `vp run test` runs the `test` script from `package.json`
+- `vp install`, `vp add`, and `vp remove` delegate through the package manager declared by `packageManager`
+- `vp dev`, `vp build`, `vp preview`, `vp lint`, `vp fmt`, `vp check`, and `vp pack` replace the corresponding standalone tools
+- Prefer `vp check` for validation loops
+
+Finally, verify the migration by running: `vp install`, `vp check`, `vp test`, and `vp build`
+
+Summarize the migration at the end and report any manual follow-up still required.
+```
+
+## Examples
+
+```bash
+# Migrate the current project
+vp migrate
+
+# Migrate a specific directory
+vp migrate my-app
+
+# Run without prompts
+vp migrate --no-interactive
+
+# Write agent and editor setup during migration
+vp migrate --agent claude --editor zed
+```
diff --git a/docs/guide/pack.md b/docs/guide/pack.md
new file mode 100644
index 0000000000..b7f31816a6
--- /dev/null
+++ b/docs/guide/pack.md
@@ -0,0 +1,61 @@
+# Pack
+
+`vp pack` builds libraries for production with [tsdown](https://tsdown.dev/guide/).
+
+## Overview
+
+`vp pack` builds libraries and standalone executables with tsdown. Use it for publishable packages and binary outputs. If you want to build a web application, use `vp build`. `vp pack` covers everything you need for building libraries out of the box, including declaration file generation, multiple output formats, source maps, and minification.
+
+For more information about how tsdown works, see the official [tsdown guide](https://tsdown.dev/guide/).
+
+## Usage
+
+```bash
+vp pack
+vp pack src/index.ts --dts
+vp pack --watch
+```
+
+## Configuration
+
+Put packaging configuration directly in the `pack` block in `vite.config.ts` so all your configuration stays in one place. We do not recommend using `tsdown.config.ts` with Vite+.
+
+See the [tsdown guide](https://tsdown.dev/guide/) and the [tsdown config file docs](https://tsdown.dev/options/config-file) to learn more about how to use and configure `vp pack`.
+
+Use it for:
+
+- [declaration files (`dts`)](https://tsdown.dev/options/dts)
+- [output formats](https://tsdown.dev/options/format)
+- [watch mode](https://tsdown.dev/options/watch)
+- [standalone executables](https://tsdown.dev/options/exe#executable)
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  pack: {
+    dts: true,
+    format: ['esm', 'cjs'],
+    sourcemap: true,
+  },
+});
+```
+
+## Standalone Executables
+
+`vp pack` can also build standalone executables through tsdown's experimental [`exe` option](https://tsdown.dev/options/exe#executable).
+
+Use this when you want to ship a CLI or other Node-based tool as a native executable that runs without requiring Node.js to be installed separately.
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  pack: {
+    entry: ['src/cli.ts'],
+    exe: true,
+  },
+});
+```
+
+See the official [tsdown executable docs](https://tsdown.dev/options/exe#executable) for details about configuring custom file names, embedded assets, and cross-platform targets.
diff --git a/docs/guide/run.md b/docs/guide/run.md
new file mode 100644
index 0000000000..5f48354325
--- /dev/null
+++ b/docs/guide/run.md
@@ -0,0 +1,292 @@
+# Run
+
+`vp run` runs `package.json` scripts and tasks defined in `vite.config.ts`. It works like `pnpm run`, with caching, dependency ordering, and workspace-aware execution built in.
+
+## Overview
+
+Use `vp run` with existing `package.json` scripts:
+
+```json [package.json]
+{
+  "scripts": {
+    "build": "node compile-legacy-app.js",
+    "test": "jest"
+  }
+}
+```
+
+`vp run build` executes the associated build script:
+
+```
+$ node compile-legacy-app.js
+
+building legacy app for production...
+
+✓ built in 69s
+```
+
+Use `vp run` without a task name to use the interactive task runner:
+
+```
+Select a task (↑/↓, Enter to run, Esc to clear):
+
+  › build: node compile-legacy-app.js
+    test: jest
+```
+
+## Caching
+
+`package.json` scripts are not cached by default. Use `--cache` to enable caching:
+
+```bash
+vp run --cache build
+```
+
+```
+$ node compile-legacy-app.js
+✓ built in 69s
+```
+
+If nothing changes, the output is replayed from the cache on the next run:
+
+```
+$ node compile-legacy-app.js ✓ cache hit, replaying
+✓ built in 69s
+
+---
+vp run: cache hit, 69s saved.
+```
+
+If an input changes, the task runs again:
+
+```
+$ node compile-legacy-app.js ✗ cache miss: 'legacy/index.js' modified, executing
+```
+
+## Task Definitions
+
+Vite Task automatically tracks which files your command uses. You can define tasks directly in `vite.config.ts` to enable caching by default or control which files and environment variables affect cache behavior.
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  run: {
+    tasks: {
+      build: {
+        dependsOn: ['lint'],
+        envs: ['NODE_ENV'],
+      },
+      deploy: {
+        command: 'deploy-script --prod',
+        cache: false,
+        dependsOn: ['build', 'test'],
+      },
+    },
+  },
+});
+```
+
+If `command` is omitted, the task uses the matching script from `package.json`. A task name can come from `vite.config.ts` or `package.json`, but not both.
+
+::: info
+Tasks defined in `vite.config.ts` are cached by default. Plain `package.json` scripts without a matching task entry are not. See [When Is Caching Enabled?](/guide/cache#when-is-caching-enabled) for the full resolution order.
+:::
+
+See [Run Config](/config/run) for the full `run` block reference.
+
+## Task Dependencies
+
+Use [`dependsOn`](#depends-on) to run tasks in the right order. Running `vp run deploy` with the config above runs `build` and `test` first. Dependencies can also target other packages in the same project with the `package#task` notation:
+
+```ts
+dependsOn: ['@my/core#build', '@my/utils#lint'];
+```
+
+## Running in a Workspace
+
+With no package-selection flags, `vp run` runs the task in the package in your current working directory:
+
+```bash
+cd packages/app
+vp run build
+```
+
+You can also target a package explicitly from anywhere:
+
+```bash
+vp run @my/app#build
+```
+
+Workspace package ordering is based on the normal monorepo dependency graph declared in each package's `package.json`. In other words, when Vite+ talks about package dependencies, it means the regular `dependencies` relationships between workspace packages, not a separate task-runner-specific graph.
+
+### Recursive (`-r`)
+
+Run the task in every workspace package, in dependency order:
+
+```bash
+vp run -r build
+```
+
+That dependency order comes from the workspace packages referenced through `package.json` dependencies.
+
+### Transitive (`-t`)
+
+Run the task in one package and all of its dependencies:
+
+```bash
+vp run -t @my/app#build
+```
+
+If `@my/app` depends on `@my/utils`, which depends on `@my/core`, this runs all three in order. Vite+ resolves that chain from the normal workspace package dependencies declared in `package.json`.
+
+### Filter (`--filter`)
+
+Select packages by name, directory, or glob pattern. The syntax matches pnpm's `--filter`:
+
+```bash
+# By name
+vp run --filter @my/app build
+
+# By glob
+vp run --filter "@my/*" build
+
+# By directory
+vp run --filter ./packages/app build
+
+# Include dependencies
+vp run --filter "@my/app..." build
+
+# Include dependents
+vp run --filter "...@my/core" build
+
+# Exclude packages
+vp run --filter "@my/*" --filter "!@my/utils" build
+```
+
+Multiple `--filter` flags are combined as a union. Exclusion filters are applied after all inclusions.
+
+### Workspace Root (`-w`)
+
+Explicitly run the task in the workspace root package:
+
+```bash
+vp run -w build
+```
+
+## Compound Commands
+
+Commands joined with `&&` are split into independent sub-tasks. Each sub-task is cached separately when [caching is enabled](/guide/cache#when-is-caching-enabled). This works for both `vite.config.ts` tasks and `package.json` scripts:
+
+```json [package.json]
+{
+  "scripts": {
+    "check": "vp lint && vp build"
+  }
+}
+```
+
+Now, run `vp run --cache check`:
+
+```
+$ vp lint
+Found 0 warnings and 0 errors.
+
+$ vp build
+✓ built in 28ms
+
+---
+vp run: 0/2 cache hit (0%).
+```
+
+Each sub-task has its own cache entry. If only `.ts` files changed but lint still passes, only `vp build` runs again the next time `vp run --cache check` is called:
+
+```
+$ vp lint ✓ cache hit, replaying
+$ vp build ✗ cache miss: 'src/index.ts' modified, executing
+✓ built in 30ms
+
+---
+vp run: 1/2 cache hit (50%), 120ms saved.
+```
+
+### Nested `vp run`
+
+When a command contains `vp run`, Vite Task inlines it as separate tasks instead of spawning a nested process. Each sub-task is cached independently and output stays flat:
+
+```json [package.json]
+{
+  "scripts": {
+    "ci": "vp run lint && vp run test && vp run build"
+  }
+}
+```
+
+Running `vp run ci` expands into three tasks:
+
+```
+┌────────┐   ┌────────┐   ┌────────┐
+│  lint  │──▶│  test  │──▶│ build  │
+└────────┘   └────────┘   └────────┘
+```
+
+Flags also work inside nested scripts. For example, `vp run -r build` inside a script expands into individual build tasks for every package.
+
+::: info
+A common monorepo pattern is a root script that runs a task recursively:
+
+```json [package.json (root)]
+{
+  "scripts": {
+    "build": "vp run -r build"
+  }
+}
+```
+
+This creates a potential recursion: root's `build` -> `vp run -r build` -> includes root's `build` -> ...
+
+Vite Task detects this and prunes the self-reference automatically, so other packages build normally.
+:::
+
+## Execution Summary
+
+Use `-v` to show a detailed execution summary:
+
+```bash
+vp run -r -v build
+```
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+    Vite+ Task Runner • Execution Summary
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Statistics:   3 tasks • 3 cache hits • 0 cache misses
+Performance:  100% cache hit rate, 468ms saved in total
+
+Task Details:
+────────────────────────────────────────────────
+  [1] @my/core#build: ~/packages/core$ vp build ✓
+      → Cache hit - output replayed - 200ms saved
+  ·······················································
+  [2] @my/utils#build: ~/packages/utils$ vp build ✓
+      → Cache hit - output replayed - 150ms saved
+  ·······················································
+  [3] @my/app#build: ~/packages/app$ vp build ✓
+      → Cache hit - output replayed - 118ms saved
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+Use `--last-details` to show the summary from the last run without running tasks again:
+
+```bash
+vp run --last-details
+```
+
+## Additional Arguments
+
+Arguments after the task name are passed through to the task command:
+
+```bash
+vp run test --reporter verbose
+```
diff --git a/docs/guide/test.md b/docs/guide/test.md
new file mode 100644
index 0000000000..8101683957
--- /dev/null
+++ b/docs/guide/test.md
@@ -0,0 +1,35 @@
+# Test
+
+`vp test` runs tests with [Vitest](https://vitest.dev).
+
+## Overview
+
+`vp test` is built on [Vitest](https://vitest.dev/), so you get a Vite-native test runner that reuses your Vite config and plugins, supports Jest-style expectations, snapshots, and coverage, and handles modern ESM, TypeScript, and JSX projects cleanly.
+
+## Usage
+
+```bash
+vp test
+vp test watch
+vp test run --coverage
+```
+
+::: info
+Unlike Vitest on its own, `vp test` does not stay in watch mode by default. Use `vp test` when you want a normal test run, and use `vp test watch` when you want to jump into watch mode.
+:::
+
+## Configuration
+
+Put test configuration directly in the `test` block in `vite.config.ts` so all your configuration stays in one place. We do not recommend using `vitest.config.ts` with Vite+.
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  test: {
+    include: ['src/**/*.test.ts'],
+  },
+});
+```
+
+For the full Vitest configuration reference, see the [Vitest config docs](https://vitest.dev/config/).
diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.md
new file mode 100644
index 0000000000..51735f49eb
--- /dev/null
+++ b/docs/guide/troubleshooting.md
@@ -0,0 +1,71 @@
+# Troubleshooting
+
+Use this page when something in Vite+ is not behaving the way you expect.
+
+::: warning
+Vite+ is still in alpha. We are making frequent changes, adding features quickly, and we want feedback to help make it great.
+:::
+
+## Supported Tool Versions
+
+Vite+ expects modern upstream tool versions.
+
+- Vite 8 or newer
+- Vitest 4.1 or newer
+
+If you are migrating an existing project and it still depends on older Vite or Vitest versions, upgrade those first before adopting Vite+.
+
+## `vp check` does not run type-aware lint rules or type checks
+
+- Confirm that `lint.options.typeAware` and `lint.options.typeCheck` are enabled in `vite.config.ts`
+- Check whether your `tsconfig.json` uses `compilerOptions.baseUrl`
+
+The Oxlint type checker path powered by `tsgolint` does not support `baseUrl`, so Vite+ skips `typeAware` and `typeCheck` when that setting is present.
+
+## `vp build` does not run my build script
+
+Unlike package managers, built-in commands cannot be overwritten. If you are trying to run a `package.json` script use `vp run build` instead.
+
+For example:
+
+- `vp build` always runs the built-in Vite build
+- `vp test` always runs the built-in Vitest command
+- `vp run build` and `vp run test` run `package.json` scripts instead
+
+::: info
+You can also run custom tasks defined in `vite.config.ts` and migrate away from `package.json` scripts entirely.
+:::
+
+## Staged Checks and Commit Hooks
+
+If `vp staged` fails or your pre-commit hook does not run:
+
+- make sure `vite.config.ts` contains a `staged` block
+- run `vp config` to install hooks
+- check whether hook installation was skipped intentionally through `VITE_GIT_HOOKS=0`
+
+A minimal staged config looks like this:
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    '*': 'vp check --fix',
+  },
+});
+```
+
+## Asking for Help
+
+If you are stuck, please reach out:
+
+- [Discord](https://discord.gg/cAnsqHh5PX) for real-time discussion and troubleshooting help
+- [GitHub](https://github.com/voidzero-dev/vite-plus) for issues, discussions, and bug reports
+
+When reporting a problem, please include:
+
+- The full output of `vp env current` and `vp --version`
+- The package manager used by the project
+- The exact steps needed to reproduce the problem and your `vite.config.ts`
+- A minimal reproduction repository or runnable sandbox
diff --git a/docs/guide/upgrade.md b/docs/guide/upgrade.md
new file mode 100644
index 0000000000..d066158f0a
--- /dev/null
+++ b/docs/guide/upgrade.md
@@ -0,0 +1,28 @@
+# Upgrading Vite+
+
+Use `vp upgrade` to update the global `vp` binary, and use Vite+'s package management commands to update the local `vite-plus` package in a project.
+
+## Overview
+
+There are two parts to upgrading Vite+:
+
+- The global `vp` command installed on your machine
+- The local `vite-plus` package used by an individual project
+
+You can upgrade both of them independently.
+
+## Global `vp`
+
+```bash
+vp upgrade
+```
+
+## Local `vite-plus`
+
+Update the project dependency with the package manager commands in Vite+:
+
+```bash
+vp update vite-plus
+```
+
+You can also use `vp add vite-plus@latest` if you want to move the dependency explicitly to the latest version.
diff --git a/docs/guide/vpx.md b/docs/guide/vpx.md
new file mode 100644
index 0000000000..0bf80c820c
--- /dev/null
+++ b/docs/guide/vpx.md
@@ -0,0 +1,66 @@
+# Running Binaries
+
+Use `vpx`, `vp exec`, and `vp dlx` to run binaries without switching between local installs, downloaded packages, and project-specific tools.
+
+## Overview
+
+`vpx` executes a command from a local or remote npm package. It can run a package that is already available locally, download a package on demand, or target an explicit package version.
+
+Use the other binary commands when you need stricter control:
+
+- `vpx` resolves a package binary locally first and can download it when needed
+- `vp exec` runs a binary from the current project's `node_modules/.bin`
+- `vp dlx` runs a package binary without adding it as a dependency
+
+## `vpx`
+
+Use `vpx` for running any local or remote binary:
+
+```bash
+vpx <pkg[@version]> [args...]
+```
+
+### Options
+
+- `-p, --package <name>` installs one or more packages before running the command
+- `-c, --shell-mode` executes the command inside a shell
+- `-s, --silent` suppresses Vite+ output and only shows the command output
+
+### Examples
+
+```bash
+vpx eslint .
+vpx create-vue my-app
+vpx typescript@5.5.4 tsc --version
+vpx -p cowsay -c 'echo "hi" | cowsay'
+```
+
+## `vp exec`
+
+Use `vp exec` when the binary must come from the current project, for example a binary from a dependency installed in `node_modules/.bin`.
+
+```bash
+vp exec <command> [args...]
+```
+
+Examples:
+
+```bash
+vp exec eslint .
+vp exec tsc --noEmit
+```
+
+## `vp dlx`
+
+Use `vp dlx` for one-off package execution without adding the package to your project dependencies.
+
+```bash
+vp dlx <package> [args...]
+```
+
+Examples:
+
+```bash
+vp dlx create-vite
+vp dlx typescript tsc --version
+```
diff --git a/docs/lib/guide/getting-started.md b/docs/lib/guide/getting-started.md
deleted file mode 100644
index 060a29ffae..0000000000
--- a/docs/lib/guide/getting-started.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Getting Started
-
-## Overview
-
-Vite+ is the unified toolchain and entry point for modern web application development. It manages your runtime, package manager, and frontend toolchain in one place by combining [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):
-
-- **Runtime Management:** Manage Node.js globally and per-project with `vp env`
-- **Package Management:** Install and manage dependencies with `vp install` and related commands
-- **Dev Server:** Run Vite's native ESM dev server with `vp dev`
-- **Code Health:** Run linting, formatting, and type checks with Oxlint, Oxfmt, and `tsgo` via `vp check`
-- **Testing:** Run tests with bundled Vitest via `vp test`
-- **Build & Pack:** Build apps with `vp build` and build libraries or standalone app binaries with `vp pack`
-- **Task Runner:** Execute monorepo tasks with `vp run` and automated caching/dependency resolution
-
-All in a single, cohesive tool designed for scale, speed, and developer sanity.
-Vite+ is fully open-source under the MIT license.
diff --git a/docs/package.json b/docs/package.json
index 3902445ed3..7f8be0f2e7 100644
--- a/docs/package.json
+++ b/docs/package.json
@@ -15,7 +15,7 @@
     "vue3-carousel": "^0.16.0"
   },
   "devDependencies": {
-    "@voidzero-dev/vitepress-theme": "4.8.0",
+    "@voidzero-dev/vitepress-theme": "4.8.2",
     "oxc-minify": "^0.110.0",
     "tailwindcss": "^4.1.18",
     "vitepress": "2.0.0-alpha.15"
diff --git a/docs/vite/guide/caching.md b/docs/vite/guide/caching.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/vite/guide/cli.md b/docs/vite/guide/cli.md
deleted file mode 100644
index fef369a1d2..0000000000
--- a/docs/vite/guide/cli.md
+++ /dev/null
@@ -1,734 +0,0 @@
-# Command Line Interface
-
-## `vp` CLI
-
-The `vp` command is the main entry point for Vite+ (vite-plus), a monorepo task runner with intelligent caching and dependency resolution.
-
-**Type:** `vp <COMMAND> [ARGS] [OPTIONS]`
-
-## Dev Server
-
-### `vp dev`
-
-Start Vite dev server in the current directory. `vp serve` is an alias for `vp dev`.
-
-#### Usage
-
-```bash
-vp dev [root] [OPTIONS]
-```
-
-#### Arguments
-
-| Arguments | Description                                                                       |
-| --------- | --------------------------------------------------------------------------------- |
-| `root`    | The root directory to start the dev server from, default is the current directory |
-
-#### Options
-
-| Options                   |                                                                                                                                                                                      |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `--host [host]`           | Specify hostname (`string`)                                                                                                                                                          |
-| `--port <port>`           | Specify port (`number`)                                                                                                                                                              |
-| `--open [path]`           | Open browser on startup (`boolean \| string`)                                                                                                                                        |
-| `--cors`                  | Enable CORS (`boolean`)                                                                                                                                                              |
-| `--strictPort`            | Exit if specified port is already in use (`boolean`)                                                                                                                                 |
-| `--force`                 | Force the optimizer to ignore the cache and re-bundle (`boolean`)                                                                                                                    |
-| `-c, --config <file>`     | Use specified config file (`string`)                                                                                                                                                 |
-| `--base <path>`           | Public base path (default: `/`) (`string`)                                                                                                                                           |
-| `-l, --logLevel <level>`  | info \| warn \| error \| silent (`string`)                                                                                                                                           |
-| `--clearScreen`           | Allow/disable clear screen when logging (`boolean`)                                                                                                                                  |
-| `--configLoader <loader>` | Use `bundle` to bundle the config with esbuild, or `runner` (experimental) to process it on the fly, or `native` (experimental) to load using the native runtime (default: `bundle`) |
-| `--profile`               | Start built-in Node.js inspector (check [Performance bottlenecks](./troubleshooting.md#performance-bottlenecks))                                                                     |
-| `-d, --debug [feat]`      | Show debug logs (`string \| boolean`)                                                                                                                                                |
-| `-f, --filter <filter>`   | Filter debug logs (`string`)                                                                                                                                                         |
-| `-m, --mode <mode>`       | Set env mode (`string`)                                                                                                                                                              |
-| `-h, --help`              | Display available CLI options                                                                                                                                                        |
-
-#### Examples
-
-```bash
-vp dev
-vp dev ./apps/website
-vp dev --port 3000
-```
-
-## Build Application
-
-### `vp build`
-
-Build for production.
-
-#### Usage
-
-```bash
-vp build [root] [OPTIONS]
-```
-
-#### Arguments
-
-| Arguments | Description                                                        |
-| --------- | ------------------------------------------------------------------ |
-| `root`    | The root directory to build from, default is the current directory |
-
-#### Options
-
-| Options                        |                                                                                                                        |
-| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
-| `--target <target>`            | Transpile target (default: `"modules"`) (`string`)                                                                     |
-| `--outDir <dir>`               | Output directory (default: `dist`) (`string`)                                                                          |
-| `--assetsDir <dir>`            | Directory under outDir to place assets in (default: `"assets"`) (`string`)                                             |
-| `--assetsInlineLimit <number>` | Static asset base64 inline threshold in bytes (default: `4096`) (`number`)                                             |
-| `--ssr [entry]`                | Build specified entry for server-side rendering (`string`)                                                             |
-| `--sourcemap [output]`         | Output source maps for build (default: `false`) (`boolean \| "inline" \| "hidden"`)                                    |
-| `--minify [minifier]`          | Enable/disable minification, or specify minifier to use (default: `"esbuild"`) (`boolean \| "terser" \| "esbuild"`)    |
-| `--manifest [name]`            | Emit build manifest json (`boolean \| string`)                                                                         |
-| `--ssrManifest [name]`         | Emit ssr manifest json (`boolean \| string`)                                                                           |
-| `--emptyOutDir`                | Force empty outDir when it's outside of root (`boolean`)                                                               |
-| `-w, --watch`                  | Rebuilds when modules have changed on disk (`boolean`)                                                                 |
-| `-c, --config <file>`          | Use specified config file (`string`)                                                                                   |
-| `--base <path>`                | Public base path (default: `/`) (`string`)                                                                             |
-| `-l, --logLevel <level>`       | Info \| warn \| error \| silent (`string`)                                                                             |
-| `--clearScreen`                | Allow/disable clear screen when logging (`boolean`)                                                                    |
-| `--configLoader <loader>`      | Use `bundle` to bundle the config with esbuild or `runner` (experimental) to process it on the fly (default: `bundle`) |
-| `--profile`                    | Start built-in Node.js inspector (check [Performance bottlenecks](./troubleshooting.md#performance-bottlenecks))       |
-| `-d, --debug [feat]`           | Show debug logs (`string \| boolean`)                                                                                  |
-| `-f, --filter <filter>`        | Filter debug logs (`string`)                                                                                           |
-| `-m, --mode <mode>`            | Set env mode (`string`)                                                                                                |
-| `-h, --help`                   | Display available CLI options                                                                                          |
-| `--app`                        | Build all environments, same as `builder: {}` (`boolean`, experimental)                                                |
-
-## Pack Libraries
-
-### `vp pack`
-
-Pack libraries using tsdown.
-
-#### Usage
-
-```bash
-vp pack [<ARGS>...]
-```
-
-#### Examples
-
-```bash
-vp pack
-vp pack --watch
-vp pack --outdir dist
-```
-
-## Build Documentation
-
-### `vp doc`
-
-Build documentation using VitePress.
-
-#### Usage
-
-```bash
-vp doc [<ARGS>...]
-```
-
-#### Examples
-
-```bash
-vp doc build
-vp doc dev
-vp doc dev --host 0.0.0.0
-```
-
-## Lint
-
-### `vp lint`
-
-Lint code using oxlint.
-
-#### Usage
-
-```bash
-vp lint [<ARGS>...]
-```
-
-#### Examples
-
-```bash
-vp lint
-vp lint --fix
-vp lint --quiet
-```
-
-## Format
-
-### `vp fmt`
-
-Format code using oxfmt.
-
-#### Usage
-
-```bash
-vp fmt [<ARGS>...]
-```
-
-#### Examples
-
-```bash
-vp fmt
-vp fmt --check
-vp fmt --ignore-path .gitignore
-```
-
-## Testing
-
-### `vp test`
-
-Run tests using Vitest.
-By default, `vp test` runs once and exits (equivalent to `vitest run`).
-Use watch mode explicitly with `vp test watch`.
-
-#### Usage
-
-```bash
-vp test [<ARGS>...]
-```
-
-#### Examples
-
-```bash
-vp test
-vp test watch
-vp test run --coverage
-```
-
-## Task Runner
-
-### `vp run`
-
-Run tasks across monorepo packages with automatic dependency ordering.
-
-#### Usage
-
-```bash
-vp run <TASKS>... [OPTIONS] [-- <TASK_ARGS>...]
-```
-
-#### Examples
-
-```bash
-# Run build in specific packages
-vp run app#build web#build
-
-# Run build recursively across all packages
-vp run build --recursive
-
-# Run without topological ordering
-vp run build --recursive --no-topological
-
-# Pass arguments to tasks
-vp run test -- --watch --coverage
-```
-
-#### Options
-
-| Option             | Alias | Description                                               |
-| ------------------ | ----- | --------------------------------------------------------- |
-| `--recursive`      | `-r`  | Run task in all packages that have it                     |
-| `--no-recursive`   |       | Explicitly disable recursive mode                         |
-| `--sequential`     | `-s`  | Run tasks sequentially (future)                           |
-| `--no-sequential`  |       | Explicitly disable sequential mode                        |
-| `--parallel`       | `-p`  | Run tasks in parallel (future)                            |
-| `--no-parallel`    |       | Explicitly disable parallel mode                          |
-| `--topological`    | `-t`  | Enable topological ordering based on package dependencies |
-| `--no-topological` |       | Disable topological ordering                              |
-
-#### Task Naming
-
-- **Scoped**: `<package>#<task>` (e.g., `app#build`)
-- **Unscoped**: `<task>` (runs in current package or all packages with `-r`)
-
-#### Dependency Modes
-
-1. **Explicit Dependencies** (always applied):
-   - Defined in `vite-task.json` `dependsOn` field
-   - Example: `"test": { "dependsOn": ["build", "lint"] }`
-
-2. **Implicit Dependencies** (when `--topological`):
-   - Based on package.json dependencies
-   - If package A depends on B, then `A#build` depends on `B#build`
-   - Default: ON for `--recursive`, OFF otherwise
-
-### Global Options
-
-| Option       | Alias | Description                             |
-| ------------ | ----- | --------------------------------------- |
-| `--debug`    | `-d`  | Display cache information for debugging |
-| `--no-debug` |       | Explicitly disable debug mode           |
-| `--help`     | `-h`  | Display help information                |
-| `--version`  | `-V`  | Show version number                     |
-
-### Task Configuration
-
-Tasks are configured in `vite-task.json` files:
-
-```json
-{
-  "tasks": {
-    "build": {
-      "command": "tsc && rollup",
-      "cacheable": true,
-      "dependsOn": ["lint"],
-      "envs": ["NODE_ENV"],
-      "fingerprintIgnores": ["node_modules/**/*", "!node_modules/**/package.json"]
-    }
-  }
-}
-```
-
-#### Configuration Fields
-
-| Field                | Type       | Description                                         |
-| -------------------- | ---------- | --------------------------------------------------- |
-| `command`            | `string`   | Shell command to execute                            |
-| `cacheable`          | `boolean`  | Whether to cache task results (default: `true`)     |
-| `dependsOn`          | `string[]` | Explicit task dependencies                          |
-| `cwd`                | `string`   | Working directory for the command                   |
-| `envs`               | `string[]` | Environment variables that affect cache             |
-| `passThroughEnvs`    | `string[]` | Environment variables passed but don't affect cache |
-| `inputs`             | `string[]` | Input file patterns (future)                        |
-| `fingerprintIgnores` | `string[]` | Glob patterns to exclude from cache fingerprint     |
-
-### Fingerprint Ignores
-
-Control which files trigger cache invalidation:
-
-```json
-{
-  "tasks": {
-    "install": {
-      "command": "pnpm install",
-      "cacheable": true,
-      "fingerprintIgnores": ["node_modules/**/*", "!node_modules/**/package.json"]
-    }
-  }
-}
-```
-
-#### Pattern Syntax
-
-- **Basic**: `node_modules/**/*` - ignore all files under node_modules
-- **Negation**: `!node_modules/**/package.json` - include package.json files
-- **Order matters**: Last matching pattern wins (gitignore-style)
-
-### Caching
-
-Vite+ uses intelligent caching to speed up task execution:
-
-#### Cache Key Components
-
-- Command fingerprint (command + cwd + envs)
-- Post-run fingerprint (input file hashes)
-- Task arguments
-
-#### Cache Behavior
-
-```bash
-# First run - executes task
-vp run build
-# → Cache miss: no previous cache entry found
-
-# Second run - replays from cache
-vp run build
-# → Cache hit - output replayed
-
-# Modify source file
-echo "new content" > src/index.ts
-# → Cache miss: content of input 'src/index.ts' changed
-
-# Modify ignored file (with fingerprintIgnores)
-echo "modified" > node_modules/pkg/index.js
-# → Cache hit - ignored file doesn't invalidate cache
-```
-
-#### Cache Location
-
-- Default: `.vite-task-cache/` in workspace root
-- Contains SQLite database with task results
-
-#### Debug Cache
-
-```bash
-# View cache entries
-vp cache view
-
-# Enable cache debug output
-vp run build --debug
-
-# Clean cache
-vp cache clean
-```
-
-### Environment Variables
-
-| Variable                  | Description                                  |
-| ------------------------- | -------------------------------------------- |
-| `VITE_LOG`                | Set logging level (e.g., `VITE_LOG=debug`)   |
-| `VITE_TASK_EXECUTION_ENV` | Internal: indicates running inside vite task |
-| `VITE_TASK_EXECUTION_ID`  | Internal: unique ID for task execution       |
-
-### Execution Modes
-
-#### Explicit Mode (default)
-
-Run specific tasks:
-
-```bash
-vp run app#build web#build
-```
-
-#### Recursive Mode
-
-Run task in all packages:
-
-```bash
-vp run build --recursive
-vp run build -r
-```
-
-**Behavior:**
-
-- Finds all packages with the specified task
-- Runs tasks in dependency order (when `--topological`)
-- Default topological ordering for recursive mode
-
-#### Topological Ordering
-
-Controls implicit dependencies based on package relationships:
-
-```bash
-# With topological (default for recursive)
-vp run build -r
-# → If A depends on B, A#build waits for B#build
-
-# Without topological
-vp run build -r --no-topological
-# → Only explicit dependencies, no implicit ordering
-```
-
-### Task Arguments
-
-Pass arguments to tasks using `--`:
-
-```bash
-# Arguments go to all tasks
-vp run build test -- --watch
-
-# For built-in commands
-vp test -- --coverage --run
-vp lint -- --fix
-```
-
-### Examples
-
-#### Common Workflows
-
-```bash
-# Install dependencies
-vp install
-
-# Lint and fix issues
-vp lint -- --fix
-
-# Format code
-vp fmt
-
-# Run build recursively
-vp run build -r
-
-# Run tests in watch mode
-vp test -- --watch
-
-# Build for production
-vp build
-
-# Start dev server
-vp dev
-
-# Build library
-vp pack
-
-# Build docs
-vp doc build
-
-# Preview docs
-vp doc dev
-```
-
-#### Monorepo Workflows
-
-```bash
-# Build all packages in dependency order
-vp run build --recursive
-
-# Build specific packages
-vp run app#build utils#build
-
-# Run tests without topological ordering
-vp run test -r --no-topological
-
-# Clean cache and rebuild
-vp cache clean
-vp run build -r
-```
-
-### Exit Codes
-
-- `0` - Success (all tasks completed successfully)
-- `Non-zero` - Failure (one or more tasks failed), or system error (workspace not found, cache error, etc.)
-
-**Note:** When running multiple tasks, the first non-zero exit code is returned.
-
-### Debugging
-
-Enable verbose logging:
-
-```bash
-# Debug mode - shows cache operations
-vp run build --debug
-
-# Trace logging
-VITE_LOG=debug vp run build
-
-# View cache contents
-vp cache view
-```
-
-## Package Management
-
-### `vp install`
-
-Aliases: `vp i`
-
-Install dependencies using the detected package manager.
-
-#### Usage
-
-```bash
-vp install [ARGS] [OPTIONS]
-```
-
-#### Examples
-
-```bash
-vp install
-vp install --loglevel debug
-```
-
-#### Note
-
-- Auto-detects package manager (pnpm/yarn/npm)
-- Prompts for selection if none package manager detected
-
-### `vp update`
-
-Aliases: `vp up`
-
-Updates packages to their latest version based on the specified range.
-
-#### Usage
-
-```bash
-vp update [-g] [<pkg>...]
-```
-
-#### Examples
-
-```bash
-vp update
-vp update @types/node
-```
-
-### `vp add`
-
-Installs packages.
-
-#### Usage
-
-```bash
-vp add [OPTIONS] <package>[@version]...
-```
-
-#### Examples
-
-```bash
-vp add -D @types/node
-```
-
-### `vp remove`
-
-Aliases: `vp rm`, `vp uninstall`, `vp un`
-
-Removes packages.
-
-#### Usage
-
-```bash
-vp remove <package>[@version]...
-```
-
-```bash
-vp remove @types/node
-```
-
-### `vp link`
-
-Aliases: `vp ln`
-
-Makes the current local package accessible system-wide, or in another location.
-
-### `vp unlink`
-
-Unlinks a system-wide package (inverse of `vp link`).
-
-If called without arguments, all linked dependencies will be unlinked inside the current project.
-
-### `vp dedupe`
-
-Perform an install removing older dependencies in the lockfile if a newer version can be used.
-
-### `vp outdated`
-
-Shows outdated packages.
-
-### `vp why`
-
-Aliases: `vp explain`
-
-Shows all packages that depend on the specified package.
-
-### `vp pm <subcommand>`
-
-The `vp pm` command group provides a set of utilities for working with package manager.
-
-> package manager commands with low usage frequency will under this command group.
-
-#### `vp pm prune`
-
-Removes unnecessary packages.
-
-#### `vp pm pack`
-
-Pack the current package into a tarball.
-
-#### `vp pm list`
-
-Aliases: `vp pm ls`
-
-List installed packages.
-
-#### `vp pm view`
-
-View a package info from the registry.
-
-#### `vp pm publish`
-
-Publishes a package to the registry.
-
-#### `vp pm owner`
-
-Manage package owners.
-
-#### `vp pm cache`
-
-Manage the packages metadata cache.
-
-## Others
-
-### `vp optimize`
-
-Pre-bundle dependencies.
-
-**Deprecated**: the pre-bundle process runs automatically and does not need to be called.
-
-#### Usage
-
-```bash
-vp optimize [root]
-```
-
-#### Options
-
-| Options                   |                                                                                                                        |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `--force`                 | Force the optimizer to ignore the cache and re-bundle (`boolean`)                                                      |
-| `-c, --config <file>`     | Use specified config file (`string`)                                                                                   |
-| `--base <path>`           | Public base path (default: `/`) (`string`)                                                                             |
-| `-l, --logLevel <level>`  | Info \| warn \| error \| silent (`string`)                                                                             |
-| `--clearScreen`           | Allow/disable clear screen when logging (`boolean`)                                                                    |
-| `--configLoader <loader>` | Use `bundle` to bundle the config with esbuild or `runner` (experimental) to process it on the fly (default: `bundle`) |
-| `-d, --debug [feat]`      | Show debug logs (`string \| boolean`)                                                                                  |
-| `-f, --filter <filter>`   | Filter debug logs (`string`)                                                                                           |
-| `-m, --mode <mode>`       | Set env mode (`string`)                                                                                                |
-| `-h, --help`              | Display available CLI options                                                                                          |
-
-### `vp preview`
-
-Locally preview the production build. Do not use this as a production server as it's not designed for it.
-
-This command starts a server in the build directory (by default `dist`). Run `vp build` beforehand to ensure that the build directory is up-to-date. Depending on the project's configured [`appType`](../../config/shared-options.md#apptype), it makes use of certain middleware.
-
-#### Usage
-
-```bash
-vp preview [root]
-```
-
-#### Options
-
-| Options                   |                                                                                                                        |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `--host [host]`           | Specify hostname (`string`)                                                                                            |
-| `--port <port>`           | Specify port (`number`)                                                                                                |
-| `--strictPort`            | Exit if specified port is already in use (`boolean`)                                                                   |
-| `--open [path]`           | Open browser on startup (`boolean \| string`)                                                                          |
-| `--outDir <dir>`          | Output directory (default: `dist`)(`string`)                                                                           |
-| `-c, --config <file>`     | Use specified config file (`string`)                                                                                   |
-| `--base <path>`           | Public base path (default: `/`) (`string`)                                                                             |
-| `-l, --logLevel <level>`  | Info \| warn \| error \| silent (`string`)                                                                             |
-| `--clearScreen`           | Allow/disable clear screen when logging (`boolean`)                                                                    |
-| `--configLoader <loader>` | Use `bundle` to bundle the config with esbuild or `runner` (experimental) to process it on the fly (default: `bundle`) |
-| `-d, --debug [feat]`      | Show debug logs (`string \| boolean`)                                                                                  |
-| `-f, --filter <filter>`   | Filter debug logs (`string`)                                                                                           |
-| `-m, --mode <mode>`       | Set env mode (`string`)                                                                                                |
-| `-h, --help`              | Display available CLI options                                                                                          |
-
-### `vp cache`
-
-Manage the task cache.
-
-#### Usage
-
-```bash
-vp cache <clean|view>
-```
-
-#### `vp cache clean`
-
-Clean up all cached task results.
-
-```bash
-vp cache clean
-```
-
-#### `vp cache view`
-
-View cache entries in JSON format for debugging.
-
-```bash
-vp cache view
-```
-
-## See Also
-
-- [Task Configuration](./tasks.md#configuration)
-- [Caching Strategy](./caching.md)
-- [Monorepo Guide](./monorepo.md)
diff --git a/docs/vite/guide/index.md b/docs/vite/guide/index.md
deleted file mode 100644
index 64d472efdb..0000000000
--- a/docs/vite/guide/index.md
+++ /dev/null
@@ -1,218 +0,0 @@
-# Getting Started
-
-## Overview
-
-Vite+ is the unified toolchain and entry point for modern web application development. It manages your runtime, package manager, and frontend toolchain in one place by combining [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):
-
-- **Runtime Management**: Manage Node.js globally and per project with `vp env`
-- **Package Management**: Install and manage dependencies with `vp install` and package-manager wrappers
-- **Dev Server**: Run Vite's native ESM dev server with instant HMR via `vp dev`
-- **Code Health**: Run linting, formatting, and type checks with Oxlint, Oxfmt, and `tsgo` via `vp check`
-- **Testing**: Run tests through bundled Vitest with `vp test`
-- **Build & Pack**: Build apps with `vp build` and build libraries or standalone app binaries with `vp pack`
-- **Task Runner**: Run monorepo tasks with caching and dependency-aware scheduling via `vp run`
-- **Scaffolding & Migration**: Create new projects or monorepos and migrate existing ones with `vp create` and `vp migrate`
-
-All in a single, cohesive tool designed for scale, speed, and developer sanity.
-Vite+ is fully open-source under the MIT license.
-
-## Installation
-
-Install Vite+ globally as `vp`:
-
-For Linux or macOS:
-
-```bash
-curl -fsSL https://viteplus.dev/install.sh | bash
-```
-
-For Windows:
-
-```bash
-irm https://viteplus.dev/install.ps1 | iex
-```
-
-::: details Supported platforms
-
-Prebuilt binaries are distributed for the following platforms (grouped by [Node.js v24 platform support tier](https://github.com/nodejs/node/blob/v24.x/BUILDING.md#platform-list)):
-
-- Tier 1
-  - Linux x64 glibc (`x86_64-unknown-linux-gnu`)
-  - Linux arm64 glibc (`aarch64-unknown-linux-gnu`)
-  - Windows x64 (`x86_64-pc-windows-msvc`)
-  - macOS x64 (`x86_64-apple-darwin`)
-  - macOS arm64 (`aarch64-apple-darwin`)
-- Tier 2
-  - Windows arm64 (`aarch64-pc-windows-msvc`)
-
-:::
-
-## Node.js Version Manager
-
-Vite+ includes a built-in Node.js version manager. During installation, you can opt-in to let Vite+ manage your Node.js versions.
-
-```bash
-vp env pin 22.12.0        # Pin version in .node-version
-vp env default lts        # Set global default
-vp env list               # Show available versions
-vp env doctor             # Diagnose issues
-vp env help               # Show all commands
-```
-
-## Scaffolding Your First Vite+ Project
-
-Create a Vite+ project or monorepo:
-
-```bash
-vp create
-```
-
-Follow the prompts to select your preferred framework, workspace shape, and configuration.
-
-## CLI Workflows
-
-`vp help` organizes commands by workflow:
-
-```bash
-# Start
-vp create           # Scaffold a new project
-vp migrate          # Migrate an existing project
-vp install          # Install dependencies
-vp env              # Manage Node.js versions
-
-# Develop
-vp dev              # Start dev server
-vp check            # Format, lint, and type-check
-vp test             # Run tests
-
-# Execute
-vp run              # Run monorepo tasks
-vp exec             # Run local binaries
-vp dlx              # Run remote/local package binaries
-
-# Build
-vp build            # Build applications
-vp pack             # Pack libraries
-vp preview          # Preview production build
-```
-
-## Monorepo Task Execution
-
-Vite+ includes a powerful task runner for managing tasks across monorepo packages:
-
-### Run tasks recursively
-
-```bash
-vp run build -r              # Build all packages with topological ordering
-vp run test -r               # Test all packages
-```
-
-### Run tasks for specific packages
-
-```bash
-vp run app#build web#build   # Build specific packages
-vp run @scope/*#test         # Test all packages matching pattern
-```
-
-### Current package
-
-```bash
-vp dev                       # Run dev script in current package
-```
-
-## Task Dependencies
-
-Tasks automatically respect dependencies:
-
-1. **Explicit dependencies** - Defined in `vite-task.json`:
-
-```json
-{
-  "tasks": {
-    "test": {
-      "command": "jest",
-      "dependsOn": ["build", "lint"]
-    }
-  }
-}
-```
-
-2. **Implicit dependencies** - Based on `package.json` relationships when using `--topological` (default for `-r`):
-   - If package A depends on package B, then `A#build` automatically depends on `B#build`
-
-Disable topological ordering:
-
-```bash
-vp run build -r --no-topological
-```
-
-## Intelligent Caching
-
-Vite+ caches task outputs to speed up repeated builds:
-
-- Automatically detects when inputs change
-- Skips tasks when outputs are cached
-- Shares cache across team members (when configured)
-
-View cache operations:
-
-```bash
-vp run build -r --debug
-```
-
-## CI/CD
-
-Use the official [`setup-vp`](https://github.com/voidzero-dev/setup-vp) GitHub Action to install Vite+ in CI:
-
-### Basic usage
-
-```yaml
-steps:
-  - uses: actions/checkout@v4
-  - uses: voidzero-dev/setup-vp@v1
-    with:
-      node-version: '22'
-      cache: true
-  - run: vp run build -r
-  - run: vp run test -r
-```
-
-### Matrix testing
-
-```yaml
-jobs:
-  test:
-    strategy:
-      matrix:
-        node-version: ['20', '22', '24']
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: voidzero-dev/setup-vp@v1
-        with:
-          node-version: ${{ matrix.node-version }}
-          cache: true
-      - run: vp run test -r
-```
-
-See the [setup-vp README](https://github.com/voidzero-dev/setup-vp) for all options.
-
-## Next Steps
-
-- Learn more about [task configuration](./task/getting-started)
-- Explore [caching strategies](./caching)
-- Set up [monorepo workspaces](./monorepo)
-- Customize [Vite+ configuration](../../config/)
-
-## Community & Support
-
-Get help and stay updated:
-
-- [GitHub Issues](https://github.com/voidzero-dev/vite-plus/issues)
-- [GitHub Discussions](https://github.com/voidzero-dev/vite-plus/discussions)
-
----
-
-::: tip Requirements
-Vite+ requires Node.js 20.19+, 22.12+ or 24.12+
-:::
diff --git a/docs/vite/guide/migration.md b/docs/vite/guide/migration.md
deleted file mode 100644
index 4e20ca0571..0000000000
--- a/docs/vite/guide/migration.md
+++ /dev/null
@@ -1,453 +0,0 @@
-# Migration Guide
-
-This guide will help you migrate your existing Vite and Vitest projects to Vite+.
-
-## Prerequisites
-
-Before migrating to Vite+, ensure your project meets the following version requirements:
-
-### Vite 8.x Required
-
-Vite+ requires **Vite 8.x** or higher. If you're currently using Vite 7.x or earlier, you must upgrade first.
-
-**To upgrade from Vite 7 to Vite 8:**
-
-1. Refer to the official [Vite Migration Guide](https://main.vite.dev/guide/migration.html) for detailed instructions.
-
-2. Key breaking changes in Vite 8:
-   - **Build targets updated**: Chrome 111+, Edge 111+, Firefox 114+, Safari 16.4+
-   - **Rolldown & Oxc adoption**: Vite 8 uses Rolldown and Oxc-based tools instead of esbuild and Rollup
-   - **Configuration changes**:
-     - Migrate `esbuild` options to `oxc`
-     - Migrate `optimizeDeps.esbuildOptions` to `optimizeDeps.rolldownOptions`
-     - Migrate `build.rollupOptions` to `build.rolldownOptions`
-
-3. Update your `package.json`:
-   ```json
-   {
-     "devDependencies": {
-       "vite": "^8.0.0"
-     }
-   }
-   ```
-
-### Vitest 4.x Required
-
-Vite+ requires **Vitest 4.x** or higher. If you're currently using Vitest 3.x or earlier, you must upgrade first.
-
-**To upgrade from Vitest 3 to Vitest 4:**
-
-1. Refer to the official [Vitest Migration Guide](https://vitest.dev/guide/migration.html) for detailed instructions.
-
-2. Key breaking changes in Vitest 4:
-   - **V8 coverage overhaul**: Uses AST-based analysis instead of `v8-to-istanbul`
-   - **Coverage options removed**: `coverage.all` and `coverage.extensions` are removed; use `coverage.include` instead
-   - **Test exclusions narrowed**: Only `node_modules` and `.git` are excluded by default
-   - **Module Runner replacement**: `vite-node` is replaced with Vite's Module Runner
-   - **Configuration changes**:
-     - `workspace` renamed to `projects`
-     - `maxThreads`/`maxForks` become `maxWorkers`
-     - Pool options moved to top level
-
-3. Update your `package.json`:
-   ```json
-   {
-     "devDependencies": {
-       "vitest": "^4.0.0"
-     }
-   }
-   ```
-
-## Automatic Migration
-
-Vite+ provides an automated migration command that handles most of the migration work for you.
-
-### Running the Migration
-
-```bash
-# Migrate current directory
-vp migrate
-```
-
-### What the Migration Does
-
-The `vp migrate` command automatically:
-
-1. **Updates dependencies**: Replaces standalone `vite`, `vitest`, `oxlint`, and `oxfmt` with unified Vite+ packages
-2. **Configures overrides**: Adds package manager overrides to ensure all dependencies use Vite+ versions
-3. **Rewrites imports**: Updates `import from 'vite'` and `import from 'vitest/config'` to `import from 'vite-plus'`
-4. **Merges configurations**: Consolidates `.oxlintrc` and `.oxfmtrc` into `vite.config.ts`
-5. **Updates scripts**: Rewrites npm scripts to use Vite+ commands
-
-### Migration Preview
-
-When you run the migration command, you'll see a preview of changes:
-
-```bash
-$ vp migrate
-
-◇  Analyzing project...
-│
-◆  Detected standalone tools:
-│  ✓ vite ^8.0.0
-│  ✓ vitest ^4.0.0
-│  ✓ oxlint ^0.1.0
-│
-◆  Configuration files found:
-│  • vite.config.ts
-│  • vitest.config.ts
-│  • .oxlintrc
-│
-◆  Migration plan:
-│
-│  Dependencies (package.json):
-│  - vite: ^8.0.0
-│  - vitest: ^4.0.0
-│  - oxlint: ^0.1.0
-│  + vite-plus: latest
-│
-│  Configuration:
-│  ✓ Merge .oxlintrc → vite.config.ts
-│  ✓ Update imports in config files
-│
-◆  Proceed with migration?
-│  ● Yes / ○ No / ○ Preview changes
-```
-
-## Manual Migration Steps
-
-If you prefer to migrate manually or need to understand what changes are made, follow these steps:
-
-### 1. Update Dependencies
-
-#### For Standalone Projects
-
-**pnpm:**
-
-```json
-{
-  "devDependencies": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest",
-    "vite-plus": "latest"
-  },
-  "pnpm": {
-    "overrides": {
-      "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-      "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
-    }
-  }
-}
-```
-
-**npm:**
-
-```json
-{
-  "devDependencies": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest",
-    "vite-plus": "latest"
-  },
-  "overrides": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
-  }
-}
-```
-
-**yarn:**
-
-```json
-{
-  "devDependencies": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest",
-    "vite-plus": "latest"
-  },
-  "resolutions": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
-  }
-}
-```
-
-#### For pnpm Monorepos
-
-Add to `pnpm-workspace.yaml`:
-
-```yaml
-catalog:
-  vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: npm:@voidzero-dev/vite-plus-test@latest
-  'vite-plus': latest
-
-overrides:
-  vite: 'catalog:'
-  vitest: 'catalog:'
-
-peerDependencyRules:
-  allowAny:
-    - vite
-    - vitest
-  allowedVersions:
-    vite: '*'
-    vitest: '*'
-```
-
-#### For npm Monorepos
-
-Add to root `package.json`:
-
-```json
-{
-  "devDependencies": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest",
-    "vite-plus": "latest"
-  },
-  "overrides": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
-  }
-}
-```
-
-#### For Yarn 4.10+ Monorepos
-
-Add to `.yarnrc.yml`:
-
-```yaml
-catalog:
-  vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: npm:@voidzero-dev/vite-plus-test@latest
-  'vite-plus': latest
-```
-
-Add to root `package.json`:
-
-```json
-{
-  "resolutions": {
-    "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-    "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
-  }
-}
-```
-
-### 3. Update Configuration Files
-
-#### Update vite.config.ts
-
-**Before:**
-
-```typescript
-import { defineConfig } from 'vite';
-
-export default defineConfig({
-  // your config
-});
-```
-
-**After:**
-
-```typescript
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  // your config
-});
-```
-
-#### Update vitest.config.ts
-
-**Before:**
-
-```typescript
-import { defineConfig } from 'vitest/config';
-
-export default defineConfig({
-  test: {
-    // your test config
-  },
-});
-```
-
-**After:**
-
-```typescript
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  test: {
-    // your test config
-  },
-});
-```
-
-### 4. Merge Linter Configuration
-
-If you have an `.oxlintrc` file, merge it into `vite.config.ts`:
-
-**Before (.oxlintrc):**
-
-```json
-{
-  "rules": {
-    "no-unused-vars": "error",
-    "no-console": "warn"
-  },
-  "ignorePatterns": ["dist", "node_modules"]
-}
-```
-
-**After (vite.config.ts):**
-
-```typescript
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  lint: {
-    rules: {
-      'no-unused-vars': 'error',
-      'no-console': 'warn',
-    },
-    ignorePatterns: ['dist', 'node_modules'],
-  },
-});
-```
-
-### 5. Merge Formatter Configuration
-
-If you have an `.oxfmtrc` file, merge it into `vite.config.ts`:
-
-**Before (.oxfmtrc):**
-
-```json
-{
-  "printWidth": 100,
-  "tabWidth": 2,
-  "semi": true,
-  "singleQuote": true
-}
-```
-
-**After (vite.config.ts):**
-
-```typescript
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  fmt: {
-    printWidth: 100,
-    tabWidth: 2,
-    semi: true,
-    singleQuote: true,
-  },
-});
-```
-
-### 6. Update lint-staged Configuration {#lint-staged}
-
-If you use lint-staged, update your configuration to use Vite+ commands:
-
-**Before:**
-
-```json
-{
-  "*.{js,ts,tsx}": ["oxlint --fix", "oxfmt --write"]
-}
-```
-
-**After:**
-
-```json
-{
-  "*.{js,ts,tsx}": ["vp check --fix"]
-}
-```
-
-::: warning
-The automatic migration only supports JSON format lint-staged configurations (`.lintstagedrc.json` or `.lintstagedrc`). If you use other formats like `.lintstagedrc.yaml`, `.lintstagedrc.js`, or `lint-staged.config.mjs`, you'll need to update them manually.
-:::
-
-## Post-Migration Steps
-
-After migration completes:
-
-1. **Verify the build**:
-
-   ```bash
-   vp run build
-   ```
-
-   ::: tip
-   `vp run` automatically installs dependencies if needed, so you don't need to run `pnpm install` / `npm install` / `yarn install` manually.
-   :::
-
-2. **Run tests**:
-
-   ```bash
-   vp test
-   ```
-
-3. **Check linting**:
-
-   ```bash
-   vp lint
-   ```
-
-4. **Review `vite.config.ts`**: Ensure all merged configurations are correct.
-
-## Troubleshooting
-
-### Version Check Failed
-
-If you see an error like:
-
-```
-❌ vite@7.x.x is not supported by auto migration
-Please upgrade vite to version >=8.0.0 first
-```
-
-You need to upgrade to Vite 8 first. See the [Vite Migration Guide](https://main.vite.dev/guide/migration.html).
-
-Similarly for Vitest:
-
-```
-❌ vitest@3.x.x is not supported by auto migration
-Please upgrade vitest to version >=4.0.0 first
-```
-
-Upgrade to Vitest 4 first. See the [Vitest Migration Guide](https://vitest.dev/guide/migration.html).
-
-### Configuration Merge Failed
-
-If the automatic configuration merge fails:
-
-```
-❌ Failed to merge .oxlintrc into vite.config.ts
-Please complete the merge manually
-```
-
-You'll need to manually add the configuration to your `vite.config.ts`. See the [Configuration Guide](/config/) for the full configuration reference.
-
-### Import Rewrite Issues
-
-If you have complex import patterns that weren't automatically updated, search for and replace:
-
-- `from 'vite'` → `from 'vite-plus'`
-- `from 'vitest/config'` → `from 'vite-plus'`
-- `from 'vitest'` → `from 'vite-plus/test'`
-
-## What's Not Migrated
-
-The migration command does **not** handle:
-
-- **ESLint → oxlint**: These are different tools, not version upgrades
-- **Prettier → oxfmt**: These are different tools, not version upgrades
-- **Package scripts → vite-task.json**: Task configuration is a separate feature
-- **TypeScript configuration changes**
-- **Build tool migrations** (webpack/rollup → vite)
-
-For these scenarios, refer to the relevant documentation sections.
diff --git a/docs/vite/guide/monorepo.md b/docs/vite/guide/monorepo.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/vite/guide/task/caching.md b/docs/vite/guide/task/caching.md
deleted file mode 100644
index 3f4d698ddc..0000000000
--- a/docs/vite/guide/task/caching.md
+++ /dev/null
@@ -1,115 +0,0 @@
-# Caching
-
-## How It Works {#how-caching-works}
-
-When a task runs successfully (exit code 0), its terminal output (stdout/stderr) is saved. On the next run, the task runner checks if anything changed:
-
-1. **Arguments** — did the [additional arguments](./cli#additional-arguments) passed to the task change?
-2. **Environment variables** — did any [fingerprinted env vars](./config#envs) change?
-3. **Input files** — did any file that the command reads change?
-
-If everything matches, the cached output is replayed instantly — the command never actually runs.
-
-::: info
-Currently, only terminal output is cached and replayed. Output files (e.g., `dist/`) are not cached — if you delete them, use `--no-cache` to force a re-run. Output file caching is planned for a future release.
-:::
-
-When a cache miss occurs, the task runner tells you exactly why:
-
-```
-$ vp lint ✗ cache miss: 'src/utils.ts' modified, executing
-$ vp build ✗ cache miss: envs changed, executing
-$ vp test ✗ cache miss: args changed, executing
-```
-
-## When Is Caching Enabled? {#when-is-caching-enabled}
-
-A command run by `vp run` is either a **task** (has an entry in `vite.config.ts`) or a **script** (only exists in `package.json` with no corresponding task entry). By default, **tasks are cached and scripts are not.** Three layers control whether caching is on:
-
-### 1. Per-task `cache: false` (highest priority, tasks only)
-
-A task can set [`cache: false`](./config#cache) to opt out. This cannot be overridden by `--cache` or `run.cache` — if a task says no caching, it means no caching.
-
-### 2. CLI flags
-
-`--no-cache` disables caching for everything. `--cache` enables caching for both tasks and scripts — equivalent to setting [`run.cache: true`](./config#run-cache) for that invocation.
-
-### 3. Workspace config
-
-The [`run.cache`](./config#run-cache) option in your root `vite.config.ts` controls the default for each category:
-
-| Setting         | Default | Effect                                |
-| --------------- | ------- | ------------------------------------- |
-| `cache.tasks`   | `true`  | Cache commands that have a task entry |
-| `cache.scripts` | `false` | Cache plain `package.json` scripts    |
-
-Use `--cache` to quickly enable script caching, or set `run.cache.scripts: true` in config to enable it permanently.
-
-## Automatic File Tracking {#automatic-file-tracking}
-
-By default, the task runner tracks which files each command reads during execution. When `vp build` runs, it records which files the process opens — your `.ts` source files, `vite.config.ts`, `package.json`, etc. — and records their content hashes. On the next run, it re-checks those hashes to determine if anything changed.
-
-This means caching works out of the box for most commands without any configuration. The tracker also records:
-
-- **File non-existence** — if a command probes for a file that doesn't exist (e.g., `utils.ts` during module resolution), creating that file later correctly invalidates the cache.
-- **Directory listings** — if a command scans a directory (e.g., a test runner looking for `*.test.ts`), adding or removing files in that directory invalidates the cache.
-
-### Over-fingerprinting {#over-fingerprinting}
-
-Automatic tracking can sometimes include more files than necessary, causing unnecessary cache misses:
-
-- **Tool cache files** — some tools maintain their own cache (e.g., TypeScript's `.tsbuildinfo`, Cargo's `target/`). These files may change between runs even when your source code hasn't, causing unnecessary cache invalidation.
-- **Directory listings** — when a command scans a directory (e.g., globbing for `**/*.js`), the task runner sees the directory read but not the glob pattern. Any file added or removed in that directory — even unrelated ones — invalidates the cache.
-
-Use the [`inputs`](./config#inputs) option to exclude noisy files or replace automatic tracking with explicit file patterns:
-
-```ts
-tasks: {
-  build: {
-    command: 'tsc',
-    inputs: [{ auto: true }, '!**/*.tsbuildinfo'],
-  },
-}
-```
-
-## Environment Variables {#environment-variables}
-
-By default, tasks run in a clean environment — only a small set of common variables (like `PATH`, `HOME`, `CI`) are passed through. Other environment variables are neither visible to the task nor included in the cache fingerprint.
-
-To make a variable affect caching, add it to [`envs`](./config#envs). Changing its value invalidates the cache:
-
-```ts
-tasks: {
-  build: {
-    command: 'webpack --mode production',
-    envs: ['NODE_ENV'],
-  },
-}
-```
-
-To pass a variable to the task **without** affecting the cache, use [`passThroughEnvs`](./config#pass-through-envs). This is useful for variables like `CI` or `GITHUB_ACTIONS` that should be available but shouldn't trigger a rebuild when they change.
-
-See the [config reference](./config#envs) for details on wildcard patterns and the full list of automatically passed-through variables.
-
-## Cache Sharing {#cache-sharing}
-
-The cache is content-based — if two tasks run the same command with the same inputs, they share the cache entry. This happens naturally when multiple tasks include a common step, either as standalone tasks or as parts of [compound commands](./running-tasks#compound-commands):
-
-```json [package.json]
-{
-  "scripts": {
-    "check": "vp lint && vp build",
-    "release": "vp lint && deploy-script"
-  }
-}
-```
-
-With caching enabled (e.g. `--cache` or [`run.cache.scripts: true`](./config#run-cache)), running `check` first means the `vp lint` step in `release` is an instant cache hit, since both run the same command against the same files.
-
-## Clearing the Cache {#clearing-the-cache}
-
-```bash
-vp cache clean
-```
-
-This deletes the entire cache directory. Tasks will run fresh on the next invocation.
diff --git a/docs/vite/guide/task/cli.md b/docs/vite/guide/task/cli.md
deleted file mode 100644
index 613db2eda7..0000000000
--- a/docs/vite/guide/task/cli.md
+++ /dev/null
@@ -1,73 +0,0 @@
-# CLI Reference
-
-## `vp run` {#vp-run}
-
-Run tasks defined in `vite.config.ts` or `package.json` scripts.
-
-```bash
-vp run [options] [task] [additional-args]
-```
-
-If `task` is omitted, an interactive selector is shown:
-
-```
-Select a task (↑/↓, Enter to run, Esc to clear):
-
-  › build: vp build
-    lint: vp lint
-```
-
-### Task Argument {#task-argument}
-
-The `[task]` argument can be:
-
-- `build` — runs the `build` task in the current package
-- `@my/app#build` — runs the `build` task in a specific package
-
-### Options {#options}
-
-| Flag                  | Short | Description                                                |
-| --------------------- | ----- | ---------------------------------------------------------- |
-| `--recursive`         | `-r`  | Run in all workspace packages, in topological order        |
-| `--transitive`        | `-t`  | Run in the current package and its transitive dependencies |
-| `--workspace-root`    | `-w`  | Run in the workspace root package                          |
-| `--filter <pattern>`  | `-F`  | Select packages by name, directory, or glob (repeatable)   |
-| `--cache`             | —     | Enable caching for all tasks and scripts                   |
-| `--no-cache`          | —     | Disable caching entirely                                   |
-| `--ignore-depends-on` | —     | Skip explicit `dependsOn` dependencies                     |
-| `--verbose`           | `-v`  | Show detailed execution summary                            |
-| `--last-details`      | —     | Display the summary from the last run                      |
-
-### Additional Arguments {#additional-arguments}
-
-Arguments after the task name are passed through to the task command:
-
-```bash
-vp run test --reporter verbose
-```
-
-### Filter Patterns {#filter-patterns}
-
-| Pattern            | Description                                |
-| ------------------ | ------------------------------------------ |
-| `@my/app`          | Exact package name                         |
-| `@my/*`            | Glob matching                              |
-| `./packages/app`   | By directory                               |
-| `{./packages/app}` | By directory (braced form)                 |
-| `@my/app...`       | Package and its dependencies               |
-| `...@my/core`      | Package and its dependents                 |
-| `@my/app^...`      | Dependencies only (exclude package itself) |
-| `...^@my/core`     | Dependents only (exclude package itself)   |
-| `!@my/utils`       | Exclude a package                          |
-
-Multiple `--filter` flags are combined as a union. Exclusion filters (`!`) are applied after all inclusions.
-
-## `vp cache clean` {#vp-cache-clean}
-
-Delete all cached task results:
-
-```bash
-vp cache clean
-```
-
-Tasks will run fresh on the next invocation.
diff --git a/docs/vite/guide/task/getting-started.md b/docs/vite/guide/task/getting-started.md
deleted file mode 100644
index 53de9ee2e7..0000000000
--- a/docs/vite/guide/task/getting-started.md
+++ /dev/null
@@ -1,141 +0,0 @@
-# Getting Started
-
-## Overview
-
-`vp run` works like `pnpm run` — it runs the scripts in your `package.json` — but adds caching, dependency ordering, and monorepo-aware execution on top. It works in both single-package projects and monorepos.
-
-You can add task definitions in `vite.config.ts` when you need more control over dependencies and caching.
-
-## Running Scripts
-
-If your project already has scripts in `package.json`, you can run them with `vp run` right away — no configuration needed:
-
-```json [package.json]
-{
-  "scripts": {
-    "build": "vp build",
-    "test": "vp test"
-  }
-}
-```
-
-```bash
-vp run build
-```
-
-```
-$ vp build
-vite v8.0.0 building for production...
-✓ 4 modules transformed.
-dist/index.html                0.12 kB │ gzip: 0.12 kB
-dist/assets/index-FvSqcG4U.js  0.69 kB │ gzip: 0.39 kB
-
-✓ built in 28ms
-```
-
-## Caching
-
-Plain `package.json` scripts are not cached by default. Pass `--cache` to try it out:
-
-```bash
-vp run --cache build
-```
-
-```
-$ vp build
-✓ built in 28ms
-```
-
-Run it again — the output is replayed instantly from cache:
-
-```
-$ vp build ✓ cache hit, replaying
-✓ built in 28ms
-
----
-[vp run] cache hit, 468ms saved.
-```
-
-Edit a source file and run again — the task runner detects the change and re-runs:
-
-```
-$ vp build ✗ cache miss: 'src/index.ts' modified, executing
-```
-
-The task runner automatically tracks which files your command reads. No configuration needed.
-
-The `--cache` flag is a quick way to try caching, but the default behavior may not suit every task — you may need to control which files or environment variables affect the cache. To configure caching properly and enable it permanently, define the task in `vite.config.ts`. See [Caching](./caching) for how it works and [Config Reference](./config) for all task options.
-
-## Task Definitions {#task-definitions}
-
-Task definitions in `vite.config.ts` enable caching by default and give you more control — dependencies, environment variables, and custom inputs:
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  run: {
-    tasks: {
-      build: {
-        // Uses the "build" script from package.json
-        dependsOn: ['lint'],
-        envs: ['NODE_ENV'],
-      },
-      deploy: {
-        command: 'deploy-script --prod',
-        cache: false,
-        dependsOn: ['build', 'test'],
-      },
-    },
-  },
-});
-```
-
-A task definition can either reference a `package.json` script (by omitting `command`) or specify its own command. You cannot define a command in both places.
-
-::: info
-Tasks defined in `vite.config.ts` are cached by default. Plain `package.json` scripts (without a matching task entry) are **not** cached by default. See [When Is Caching Enabled?](./caching#when-is-caching-enabled) for details.
-:::
-
-See [Config Reference](./config) for all available task options.
-
-## Task Dependencies
-
-Use [`dependsOn`](./config#depends-on) to ensure tasks run in the right order. Running `vp run deploy` with the config above runs `build` and `test` first:
-
-```
-                ┌─────────┐   ┌────────┐
-                │  build  │   │  test  │
-                └────┬────┘   └───┬────┘
-                     │            │
-                     └─────┬──────┘
-                           │
-                     ┌─────▼─────┐
-                     │  deploy   │
-                     └───────────┘
-```
-
-Dependencies can reference tasks in other packages using the `package#task` format:
-
-```ts
-dependsOn: ['@my/core#build', '@my/utils#lint'];
-```
-
-## Running Across Packages
-
-In a monorepo, use `-r` (recursive) to run a task across all packages:
-
-```bash
-vp run -r build
-```
-
-The task runner automatically orders packages by their `package.json` dependency graph — if `@my/app` depends on `@my/utils` which depends on `@my/core`, they build in that order. Each package's result is cached independently.
-
-See [Running Tasks](./running-tasks) for package selection with `--filter`, `--transitive`, and other options.
-
-## What's Next?
-
-- [Running Tasks](./running-tasks) — package selection, compound commands, and concurrency
-- [Caching](./caching) — how caching works, file tracking, and cache sharing
-- [CLI Reference](./cli) — all flags and options
-- [Config Reference](./config) — all task configuration options
diff --git a/docs/vite/guide/task/running-tasks.md b/docs/vite/guide/task/running-tasks.md
deleted file mode 100644
index 4645453010..0000000000
--- a/docs/vite/guide/task/running-tasks.md
+++ /dev/null
@@ -1,181 +0,0 @@
-# Running Tasks
-
-## Package Selection {#package-selection}
-
-With no flags, `vp run` runs the task in the package containing your current directory:
-
-```bash
-cd packages/app
-vp run build        # runs build in @my/app only
-```
-
-Use `package#task` to target a specific package from anywhere:
-
-```bash
-vp run @my/app#build
-```
-
-### Recursive (`-r`) {#recursive}
-
-Run the task across **all** packages in the workspace:
-
-```bash
-vp run -r build     # builds every package, dependencies first
-```
-
-### Transitive (`-t`) {#transitive}
-
-Run the task in a package **and all its dependencies**:
-
-```bash
-vp run -t @my/app#build
-```
-
-If `@my/app` depends on `@my/utils` which depends on `@my/core`, this builds all three in dependency order. You can also use `--filter "@my/app..."` for the same result.
-
-### Filter (`--filter`) {#filter}
-
-Select packages by name, directory, or glob pattern. The syntax is compatible with pnpm's `--filter`:
-
-```bash
-# By name
-vp run --filter @my/app build
-
-# By glob
-vp run --filter "@my/*" build
-
-# By directory
-vp run --filter ./packages/app build
-
-# With dependencies
-vp run --filter "@my/app..." build    # app + all its dependencies
-
-# With dependents
-vp run --filter "...@my/core" build   # core + everything that depends on it
-
-# Exclude packages
-vp run --filter "@my/*" --filter "!@my/utils" build
-```
-
-Multiple `--filter` flags produce a union of the selected packages.
-
-### Workspace Root (`-w`) {#workspace-root}
-
-Explicitly select the workspace root package:
-
-```bash
-vp run -w build
-```
-
-## Compound Commands {#compound-commands}
-
-Commands joined with `&&` are split into independent sub-tasks, each cached separately when [caching is enabled](./caching#when-is-caching-enabled). This applies to both `vite.config.ts` tasks and `package.json` scripts, where compound commands are common:
-
-```json [package.json]
-{
-  "scripts": {
-    "check": "vp lint && vp build"
-  }
-}
-```
-
-```
-$ vp lint
-Found 0 warnings and 0 errors.
-
-$ vp build
-✓ built in 28ms
-
----
-[vp run] 0/2 cache hit (0%).
-```
-
-Each sub-task has its own cache entry. On the next run, if only `.ts` files changed but lint passes, only `vp build` re-runs:
-
-```
-$ vp lint ✓ cache hit, replaying
-$ vp build ✗ cache miss: 'src/index.ts' modified, executing
-✓ built in 30ms
-
----
-[vp run] 1/2 cache hit (50%), 120ms saved.
-```
-
-### Nested `vp run` {#nested-vp-run}
-
-When a command contains `vp run`, the task runner **inlines it as separate tasks** rather than spawning a nested process. Each sub-task is cached independently and output is shown flat:
-
-```json [package.json]
-{
-  "scripts": {
-    "ci": "vp run lint && vp run test && vp run build"
-  }
-}
-```
-
-Running `vp run ci` expands into three separate tasks, each with its own cache entry:
-
-```
-┌────────┐
-│  lint  │
-└───┬────┘
-    │
-┌───▼────┐
-│  test  │
-└───┬────┘
-    │
-┌───▼────┐
-│ build  │
-└────────┘
-```
-
-Flags work inside nested scripts too. For example, `vp run -r build` inside a script expands into individual build tasks for every package.
-
-::: details Self-Referencing Scripts
-A common monorepo pattern is a root script that runs a task recursively:
-
-```json [package.json (root)]
-{
-  "scripts": {
-    "build": "vp run -r build"
-  }
-}
-```
-
-This creates a potential recursion: root's `build` → `vp run -r build` → includes root's `build` → ... The task runner detects this and prunes the self-reference automatically, so other packages' builds run normally without infinite loops.
-:::
-
-## Execution Summary {#execution-summary}
-
-Use `-v` to see a detailed execution summary:
-
-```bash
-vp run -r -v build
-```
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-    Vite+ Task Runner • Execution Summary
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Statistics:   3 tasks • 3 cache hits • 0 cache misses
-Performance:  100% cache hit rate, 468ms saved in total
-
-Task Details:
-────────────────────────────────────────────────
-  [1] @my/core#build: ~/packages/core$ vp build ✓
-      → Cache hit - output replayed - 200ms saved
-  ·······················································
-  [2] @my/utils#build: ~/packages/utils$ vp build ✓
-      → Cache hit - output replayed - 150ms saved
-  ·······················································
-  [3] @my/app#build: ~/packages/app$ vp build ✓
-      → Cache hit - output replayed - 118ms saved
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-Use `--last-details` to recall the summary from the last run without re-executing:
-
-```bash
-vp run --last-details
-```
diff --git a/docs/vite/guide/tasks.md b/docs/vite/guide/tasks.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/docs/vite/guide/troubleshooting.md b/docs/vite/guide/troubleshooting.md
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/packages/cli/README.md b/packages/cli/README.md
index 21154edb72..dc54f7164d 100644
--- a/packages/cli/README.md
+++ b/packages/cli/README.md
@@ -29,7 +29,7 @@ Install Vite+ globally as `vp`:
 For Linux or macOS:
 
 ```bash
-curl -fsSL https://viteplus.dev/install.sh | bash
+curl -fsSL https://vite.plus | bash
 ```
 
 For Windows:
@@ -138,6 +138,7 @@ Vite+ automatically wraps your package manager (pnpm, npm, or Yarn) based on `pa
 #### Maintain
 
 - **upgrade** - Update `vp` itself to the latest version
+- **implode** - Remove `vp` and all related data
 
 ### Scaffolding your first Vite+ project
 
diff --git a/packages/cli/binding/src/cli.rs b/packages/cli/binding/src/cli.rs
index 7f2b694ebc..8059ccec06 100644
--- a/packages/cli/binding/src/cli.rs
+++ b/packages/cli/binding/src/cli.rs
@@ -4,8 +4,8 @@
 //! It handles argument parsing, command dispatching, and orchestration of the task execution.
 
 use std::{
-    borrow::Cow, env, ffi::OsStr, future::Future, io::IsTerminal, iter, pin::Pin, process::Stdio,
-    sync::Arc, time::Instant,
+    borrow::Cow, env, ffi::OsStr, future::Future, io::IsTerminal, iter, path::PathBuf, pin::Pin,
+    process::Stdio, sync::Arc, time::Instant,
 };
 
 use clap::{
@@ -15,6 +15,7 @@ use clap::{
 use owo_colors::OwoColorize;
 use rustc_hash::FxHashMap;
 use serde::{Deserialize, Serialize};
+use tokio::fs::write;
 use vite_error::Error;
 use vite_path::{AbsolutePath, AbsolutePathBuf};
 use vite_shared::{PrependOptions, output, prepend_to_path_env};
@@ -184,6 +185,8 @@ impl ResolvedSubcommand {
 pub struct SubcommandResolver {
     cli_options: Option<CliOptions>,
     workspace_path: Arc<AbsolutePath>,
+    /// Track temporary config files created during resolution for cleanup
+    temp_config_files: Vec<AbsolutePathBuf>,
 }
 
 impl std::fmt::Debug for SubcommandResolver {
@@ -191,13 +194,14 @@ impl std::fmt::Debug for SubcommandResolver {
         f.debug_struct("SubcommandResolver")
             .field("has_cli_options", &self.cli_options.is_some())
             .field("workspace_path", &self.workspace_path)
+            .field("temp_config_files_count", &self.temp_config_files.len())
             .finish()
     }
 }
 
 impl SubcommandResolver {
     pub fn new(workspace_path: Arc<AbsolutePath>) -> Self {
-        Self { cli_options: None, workspace_path }
+        Self { cli_options: None, workspace_path, temp_config_files: Vec::new() }
     }
 
     pub fn with_cli_options(mut self, cli_options: CliOptions) -> Self {
@@ -205,10 +209,143 @@ impl SubcommandResolver {
         self
     }
 
+    /// Clean up temporary config files created during resolution.
+    /// Should be called after command execution completes (success or failure).
+    pub async fn cleanup_temp_files(&mut self) {
+        for path in self.temp_config_files.drain(..) {
+            if let Err(e) = tokio::fs::remove_file(&path).await {
+                if e.kind() != std::io::ErrorKind::NotFound {
+                    tracing::warn!(
+                        "Failed to cleanup temp config file {}: {}",
+                        path.as_path().display(),
+                        e
+                    );
+                }
+            }
+        }
+    }
+
+    /// Write a temporary TS config file that re-exports a field from vite.config.
+    /// The temp file imports the vite config and re-exports the specified field,
+    /// so the tool (e.g. oxlint) picks it up via `-c <path>`.
+    /// The `config_file_path` must be an absolute path.
+    async fn write_temp_ts_config_import(
+        &mut self,
+        config_file_path: &str,
+        temp_filename: &str,
+        field_name: &str,
+        args: &mut Vec<String>,
+    ) -> anyhow::Result<()> {
+        let path = PathBuf::from(config_file_path);
+        if !path.is_absolute() {
+            anyhow::bail!("config_file_path must be an absolute path, got: {config_file_path}");
+        }
+
+        let config_basename = path
+            .file_name()
+            .and_then(|n| n.to_str())
+            .ok_or_else(|| {
+                anyhow::anyhow!("Failed to get file name of config file: {config_file_path}")
+            })?
+            .to_string();
+
+        let config_dir = AbsolutePathBuf::new(path)
+            .and_then(|p| p.parent().map(|p| p.to_absolute_path_buf()))
+            .ok_or_else(|| {
+                anyhow::anyhow!("Failed to get parent directory of config file: {config_file_path}")
+            })?;
+
+        let config_path = config_dir.join(temp_filename);
+        let content = format!(
+            "import {{ defineConfig }} from 'vite-plus/lint';\nimport viteConfig from './{config_basename}';\nexport default defineConfig(viteConfig.{field_name} as any);\n"
+        );
+        write(&config_path, content).await?;
+
+        self.temp_config_files.push(config_path.clone());
+
+        let config_path_str = config_path
+            .as_path()
+            .to_str()
+            .ok_or_else(|| anyhow::anyhow!("config path is not valid UTF-8"))?;
+        args.insert(0, config_path_str.to_string());
+        args.insert(0, "-c".to_string());
+        // Prevent oxlint from linting the temp config file itself
+        args.push("--ignore-pattern".to_string());
+        args.push(temp_filename.to_string());
+        Ok(())
+    }
+
+    /// Write a temporary JSON config file and prepend `-c <path>` to args.
+    /// The file will be tracked for cleanup after command execution.
+    /// The `config_file_path` must be an absolute path.
+    async fn write_temp_json_config_file(
+        &mut self,
+        config: &serde_json::Value,
+        config_file_path: &str,
+        temp_filename: &str,
+        args: &mut Vec<String>,
+    ) -> anyhow::Result<()> {
+        let mut config = config.clone();
+
+        // Add temp file to ignorePatterns to prevent self-checking
+        if let Some(obj) = config.as_object_mut() {
+            if let Some(patterns) = obj.get_mut("ignorePatterns") {
+                if let Some(array) = patterns.as_array_mut() {
+                    array.push(serde_json::json!(temp_filename));
+                }
+            } else {
+                obj.insert("ignorePatterns".to_string(), serde_json::json!([temp_filename]));
+            }
+        }
+
+        let path = PathBuf::from(config_file_path);
+        if !path.is_absolute() {
+            anyhow::bail!("config_file_path must be an absolute path, got: {config_file_path}");
+        }
+
+        let config_dir = AbsolutePathBuf::new(path)
+            .and_then(|p| p.parent().map(|p| p.to_absolute_path_buf()))
+            .ok_or_else(|| {
+                anyhow::anyhow!("Failed to get parent directory of config file: {config_file_path}")
+            })?;
+
+        let config_path = config_dir.join(temp_filename);
+        write(&config_path, serde_json::to_string(&config)?).await?;
+
+        self.temp_config_files.push(config_path.clone());
+
+        let config_path_str = config_path
+            .as_path()
+            .to_str()
+            .ok_or_else(|| anyhow::anyhow!("config path is not valid UTF-8"))?;
+        args.insert(0, config_path_str.to_string());
+        args.insert(0, "-c".to_string());
+        Ok(())
+    }
+
+    async fn resolve_universal_vite_config(&self) -> anyhow::Result<ResolvedUniversalViteConfig> {
+        let cli_options = self
+            .cli_options
+            .as_ref()
+            .ok_or_else(|| anyhow::anyhow!("CLI options required for vite config resolution"))?;
+        let workspace_path_str = self
+            .workspace_path
+            .as_path()
+            .to_str()
+            .ok_or_else(|| anyhow::anyhow!("workspace path is not valid UTF-8"))?;
+        let vite_config_json =
+            (cli_options.resolve_universal_vite_config)(workspace_path_str.to_string()).await?;
+
+        Ok(serde_json::from_str(&vite_config_json).inspect_err(|_| {
+            tracing::error!("Failed to parse vite config: {vite_config_json}");
+        })?)
+    }
+
     /// Resolve a synthesizable subcommand to a concrete program, args, cache config, and envs.
     async fn resolve(
         &mut self,
         subcommand: SynthesizableSubcommand,
+        resolved_vite_config: Option<&ResolvedUniversalViteConfig>,
         envs: &Arc<FxHashMap<Arc<OsStr>, Arc<OsStr>>>,
         cwd: &Arc<AbsolutePath>,
     ) -> anyhow::Result<ResolvedSubcommand> {
@@ -223,25 +360,24 @@ impl SubcommandResolver {
                 let js_path_str = js_path
                     .to_str()
                     .ok_or_else(|| anyhow::anyhow!("lint JS path is not valid UTF-8"))?;
-
-                let workspace_path_str = self
-                    .workspace_path
-                    .as_path()
-                    .to_str()
-                    .ok_or_else(|| anyhow::anyhow!("workspace path is not valid UTF-8"))?;
-                let vite_config_json =
-                    (cli_options.resolve_universal_vite_config)(workspace_path_str.to_string())
-                        .await?;
-                let resolved_vite_config: ResolvedUniversalViteConfig =
-                    serde_json::from_str(&vite_config_json).inspect_err(|_| {
-                        tracing::error!("Failed to parse vite config: {vite_config_json}");
-                    })?;
+                let owned_resolved_vite_config;
+                let resolved_vite_config = if let Some(config) = resolved_vite_config {
+                    config
+                } else {
+                    owned_resolved_vite_config = self.resolve_universal_vite_config().await?;
+                    &owned_resolved_vite_config
+                };
 
                 if let (Some(_), Some(config_file)) =
                     (&resolved_vite_config.lint, &resolved_vite_config.config_file)
                 {
-                    args.insert(0, "-c".to_string());
-                    args.insert(1, config_file.clone());
+                    self.write_temp_ts_config_import(
+                        config_file,
+                        ".vite-plus-lint.tmp.mts",
+                        "lint",
+                        &mut args,
+                    )
+                    .await?;
                 }
 
                 Ok(ResolvedSubcommand {
@@ -268,25 +404,24 @@ impl SubcommandResolver {
                 let js_path_str = js_path
                     .to_str()
                     .ok_or_else(|| anyhow::anyhow!("fmt JS path is not valid UTF-8"))?;
+                let owned_resolved_vite_config;
+                let resolved_vite_config = if let Some(config) = resolved_vite_config {
+                    config
+                } else {
+                    owned_resolved_vite_config = self.resolve_universal_vite_config().await?;
+                    &owned_resolved_vite_config
+                };
 
-                let workspace_path_str = self
-                    .workspace_path
-                    .as_path()
-                    .to_str()
-                    .ok_or_else(|| anyhow::anyhow!("workspace path is not valid UTF-8"))?;
-                let vite_config_json =
-                    (cli_options.resolve_universal_vite_config)(workspace_path_str.to_string())
-                        .await?;
-                let resolved_vite_config: ResolvedUniversalViteConfig =
-                    serde_json::from_str(&vite_config_json).inspect_err(|_| {
-                        tracing::error!("Failed to parse vite config: {vite_config_json}");
-                    })?;
-
-                if let (Some(_), Some(config_file)) =
+                if let (Some(fmt_config), Some(config_file)) =
                     (&resolved_vite_config.fmt, &resolved_vite_config.config_file)
                 {
-                    args.insert(0, "-c".to_string());
-                    args.insert(1, config_file.clone());
+                    self.write_temp_json_config_file(
+                        fmt_config,
+                        config_file,
+                        ".vite-plus-fmt.tmp.json",
+                        &mut args,
+                    )
+                    .await?;
                 }
 
                 Ok(ResolvedSubcommand {
@@ -521,6 +656,10 @@ impl VitePlusCommandHandler {
     pub fn new(resolver: SubcommandResolver) -> Self {
         Self { resolver }
     }
+
+    pub async fn cleanup_temp_files(&mut self) {
+        self.resolver.cleanup_temp_files().await;
+    }
 }
 
 #[async_trait::async_trait(?Send)]
@@ -558,7 +697,8 @@ impl CommandHandler for VitePlusCommandHandler {
                 ))
             }
             CLIArgs::Synthesizable(subcmd) => {
-                let resolved = self.resolver.resolve(subcmd, &command.envs, &command.cwd).await?;
+                let resolved =
+                    self.resolver.resolve(subcmd, None, &command.envs, &command.cwd).await?;
                 Ok(HandledCommand::Synthesized(resolved.into_synthetic_plan_request()))
             }
             CLIArgs::ViteTask(cmd) => Ok(HandledCommand::ViteTaskCommand(cmd)),
@@ -618,12 +758,15 @@ impl UserConfigLoader for VitePlusConfigLoader {
 async fn resolve_and_build_command(
     resolver: &mut SubcommandResolver,
     subcommand: SynthesizableSubcommand,
+    resolved_vite_config: Option<&ResolvedUniversalViteConfig>,
     envs: &Arc<FxHashMap<Arc<OsStr>, Arc<OsStr>>>,
     cwd: &AbsolutePathBuf,
     cwd_arc: &Arc<AbsolutePath>,
 ) -> Result<tokio::process::Command, Error> {
-    let resolved =
-        resolver.resolve(subcommand, envs, cwd_arc).await.map_err(|e| Error::Anyhow(e))?;
+    let resolved = resolver
+        .resolve(subcommand, resolved_vite_config, envs, cwd_arc)
+        .await
+        .map_err(|e| Error::Anyhow(e))?;
 
     // Resolve the program path using `which` to handle Windows .cmd/.bat files (PATHEXT)
     let program_path = {
@@ -653,11 +796,14 @@ async fn resolve_and_build_command(
 async fn resolve_and_execute(
     resolver: &mut SubcommandResolver,
     subcommand: SynthesizableSubcommand,
+    resolved_vite_config: Option<&ResolvedUniversalViteConfig>,
     envs: &Arc<FxHashMap<Arc<OsStr>, Arc<OsStr>>>,
     cwd: &AbsolutePathBuf,
     cwd_arc: &Arc<AbsolutePath>,
 ) -> Result<ExitStatus, Error> {
-    let mut cmd = resolve_and_build_command(resolver, subcommand, envs, cwd, cwd_arc).await?;
+    let mut cmd =
+        resolve_and_build_command(resolver, subcommand, resolved_vite_config, envs, cwd, cwd_arc)
+            .await?;
     let mut child = cmd.spawn().map_err(|e| Error::Anyhow(e.into()))?;
     let status = child.wait().await.map_err(|e| Error::Anyhow(e.into()))?;
     Ok(ExitStatus(status.code().unwrap_or(1) as u8))
@@ -668,12 +814,15 @@ async fn resolve_and_execute(
 async fn resolve_and_execute_with_stdout_filter(
     resolver: &mut SubcommandResolver,
     subcommand: SynthesizableSubcommand,
+    resolved_vite_config: Option<&ResolvedUniversalViteConfig>,
     envs: &Arc<FxHashMap<Arc<OsStr>, Arc<OsStr>>>,
     cwd: &AbsolutePathBuf,
     cwd_arc: &Arc<AbsolutePath>,
     filter: impl Fn(&str) -> Cow<'_, str>,
 ) -> Result<ExitStatus, Error> {
-    let mut cmd = resolve_and_build_command(resolver, subcommand, envs, cwd, cwd_arc).await?;
+    let mut cmd =
+        resolve_and_build_command(resolver, subcommand, resolved_vite_config, envs, cwd, cwd_arc)
+            .await?;
     cmd.stdout(Stdio::piped());
 
     let child = cmd.spawn().map_err(|e| Error::Anyhow(e.into()))?;
@@ -696,12 +845,15 @@ struct CapturedCommandOutput {
 async fn resolve_and_capture_output(
     resolver: &mut SubcommandResolver,
     subcommand: SynthesizableSubcommand,
+    resolved_vite_config: Option<&ResolvedUniversalViteConfig>,
     envs: &Arc<FxHashMap<Arc<OsStr>, Arc<OsStr>>>,
     cwd: &AbsolutePathBuf,
     cwd_arc: &Arc<AbsolutePath>,
     force_color_if_terminal: bool,
 ) -> Result<CapturedCommandOutput, Error> {
-    let mut cmd = resolve_and_build_command(resolver, subcommand, envs, cwd, cwd_arc).await?;
+    let mut cmd =
+        resolve_and_build_command(resolver, subcommand, resolved_vite_config, envs, cwd, cwd_arc)
+            .await?;
     cmd.stdout(Stdio::piped());
     cmd.stderr(Stdio::piped());
     if force_color_if_terminal && std::io::stdout().is_terminal() {
@@ -750,6 +902,45 @@ struct LintFailure {
     diagnostics: String,
 }
 
+#[derive(Clone, Copy, Debug, Eq, PartialEq)]
+enum LintMessageKind {
+    LintOnly,
+    LintAndTypeCheck,
+}
+
+impl LintMessageKind {
+    fn from_lint_config(lint_config: Option<&serde_json::Value>) -> Self {
+        let type_check_enabled = lint_config
+            .and_then(|config| config.get("options"))
+            .and_then(|options| options.get("typeCheck"))
+            .and_then(serde_json::Value::as_bool)
+            .unwrap_or(false);
+
+        if type_check_enabled { Self::LintAndTypeCheck } else { Self::LintOnly }
+    }
+
+    fn success_label(self) -> &'static str {
+        match self {
+            Self::LintOnly => "Found no warnings or lint errors",
+            Self::LintAndTypeCheck => "Found no warnings, lint errors, or type errors",
+        }
+    }
+
+    fn warning_heading(self) -> &'static str {
+        match self {
+            Self::LintOnly => "Lint warnings found",
+            Self::LintAndTypeCheck => "Lint or type warnings found",
+        }
+    }
+
+    fn issue_heading(self) -> &'static str {
+        match self {
+            Self::LintOnly => "Lint issues found",
+            Self::LintAndTypeCheck => "Lint or type issues found",
+        }
+    }
+}
+
 fn parse_check_summary(line: &str) -> Option<CheckSummary> {
     let rest = line.strip_prefix("Finished in ")?;
     let (duration, rest) = rest.split_once(" on ")?;
@@ -921,6 +1112,7 @@ async fn execute_direct_subcommand(
                 print_summary_line(
                     "`vp check` did not run because both `--no-fmt` and `--no-lint` were set",
                 );
+                resolver.cleanup_temp_files().await;
                 return Ok(ExitStatus(1));
             }
 
@@ -928,6 +1120,7 @@ async fn execute_direct_subcommand(
             let has_paths = !paths.is_empty();
             let mut fmt_fix_started: Option<Instant> = None;
             let mut deferred_lint_pass: Option<(String, String)> = None;
+            let resolved_vite_config = resolver.resolve_universal_vite_config().await?;
 
             if !no_fmt {
                 let mut args = if fix { vec![] } else { vec!["--check".to_string()] };
@@ -942,6 +1135,7 @@ async fn execute_direct_subcommand(
                 let captured = resolve_and_capture_output(
                     &mut resolver,
                     SynthesizableSubcommand::Fmt { args },
+                    Some(&resolved_vite_config),
                     &envs,
                     cwd,
                     &cwd_arc,
@@ -997,11 +1191,14 @@ async fn execute_direct_subcommand(
                     );
                 }
                 if status != ExitStatus::SUCCESS {
+                    resolver.cleanup_temp_files().await;
                     return Ok(status);
                 }
             }
 
             if !no_lint {
+                let lint_message_kind =
+                    LintMessageKind::from_lint_config(resolved_vite_config.lint.as_ref());
                 let mut args = Vec::new();
                 if fix {
                     args.push("--fix".to_string());
@@ -1012,6 +1209,7 @@ async fn execute_direct_subcommand(
                 let captured = resolve_and_capture_output(
                     &mut resolver,
                     SynthesizableSubcommand::Lint { args },
+                    Some(&resolved_vite_config),
                     &envs,
                     cwd,
                     &cwd_arc,
@@ -1030,10 +1228,9 @@ async fn execute_direct_subcommand(
 
                 match analyze_lint_output(&combined_output) {
                     Some(Ok(success)) => {
-                        let issue_label = "Found no warnings, lint errors, or type errors";
-
                         let message = format!(
-                            "{issue_label} in {}",
+                            "{} in {}",
+                            lint_message_kind.success_label(),
                             format_count(success.summary.files, "file", "files"),
                         );
                         let detail = format!(
@@ -1049,9 +1246,9 @@ async fn execute_direct_subcommand(
                     }
                     Some(Err(failure)) => {
                         if failure.errors == 0 && failure.warnings > 0 {
-                            output::warn("Lint or type warnings found");
+                            output::warn(lint_message_kind.warning_heading());
                         } else {
-                            output::error("Lint or type issues found");
+                            output::error(lint_message_kind.issue_heading());
                         }
                         print_stdout_block(&failure.diagnostics);
                         print_summary_line(&format!(
@@ -1072,6 +1269,7 @@ async fn execute_direct_subcommand(
                     }
                 }
                 if status != ExitStatus::SUCCESS {
+                    resolver.cleanup_temp_files().await;
                     return Ok(status);
                 }
             }
@@ -1087,6 +1285,7 @@ async fn execute_direct_subcommand(
                 let captured = resolve_and_capture_output(
                     &mut resolver,
                     SynthesizableSubcommand::Fmt { args },
+                    Some(&resolved_vite_config),
                     &envs,
                     cwd,
                     &cwd_arc,
@@ -1107,6 +1306,7 @@ async fn execute_direct_subcommand(
                         print_stdout_block(&combined_output);
                     }
                     print_summary_line("Formatting failed after lint fixes were applied");
+                    resolver.cleanup_temp_files().await;
                     return Ok(status);
                 }
                 if let Some(started) = fmt_fix_started {
@@ -1127,6 +1327,7 @@ async fn execute_direct_subcommand(
                 resolve_and_execute_with_stdout_filter(
                     &mut resolver,
                     other,
+                    None,
                     &envs,
                     cwd,
                     &cwd_arc,
@@ -1134,11 +1335,13 @@ async fn execute_direct_subcommand(
                 )
                 .await?
             } else {
-                resolve_and_execute(&mut resolver, other, &envs, cwd, &cwd_arc).await?
+                resolve_and_execute(&mut resolver, other, None, &envs, cwd, &cwd_arc).await?
             }
         }
     };
 
+    resolver.cleanup_temp_files().await;
+
     Ok(status)
 }
 
@@ -1183,6 +1386,8 @@ async fn execute_vite_task_command(
     // Main execution (consumes session)
     let result = session.main(command).await.map_err(|e| Error::Anyhow(e));
 
+    command_handler.cleanup_temp_files().await;
+
     result
 }
 
@@ -1421,11 +1626,12 @@ mod tests {
     use std::path::PathBuf;
 
     use clap::Parser;
+    use serde_json::json;
     use vite_task::config::UserRunConfig;
 
     use super::{
-        CLIArgs, SynthesizableSubcommand, extract_unknown_argument, has_pass_as_value_suggestion,
-        should_prepend_vitest_run, should_suppress_subcommand_stdout,
+        CLIArgs, LintMessageKind, SynthesizableSubcommand, extract_unknown_argument,
+        has_pass_as_value_suggestion, should_prepend_vitest_run, should_suppress_subcommand_stdout,
     };
 
     #[test]
@@ -1534,6 +1740,30 @@ mod tests {
         assert!(!should_suppress_subcommand_stdout(&subcommand));
     }
 
+    #[test]
+    fn lint_message_kind_defaults_to_lint_only_without_typecheck() {
+        assert_eq!(LintMessageKind::from_lint_config(None), LintMessageKind::LintOnly);
+        assert_eq!(
+            LintMessageKind::from_lint_config(Some(&json!({ "options": {} }))),
+            LintMessageKind::LintOnly
+        );
+    }
+
+    #[test]
+    fn lint_message_kind_detects_typecheck_from_vite_config() {
+        let kind = LintMessageKind::from_lint_config(Some(&json!({
+            "options": {
+                "typeAware": true,
+                "typeCheck": true
+            }
+        })));
+
+        assert_eq!(kind, LintMessageKind::LintAndTypeCheck);
+        assert_eq!(kind.success_label(), "Found no warnings, lint errors, or type errors");
+        assert_eq!(kind.warning_heading(), "Lint or type warnings found");
+        assert_eq!(kind.issue_heading(), "Lint or type issues found");
+    }
+
     #[test]
     fn global_subcommands_produce_invalid_subcommand_error() {
         use clap::error::ErrorKind;
diff --git a/packages/cli/install.ps1 b/packages/cli/install.ps1
index 35a1159a8a..aaa5043e22 100644
--- a/packages/cli/install.ps1
+++ b/packages/cli/install.ps1
@@ -1,8 +1,8 @@
 # Vite+ CLI Installer for Windows
-# https://viteplus.dev/install.ps1
+# https://vite.plus/ps1
 #
 # Usage:
-#   irm https://viteplus.dev/install.ps1 | iex
+#   irm https://vite.plus/ps1 | iex
 #
 # Environment variables:
 #   VITE_PLUS_VERSION - Version to install (default: latest)
diff --git a/packages/cli/install.sh b/packages/cli/install.sh
index 26b27622e4..df817040e0 100644
--- a/packages/cli/install.sh
+++ b/packages/cli/install.sh
@@ -1,9 +1,9 @@
 #!/bin/bash
 # Vite+ CLI Installer
-# https://viteplus.dev/install.sh
+# https://vite.plus
 #
 # Usage:
-#   curl -fsSL https://viteplus.dev/install.sh | bash
+#   curl -fsSL https://vite.plus | bash
 #
 # Environment variables:
 #   VITE_PLUS_VERSION - Version to install (default: latest)
diff --git a/packages/cli/snap-tests-global/cli-helper-message/snap.txt b/packages/cli/snap-tests-global/cli-helper-message/snap.txt
index 93f0a5a250..da560c81fe 100644
--- a/packages/cli/snap-tests-global/cli-helper-message/snap.txt
+++ b/packages/cli/snap-tests-global/cli-helper-message/snap.txt
@@ -46,6 +46,8 @@ Maintain:
   upgrade  Update vp itself to the latest version
   implode  Remove vp and all related data
 
+Documentation: https://viteplus.dev/guide/
+
 Options:
   -V, --version  Print version
   -h, --help     Print help
@@ -104,6 +106,8 @@ Options:
   --node <NODE>         Node.js version to use for global installation (only with -g)
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp add -h # show add help message
 VITE+ - The Unified Toolchain for the Web
@@ -132,6 +136,8 @@ Options:
   --node <NODE>                       Node.js version to use for global installation (only with -g)
   -h, --help                          Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp remove -h # show remove help message
 VITE+ - The Unified Toolchain for the Web
@@ -155,6 +161,8 @@ Options:
   --dry-run             Preview what would be removed without actually removing (only with -g)
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp update -h # show update help message
 VITE+ - The Unified Toolchain for the Web
@@ -181,6 +189,8 @@ Options:
   --workspace           Only update if package exists in workspace (pnpm-specific)
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp link -h # show link help message
 VITE+ - The Unified Toolchain for the Web
@@ -196,6 +206,8 @@ Arguments:
 Options:
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp unlink -h # show unlink help message
 VITE+ - The Unified Toolchain for the Web
@@ -212,6 +224,8 @@ Options:
   -r, --recursive  Unlink in every workspace package
   -h, --help       Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp dedupe -h # show dedupe help message
 VITE+ - The Unified Toolchain for the Web
@@ -227,6 +241,8 @@ Options:
   --check     Check if deduplication would make changes
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp outdated -h # show outdated help message
 VITE+ - The Unified Toolchain for the Web
@@ -253,6 +269,8 @@ Options:
   -g, --global          Check globally installed packages
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp why -h # show why help message
 VITE+ - The Unified Toolchain for the Web
@@ -281,6 +299,8 @@ Options:
   --find-by <FINDER_NAME>  Use a finder function defined in .pnpmfile.cjs
   -h, --help               Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp info -h # show info help message
 VITE+ - The Unified Toolchain for the Web
@@ -298,6 +318,8 @@ Options:
   --json      Output in JSON format
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm -h # show pm help message
 VITE+ - The Unified Toolchain for the Web
@@ -330,6 +352,8 @@ Commands:
 Options:
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp env # show env help message
 VITE+ - The Unified Toolchain for the Web
@@ -389,6 +413,8 @@ Related Commands:
   vp update -g [package]        # Update global packages
   vp list -g [package]          # List global packages
 
+Documentation: https://viteplus.dev/guide/env
+
 
 > vp upgrade -h # show upgrade help message
 VITE+ - The Unified Toolchain for the Web
@@ -409,3 +435,5 @@ Options:
   --registry <REGISTRY>  Custom npm registry URL
   -h, --help             Print help
 
+Documentation: https://viteplus.dev/guide/upgrade
+
diff --git a/packages/cli/snap-tests-global/command-add-npm10/snap.txt b/packages/cli/snap-tests-global/command-add-npm10/snap.txt
index c4b7f790db..645d7b1d70 100644
--- a/packages/cli/snap-tests-global/command-add-npm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-add-npm10/snap.txt
@@ -25,6 +25,8 @@ Options:
   --node <NODE>                       Node.js version to use for global installation (only with -g)
   -h, --help                          Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp add testnpm2 -D -- --no-audit && cat package.json # should add package as dev dependencies
 
diff --git a/packages/cli/snap-tests-global/command-add-npm11/snap.txt b/packages/cli/snap-tests-global/command-add-npm11/snap.txt
index 2e22bff2ae..d08b0a1062 100644
--- a/packages/cli/snap-tests-global/command-add-npm11/snap.txt
+++ b/packages/cli/snap-tests-global/command-add-npm11/snap.txt
@@ -25,6 +25,8 @@ Options:
   --node <NODE>                       Node.js version to use for global installation (only with -g)
   -h, --help                          Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp add testnpm2 -D -- --no-audit && cat package.json # should add package as dev dependencies
 
diff --git a/packages/cli/snap-tests-global/command-add-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-add-pnpm10/snap.txt
index 929a077fdb..f3163aabca 100644
--- a/packages/cli/snap-tests-global/command-add-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-add-pnpm10/snap.txt
@@ -25,6 +25,8 @@ Options:
   --node <NODE>                       Node.js version to use for global installation (only with -g)
   -h, --help                          Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 [2]> vp add # should error because no packages specified
 error: the following required arguments were not provided:
diff --git a/packages/cli/snap-tests-global/command-add-pnpm9/snap.txt b/packages/cli/snap-tests-global/command-add-pnpm9/snap.txt
index b3e0894a3d..6b70cd3712 100644
--- a/packages/cli/snap-tests-global/command-add-pnpm9/snap.txt
+++ b/packages/cli/snap-tests-global/command-add-pnpm9/snap.txt
@@ -25,6 +25,8 @@ Options:
   --node <NODE>                       Node.js version to use for global installation (only with -g)
   -h, --help                          Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp add testnpm2 -D && cat package.json # should add package as dev dependencies
 Packages: +<variable>
diff --git a/packages/cli/snap-tests-global/command-add-yarn4/snap.txt b/packages/cli/snap-tests-global/command-add-yarn4/snap.txt
index 587599767f..12414733ed 100644
--- a/packages/cli/snap-tests-global/command-add-yarn4/snap.txt
+++ b/packages/cli/snap-tests-global/command-add-yarn4/snap.txt
@@ -25,6 +25,8 @@ Options:
   --node <NODE>                       Node.js version to use for global installation (only with -g)
   -h, --help                          Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp add testnpm2 -D && cat package.json # should add package as dev dependencies
 ➤ YN0000: · Yarn <semver>
diff --git a/packages/cli/snap-tests-global/command-cache-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-cache-pnpm10/snap.txt
index 98f7ec1a9b..2916822b7f 100644
--- a/packages/cli/snap-tests-global/command-cache-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-cache-pnpm10/snap.txt
@@ -12,6 +12,8 @@ Arguments:
 Options:
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm cache dir > /dev/null # should show cache directory (uses pnpm store path)
 > vp pm cache path > /dev/null # should show cache path (alias for dir, uses pnpm store path)
\ No newline at end of file
diff --git a/packages/cli/snap-tests-global/command-config-help/snap.txt b/packages/cli/snap-tests-global/command-config-help/snap.txt
index a242d4d33c..976ac97746 100644
--- a/packages/cli/snap-tests-global/command-config-help/snap.txt
+++ b/packages/cli/snap-tests-global/command-config-help/snap.txt
@@ -12,6 +12,8 @@ Options:
 Environment:
   VITE_GIT_HOOKS=0  Skip hook installation
 
+Documentation: https://viteplus.dev/guide/commit-hooks
+
 
 > vp config --help
 VITE+ - The Unified Toolchain for the Web
@@ -27,6 +29,8 @@ Options:
 Environment:
   VITE_GIT_HOOKS=0  Skip hook installation
 
+Documentation: https://viteplus.dev/guide/commit-hooks
+
 
 > vp help config
 VITE+ - The Unified Toolchain for the Web
@@ -42,3 +46,5 @@ Options:
 Environment:
   VITE_GIT_HOOKS=0  Skip hook installation
 
+Documentation: https://viteplus.dev/guide/commit-hooks
+
diff --git a/packages/cli/snap-tests-global/command-config-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-config-pnpm10/snap.txt
index df6af500e7..47cd0a482d 100644
--- a/packages/cli/snap-tests-global/command-config-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-config-pnpm10/snap.txt
@@ -14,6 +14,8 @@ Commands:
 Options:
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm config list --location project > /dev/null # should list all project configuration
 > vp pm config set vite-plus-pm-config-test-key test-value --location project # should set config value in project scope
diff --git a/packages/cli/snap-tests-global/command-create-help/snap.txt b/packages/cli/snap-tests-global/command-create-help/snap.txt
index cecbe04de9..27b686294a 100644
--- a/packages/cli/snap-tests-global/command-create-help/snap.txt
+++ b/packages/cli/snap-tests-global/command-create-help/snap.txt
@@ -49,6 +49,8 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+Documentation: https://viteplus.dev/guide/create
+
 
 > vp create --help
 VITE+ - The Unified Toolchain for the Web
@@ -101,6 +103,8 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+Documentation: https://viteplus.dev/guide/create
+
 
 > vp help create
 VITE+ - The Unified Toolchain for the Web
@@ -153,3 +157,5 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+Documentation: https://viteplus.dev/guide/create
+
diff --git a/packages/cli/snap-tests-global/command-dedupe-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-dedupe-pnpm10/snap.txt
index 97e21e492a..feefb9f931 100644
--- a/packages/cli/snap-tests-global/command-dedupe-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-dedupe-pnpm10/snap.txt
@@ -12,6 +12,8 @@ Options:
   --check     Check if deduplication would make changes
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp dedupe && cat package.json # should dedupe dependencies
 Already up to date
diff --git a/packages/cli/snap-tests-global/command-dlx-npm10/snap.txt b/packages/cli/snap-tests-global/command-dlx-npm10/snap.txt
index 1498a2984c..fc77dbfda3 100644
--- a/packages/cli/snap-tests-global/command-dlx-npm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-dlx-npm10/snap.txt
@@ -14,6 +14,8 @@ Options:
   -s, --silent          Suppress all output except the executed command's output
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/vpx
+
 
 > vp dlx -s cowsay hello # should run cowsay with npm exec
  _______
diff --git a/packages/cli/snap-tests-global/command-dlx-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-dlx-pnpm10/snap.txt
index dcfe74befc..7a3c824f90 100644
--- a/packages/cli/snap-tests-global/command-dlx-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-dlx-pnpm10/snap.txt
@@ -14,6 +14,8 @@ Options:
   -s, --silent          Suppress all output except the executed command's output
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/vpx
+
 
 > vp dlx -s cowsay hello # should run cowsay with pnpm dlx
  _______
diff --git a/packages/cli/snap-tests-global/command-dlx-yarn4/snap.txt b/packages/cli/snap-tests-global/command-dlx-yarn4/snap.txt
index 5dd79009f6..6fc59eea0b 100644
--- a/packages/cli/snap-tests-global/command-dlx-yarn4/snap.txt
+++ b/packages/cli/snap-tests-global/command-dlx-yarn4/snap.txt
@@ -14,6 +14,8 @@ Options:
   -s, --silent          Suppress all output except the executed command's output
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/vpx
+
 
 > vp dlx -s cowsay hello # should run cowsay with yarn dlx
  _______
diff --git a/packages/cli/snap-tests-global/command-env-use/snap.txt b/packages/cli/snap-tests-global/command-env-use/snap.txt
index 310422aea7..6816e87cc6 100644
--- a/packages/cli/snap-tests-global/command-env-use/snap.txt
+++ b/packages/cli/snap-tests-global/command-env-use/snap.txt
@@ -14,6 +14,8 @@ Options:
   --silent-if-unchanged  Suppress output if version is already active
   -h, --help             Print help
 
+Documentation: https://viteplus.dev/guide/env
+
 
 > vp env use 20.18.0 --no-install # should output export command to stdout
 export VITE_PLUS_NODE_VERSION=20.18.0
diff --git a/packages/cli/snap-tests-global/command-exec/snap.txt b/packages/cli/snap-tests-global/command-exec/snap.txt
index bba03404e8..3a7d4d1ffc 100644
--- a/packages/cli/snap-tests-global/command-exec/snap.txt
+++ b/packages/cli/snap-tests-global/command-exec/snap.txt
@@ -62,6 +62,8 @@ Examples:
   vp exec -r -- tsc --noEmit                         # Run in all workspace packages
   vp exec --filter 'app...' -- tsc                   # Run in filtered packages
 
+Documentation: https://viteplus.dev/guide/vpx
+
 
 [1]> vp exec # missing command should error
 VITE+ - The Unified Toolchain for the Web
diff --git a/packages/cli/snap-tests-global/command-link-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-link-pnpm10/snap.txt
index 062fc7e7c6..c74bb34ba6 100644
--- a/packages/cli/snap-tests-global/command-link-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-link-pnpm10/snap.txt
@@ -12,6 +12,8 @@ Arguments:
 Options:
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp install # install initial dependencies
 VITE+ - The Unified Toolchain for the Web
diff --git a/packages/cli/snap-tests-global/command-list-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-list-pnpm10/snap.txt
index e20a78aa5f..4d477c5443 100644
--- a/packages/cli/snap-tests-global/command-list-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-list-pnpm10/snap.txt
@@ -41,6 +41,8 @@ Options:
   -g, --global             List global packages
   -h, --help               Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm list # should list installed packages
 Legend: production dependency, optional only, dev only
diff --git a/packages/cli/snap-tests-global/command-outdated-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-outdated-pnpm10/snap.txt
index aa3e3ad7f9..61a44a15a0 100644
--- a/packages/cli/snap-tests-global/command-outdated-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-outdated-pnpm10/snap.txt
@@ -23,6 +23,8 @@ Options:
   -g, --global          Check globally installed packages
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp install # should install packages first
 VITE+ - The Unified Toolchain for the Web
diff --git a/packages/cli/snap-tests-global/command-owner-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-owner-pnpm10/snap.txt
index cd995e37ad..a8f452c954 100644
--- a/packages/cli/snap-tests-global/command-owner-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-owner-pnpm10/snap.txt
@@ -13,6 +13,8 @@ Commands:
 Options:
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm owner list testnpm2 # should list package owners (uses npm owner)
 fengmk2 <fengmk2@gmail.com>
diff --git a/packages/cli/snap-tests-global/command-pack-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-pack-pnpm10/snap.txt
index a619d11094..225738b7f6 100644
--- a/packages/cli/snap-tests-global/command-pack-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-pack-pnpm10/snap.txt
@@ -17,6 +17,8 @@ Options:
   --json                                 Output in JSON format
   -h, --help                             Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm pack && rm -rf *.tgz # should pack current package
 📦  command-pack-pnpm10@<semver>
diff --git a/packages/cli/snap-tests-global/command-prune-npm10/snap.txt b/packages/cli/snap-tests-global/command-prune-npm10/snap.txt
index 3e451c142f..e95cab24db 100644
--- a/packages/cli/snap-tests-global/command-prune-npm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-prune-npm10/snap.txt
@@ -19,6 +19,8 @@ Options:
   --no-optional  Remove optional dependencies
   -h, --help     Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm prune # should prune extraneous dependencies
 
diff --git a/packages/cli/snap-tests-global/command-prune-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-prune-pnpm10/snap.txt
index 7639857111..12908db3ff 100644
--- a/packages/cli/snap-tests-global/command-prune-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-prune-pnpm10/snap.txt
@@ -31,6 +31,8 @@ Options:
   --no-optional  Remove optional dependencies
   -h, --help     Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm prune && cat package.json # should prune extraneous dependencies
 Lockfile is up to date, resolution step is skipped
diff --git a/packages/cli/snap-tests-global/command-prune-yarn4/snap.txt b/packages/cli/snap-tests-global/command-prune-yarn4/snap.txt
index 41d91ca078..9fce3dc77e 100644
--- a/packages/cli/snap-tests-global/command-prune-yarn4/snap.txt
+++ b/packages/cli/snap-tests-global/command-prune-yarn4/snap.txt
@@ -13,6 +13,8 @@ Options:
   --no-optional  Remove optional dependencies
   -h, --help     Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm prune # should show warning that yarn does not support prune command
 warn: yarn does not have 'prune' command. yarn install will prune extraneous packages automatically.
diff --git a/packages/cli/snap-tests-global/command-publish-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-publish-pnpm10/snap.txt
index f2cf4a4fe5..7f1df06201 100644
--- a/packages/cli/snap-tests-global/command-publish-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-publish-pnpm10/snap.txt
@@ -23,6 +23,8 @@ Options:
   --filter <PATTERN>         Filter packages in monorepo
   -h, --help                 Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm publish --dry-run -- --loglevel error # should preview publish without actually publishing (uses pnpm publish --dry-run)
 + command-publish-pnpm10@<semver>
diff --git a/packages/cli/snap-tests-global/command-remove-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-remove-pnpm10/snap.txt
index 92983d30fc..88a595fba5 100644
--- a/packages/cli/snap-tests-global/command-remove-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-remove-pnpm10/snap.txt
@@ -20,6 +20,8 @@ Options:
   --dry-run             Preview what would be removed without actually removing (only with -g)
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 [2]> vp remove # should error because no packages specified
 error: the following required arguments were not provided:
diff --git a/packages/cli/snap-tests-global/command-staged-help/snap.txt b/packages/cli/snap-tests-global/command-staged-help/snap.txt
index 4a7732dacf..5f834be810 100644
--- a/packages/cli/snap-tests-global/command-staged-help/snap.txt
+++ b/packages/cli/snap-tests-global/command-staged-help/snap.txt
@@ -23,6 +23,8 @@ Options:
   -v, --verbose                      Show task output even when tasks succeed
   -h, --help                         Show this help message
 
+Documentation: https://viteplus.dev/guide/commit-hooks
+
 
 > vp staged --help
 VITE+ - The Unified Toolchain for the Web
@@ -49,6 +51,8 @@ Options:
   -v, --verbose                      Show task output even when tasks succeed
   -h, --help                         Show this help message
 
+Documentation: https://viteplus.dev/guide/commit-hooks
+
 
 > vp help staged
 VITE+ - The Unified Toolchain for the Web
@@ -75,3 +79,5 @@ Options:
   -v, --verbose                      Show task output even when tasks succeed
   -h, --help                         Show this help message
 
+Documentation: https://viteplus.dev/guide/commit-hooks
+
diff --git a/packages/cli/snap-tests-global/command-staged-no-config/snap.txt b/packages/cli/snap-tests-global/command-staged-no-config/snap.txt
index b194f24ce4..a09b1e6a12 100644
--- a/packages/cli/snap-tests-global/command-staged-no-config/snap.txt
+++ b/packages/cli/snap-tests-global/command-staged-no-config/snap.txt
@@ -1,5 +1,7 @@
 [1]> vp staged # should warn about missing staged config and exit with code 1
-No "staged" config found in vite.config.ts. Please add a staged config:
+VITE+ - The Unified Toolchain for the Web
+
+error: No "staged" config found in vite.config.ts. Please add a staged config:
 
   // vite.config.ts
   export default defineConfig({
diff --git a/packages/cli/snap-tests-global/command-unlink-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-unlink-pnpm10/snap.txt
index 403e2c630a..580763292a 100644
--- a/packages/cli/snap-tests-global/command-unlink-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-unlink-pnpm10/snap.txt
@@ -13,6 +13,8 @@ Options:
   -r, --recursive  Unlink in every workspace package
   -h, --help       Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > mkdir -p ../unlink-test-lib && echo '{"name": "unlink-test-lib", "version": "1.0.0"}' > ../unlink-test-lib/package.json # create test library
 > vp link ../unlink-test-lib && cat package.json # link the library first
diff --git a/packages/cli/snap-tests-global/command-update-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-update-pnpm10/snap.txt
index 772874b790..316e352d90 100644
--- a/packages/cli/snap-tests-global/command-update-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-update-pnpm10/snap.txt
@@ -23,6 +23,8 @@ Options:
   --workspace           Only update if package exists in workspace (pnpm-specific)
   -h, --help            Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp update testnpm2 && cat package.json # should update package within semver range
 Packages: +<variable>
diff --git a/packages/cli/snap-tests-global/command-view-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-view-pnpm10/snap.txt
index 8484881fc2..c63988e5d1 100644
--- a/packages/cli/snap-tests-global/command-view-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-view-pnpm10/snap.txt
@@ -14,6 +14,8 @@ Options:
   --json      Output in JSON format
   -h, --help  Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp pm view testnpm2 # should view lodash package information (uses npm view)
 
diff --git a/packages/cli/snap-tests-global/command-why-pnpm10/snap.txt b/packages/cli/snap-tests-global/command-why-pnpm10/snap.txt
index 3f80f0f525..35fc8747bc 100644
--- a/packages/cli/snap-tests-global/command-why-pnpm10/snap.txt
+++ b/packages/cli/snap-tests-global/command-why-pnpm10/snap.txt
@@ -25,6 +25,8 @@ Options:
   --find-by <FINDER_NAME>  Use a finder function defined in .pnpmfile.cjs
   -h, --help               Print help
 
+Documentation: https://viteplus.dev/guide/install
+
 
 > vp install # should install packages first
 VITE+ - The Unified Toolchain for the Web
diff --git a/packages/cli/snap-tests-global/global-cli-fallback/snap.txt b/packages/cli/snap-tests-global/global-cli-fallback/snap.txt
index 5f5b8a73a4..9a753fb599 100644
--- a/packages/cli/snap-tests-global/global-cli-fallback/snap.txt
+++ b/packages/cli/snap-tests-global/global-cli-fallback/snap.txt
@@ -24,6 +24,8 @@ Examples:
   vp build --watch
   vp build --sourcemap
 
+Documentation: https://viteplus.dev/guide/build
+
 
 > vp dev -h # should fall back to global vite-plus and show dev help
 VITE+ - The Unified Toolchain for the Web
@@ -51,6 +53,8 @@ Examples:
   vp dev --open
   vp dev --host localhost --port 5173
 
+Documentation: https://viteplus.dev/guide/dev
+
 
 > vp test -h # should fall back to global vite-plus and show test help
 VITE+ - The Unified Toolchain for the Web
@@ -83,3 +87,5 @@ Examples:
   vp test run src/foo.test.ts
   vp test watch --coverage
 
+Documentation: https://viteplus.dev/guide/test
+
diff --git a/packages/cli/snap-tests-global/migration-check/snap.txt b/packages/cli/snap-tests-global/migration-check/snap.txt
index 2faedae2f3..89ce2f9db6 100644
--- a/packages/cli/snap-tests-global/migration-check/snap.txt
+++ b/packages/cli/snap-tests-global/migration-check/snap.txt
@@ -28,3 +28,42 @@ Examples:
   # Non-interactive mode
   vp migrate --no-interactive
 
+Migration Prompt:
+  Give this to a coding agent when you want it to drive the migration:
+
+  Migrate this project to Vite+.
+  Vite+ replaces the current split tooling around runtime management, package
+  management, dev/build/test commands, linting, formatting, and packaging.
+  Run `vp help` and `vp help migrate` before making changes.
+  Use vp migrate --no-interactive in the workspace root.
+  Make sure the project is using Vite 8+ and Vitest 4.1+ before migrating.
+
+  After the migration:
+  - Confirm `vite` imports were rewritten to `vite-plus` where needed
+  - Confirm `vitest` imports were rewritten to `vite-plus/test` where needed
+  - Remove old `vite` and `vitest` dependencies only after those rewrites
+    are confirmed
+  - Move remaining tool-specific config into the appropriate blocks in
+    `vite.config.ts`
+
+  Command mapping:
+  - `vp run <script>` is the equivalent of `pnpm run <script>`
+  - `vp test` runs the built-in test command, while `vp run test` runs the
+    `test` script from `package.json`
+  - `vp install`, `vp add`, and `vp remove` delegate through the package
+    manager declared by `packageManager`
+  - `vp dev`, `vp build`, `vp preview`, `vp lint`, `vp fmt`, `vp check`,
+    and `vp pack` replace the corresponding standalone tools
+  - Prefer `vp check` for validation loops
+
+  Finally, verify the migration by running:
+  - vp install
+  - vp check
+  - vp test
+  - vp build
+
+  Summarize the migration at the end and report any manual follow-up still
+  required.
+
+Documentation: https://viteplus.dev/guide/migrate
+
diff --git a/packages/cli/snap-tests-global/migration-lintstagedrc-json/snap.txt b/packages/cli/snap-tests-global/migration-lintstagedrc-json/snap.txt
index 8d94817802..238997d15c 100644
--- a/packages/cli/snap-tests-global/migration-lintstagedrc-json/snap.txt
+++ b/packages/cli/snap-tests-global/migration-lintstagedrc-json/snap.txt
@@ -28,6 +28,45 @@ Examples:
   # Non-interactive mode
   vp migrate --no-interactive
 
+Migration Prompt:
+  Give this to a coding agent when you want it to drive the migration:
+
+  Migrate this project to Vite+.
+  Vite+ replaces the current split tooling around runtime management, package
+  management, dev/build/test commands, linting, formatting, and packaging.
+  Run `vp help` and `vp help migrate` before making changes.
+  Use vp migrate --no-interactive in the workspace root.
+  Make sure the project is using Vite 8+ and Vitest 4.1+ before migrating.
+
+  After the migration:
+  - Confirm `vite` imports were rewritten to `vite-plus` where needed
+  - Confirm `vitest` imports were rewritten to `vite-plus/test` where needed
+  - Remove old `vite` and `vitest` dependencies only after those rewrites
+    are confirmed
+  - Move remaining tool-specific config into the appropriate blocks in
+    `vite.config.ts`
+
+  Command mapping:
+  - `vp run <script>` is the equivalent of `pnpm run <script>`
+  - `vp test` runs the built-in test command, while `vp run test` runs the
+    `test` script from `package.json`
+  - `vp install`, `vp add`, and `vp remove` delegate through the package
+    manager declared by `packageManager`
+  - `vp dev`, `vp build`, `vp preview`, `vp lint`, `vp fmt`, `vp check`,
+    and `vp pack` replace the corresponding standalone tools
+  - Prefer `vp check` for validation loops
+
+  Finally, verify the migration by running:
+  - vp install
+  - vp check
+  - vp test
+  - vp build
+
+  Summarize the migration at the end and report any manual follow-up still
+  required.
+
+Documentation: https://viteplus.dev/guide/migrate
+
 
 > vp migrate --no-interactive # migration work with lintstagedrc.json
 VITE+ - The Unified Toolchain for the Web
diff --git a/packages/cli/snap-tests-global/new-check/snap.txt b/packages/cli/snap-tests-global/new-check/snap.txt
index 98a65154f8..8deb28f424 100644
--- a/packages/cli/snap-tests-global/new-check/snap.txt
+++ b/packages/cli/snap-tests-global/new-check/snap.txt
@@ -49,6 +49,8 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+Documentation: https://viteplus.dev/guide/create
+
 
 > vp create --list # list templates
 VITE+ - The Unified Toolchain for the Web
@@ -80,6 +82,8 @@ Examples:
 Tip:
   You can use any npm template or git repo with vp create.
 
+Documentation: https://viteplus.dev/guide/create
+
 
 [1]> vp create --no-interactive # run in non-interactive mode without template name will show error
 
diff --git a/packages/cli/snap-tests/check-fix-paths/snap.txt b/packages/cli/snap-tests/check-fix-paths/snap.txt
index 16ac98ff36..f335c815b6 100644
--- a/packages/cli/snap-tests/check-fix-paths/snap.txt
+++ b/packages/cli/snap-tests/check-fix-paths/snap.txt
@@ -1,3 +1,3 @@
 > vp check --fix src/index.js
 pass: Formatting completed for checked files (<variable>ms)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-fix-reformat/snap.txt b/packages/cli/snap-tests/check-fix-reformat/snap.txt
index 57aa29f3a4..8284e59b13 100644
--- a/packages/cli/snap-tests/check-fix-reformat/snap.txt
+++ b/packages/cli/snap-tests/check-fix-reformat/snap.txt
@@ -1,7 +1,7 @@
 > vp check --fix
 pass: Formatting completed for checked files (<variable>ms)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
 
 > vp check # should pass after fix
 pass: All 4 files are correctly formatted (<variable>ms, <variable> threads)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-fix/snap.txt b/packages/cli/snap-tests/check-fix/snap.txt
index 9222a15fad..3c35478886 100644
--- a/packages/cli/snap-tests/check-fix/snap.txt
+++ b/packages/cli/snap-tests/check-fix/snap.txt
@@ -1,3 +1,3 @@
 > vp check --fix
 pass: Formatting completed for checked files (<variable>ms)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-fmt-fail/snap.txt b/packages/cli/snap-tests/check-fmt-fail/snap.txt
index 239d1f3c94..c3431b012c 100644
--- a/packages/cli/snap-tests/check-fmt-fail/snap.txt
+++ b/packages/cli/snap-tests/check-fmt-fail/snap.txt
@@ -7,8 +7,8 @@ Found formatting issues in 2 files (<variable>ms, <variable> threads). Run `vp c
 
 > vp check --fix
 pass: Formatting completed for checked files (<variable>ms)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
 
 > vp check # should pass after fix
 pass: All 3 files are correctly formatted (<variable>ms, <variable> threads)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-lint-fail-no-typecheck/.oxlintrc.json b/packages/cli/snap-tests/check-lint-fail-no-typecheck/.oxlintrc.json
new file mode 100644
index 0000000000..d71deeeee8
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-no-typecheck/.oxlintrc.json
@@ -0,0 +1,5 @@
+{
+  "rules": {
+    "no-eval": "error"
+  }
+}
diff --git a/packages/cli/snap-tests/check-lint-fail-no-typecheck/package.json b/packages/cli/snap-tests/check-lint-fail-no-typecheck/package.json
new file mode 100644
index 0000000000..8a634f539b
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-no-typecheck/package.json
@@ -0,0 +1,5 @@
+{
+  "name": "check-lint-fail-no-typecheck",
+  "version": "0.0.0",
+  "private": true
+}
diff --git a/packages/cli/snap-tests/check-lint-fail-no-typecheck/snap.txt b/packages/cli/snap-tests/check-lint-fail-no-typecheck/snap.txt
new file mode 100644
index 0000000000..69b7f7d2e0
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-no-typecheck/snap.txt
@@ -0,0 +1,13 @@
+[1]> vp check
+pass: All 5 files are correctly formatted (<variable>ms, <variable> threads)
+error: Lint issues found
+× eslint(no-eval): eval can be harmful.
+   ╭─[src/index.js:2:3]
+ 1 │ function hello() {
+ 2 │   eval("code");
+   ·   ────
+ 3 │   return "hello";
+   ╰────
+  help: Avoid eval(). For JSON parsing use JSON.parse(); for dynamic property access use bracket notation (obj[key]); for other cases refactor to avoid evaluating strings as code.
+
+Found 1 error and 0 warnings in 2 files (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-lint-fail-no-typecheck/src/index.js b/packages/cli/snap-tests/check-lint-fail-no-typecheck/src/index.js
new file mode 100644
index 0000000000..e916f931f1
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-no-typecheck/src/index.js
@@ -0,0 +1,6 @@
+function hello() {
+  eval("code");
+  return "hello";
+}
+
+export { hello };
diff --git a/packages/cli/snap-tests/check-lint-fail-no-typecheck/steps.json b/packages/cli/snap-tests/check-lint-fail-no-typecheck/steps.json
new file mode 100644
index 0000000000..d9c26d5a29
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-no-typecheck/steps.json
@@ -0,0 +1,6 @@
+{
+  "env": {
+    "VITE_DISABLE_AUTO_INSTALL": "1"
+  },
+  "commands": ["vp check"]
+}
diff --git a/packages/cli/snap-tests/check-lint-fail-no-typecheck/vite.config.ts b/packages/cli/snap-tests/check-lint-fail-no-typecheck/vite.config.ts
new file mode 100644
index 0000000000..a296af3c42
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-no-typecheck/vite.config.ts
@@ -0,0 +1,12 @@
+export default {
+  fmt: {},
+  lint: {
+    options: {
+      typeAware: true,
+      typeCheck: false,
+    },
+    rules: {
+      "no-eval": "error",
+    },
+  },
+};
diff --git a/packages/cli/snap-tests/check-lint-fail-typecheck/.oxlintrc.json b/packages/cli/snap-tests/check-lint-fail-typecheck/.oxlintrc.json
new file mode 100644
index 0000000000..d71deeeee8
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-typecheck/.oxlintrc.json
@@ -0,0 +1,5 @@
+{
+  "rules": {
+    "no-eval": "error"
+  }
+}
diff --git a/packages/cli/snap-tests/check-lint-fail-typecheck/package.json b/packages/cli/snap-tests/check-lint-fail-typecheck/package.json
new file mode 100644
index 0000000000..c1e018f941
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-typecheck/package.json
@@ -0,0 +1,5 @@
+{
+  "name": "check-lint-fail-typecheck",
+  "version": "0.0.0",
+  "private": true
+}
diff --git a/packages/cli/snap-tests/check-lint-fail-typecheck/snap.txt b/packages/cli/snap-tests/check-lint-fail-typecheck/snap.txt
new file mode 100644
index 0000000000..15aa8cb532
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-typecheck/snap.txt
@@ -0,0 +1,13 @@
+[1]> vp check
+pass: All 5 files are correctly formatted (<variable>ms, <variable> threads)
+error: Lint or type issues found
+× eslint(no-eval): eval can be harmful.
+   ╭─[src/index.js:2:3]
+ 1 │ function hello() {
+ 2 │   eval("code");
+   ·   ────
+ 3 │   return "hello";
+   ╰────
+  help: Avoid eval(). For JSON parsing use JSON.parse(); for dynamic property access use bracket notation (obj[key]); for other cases refactor to avoid evaluating strings as code.
+
+Found 1 error and 0 warnings in 2 files (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-lint-fail-typecheck/src/index.js b/packages/cli/snap-tests/check-lint-fail-typecheck/src/index.js
new file mode 100644
index 0000000000..e916f931f1
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-typecheck/src/index.js
@@ -0,0 +1,6 @@
+function hello() {
+  eval("code");
+  return "hello";
+}
+
+export { hello };
diff --git a/packages/cli/snap-tests/check-lint-fail-typecheck/steps.json b/packages/cli/snap-tests/check-lint-fail-typecheck/steps.json
new file mode 100644
index 0000000000..d9c26d5a29
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-typecheck/steps.json
@@ -0,0 +1,6 @@
+{
+  "env": {
+    "VITE_DISABLE_AUTO_INSTALL": "1"
+  },
+  "commands": ["vp check"]
+}
diff --git a/packages/cli/snap-tests/check-lint-fail-typecheck/vite.config.ts b/packages/cli/snap-tests/check-lint-fail-typecheck/vite.config.ts
new file mode 100644
index 0000000000..73be7c0ab4
--- /dev/null
+++ b/packages/cli/snap-tests/check-lint-fail-typecheck/vite.config.ts
@@ -0,0 +1,12 @@
+export default {
+  fmt: {},
+  lint: {
+    options: {
+      typeAware: true,
+      typeCheck: true,
+    },
+    rules: {
+      "no-eval": "error",
+    },
+  },
+};
diff --git a/packages/cli/snap-tests/check-lint-fail/snap.txt b/packages/cli/snap-tests/check-lint-fail/snap.txt
index d19332cb43..20118a3a0e 100644
--- a/packages/cli/snap-tests/check-lint-fail/snap.txt
+++ b/packages/cli/snap-tests/check-lint-fail/snap.txt
@@ -1,6 +1,6 @@
 [1]> vp check
 pass: All 4 files are correctly formatted (<variable>ms, <variable> threads)
-error: Lint or type issues found
+error: Lint issues found
 × eslint(no-eval): eval can be harmful.
    ╭─[src/index.js:2:3]
  1 │ function hello() {
diff --git a/packages/cli/snap-tests/check-lint-warn/snap.txt b/packages/cli/snap-tests/check-lint-warn/snap.txt
index 25d8bccd6b..b2c6dddf22 100644
--- a/packages/cli/snap-tests/check-lint-warn/snap.txt
+++ b/packages/cli/snap-tests/check-lint-warn/snap.txt
@@ -1,6 +1,6 @@
 > vp check
 pass: All 4 files are correctly formatted (<variable>ms, <variable> threads)
-warn: Lint or type warnings found
+warn: Lint warnings found
 ⚠ eslint(no-console): Unexpected console statement.
    ╭─[src/index.js:2:3]
  1 │ function hello() {
diff --git a/packages/cli/snap-tests/check-no-fmt/snap.txt b/packages/cli/snap-tests/check-no-fmt/snap.txt
index a252c8c003..752440eac2 100644
--- a/packages/cli/snap-tests/check-no-fmt/snap.txt
+++ b/packages/cli/snap-tests/check-no-fmt/snap.txt
@@ -1,2 +1,2 @@
 > vp check --no-fmt
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-pass-no-typecheck/package.json b/packages/cli/snap-tests/check-pass-no-typecheck/package.json
new file mode 100644
index 0000000000..a42bd07659
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-no-typecheck/package.json
@@ -0,0 +1,5 @@
+{
+  "name": "check-pass-no-typecheck",
+  "version": "0.0.0",
+  "private": true
+}
diff --git a/packages/cli/snap-tests/check-pass-no-typecheck/snap.txt b/packages/cli/snap-tests/check-pass-no-typecheck/snap.txt
new file mode 100644
index 0000000000..6d34d2a543
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-no-typecheck/snap.txt
@@ -0,0 +1,3 @@
+> vp check
+pass: All 4 files are correctly formatted (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 2 files (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-pass-no-typecheck/src/index.js b/packages/cli/snap-tests/check-pass-no-typecheck/src/index.js
new file mode 100644
index 0000000000..13305bd3e9
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-no-typecheck/src/index.js
@@ -0,0 +1,5 @@
+function hello() {
+  return "hello";
+}
+
+export { hello };
diff --git a/packages/cli/snap-tests/check-pass-no-typecheck/steps.json b/packages/cli/snap-tests/check-pass-no-typecheck/steps.json
new file mode 100644
index 0000000000..d9c26d5a29
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-no-typecheck/steps.json
@@ -0,0 +1,6 @@
+{
+  "env": {
+    "VITE_DISABLE_AUTO_INSTALL": "1"
+  },
+  "commands": ["vp check"]
+}
diff --git a/packages/cli/snap-tests/check-pass-no-typecheck/vite.config.ts b/packages/cli/snap-tests/check-pass-no-typecheck/vite.config.ts
new file mode 100644
index 0000000000..34a6d886f6
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-no-typecheck/vite.config.ts
@@ -0,0 +1,9 @@
+export default {
+  fmt: {},
+  lint: {
+    options: {
+      typeAware: true,
+      typeCheck: false,
+    },
+  },
+};
diff --git a/packages/cli/snap-tests/check-pass-typecheck/package.json b/packages/cli/snap-tests/check-pass-typecheck/package.json
new file mode 100644
index 0000000000..40ceae4dc3
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-typecheck/package.json
@@ -0,0 +1,5 @@
+{
+  "name": "check-pass-typecheck",
+  "version": "0.0.0",
+  "private": true
+}
diff --git a/packages/cli/snap-tests/check-pass-typecheck/snap.txt b/packages/cli/snap-tests/check-pass-typecheck/snap.txt
new file mode 100644
index 0000000000..ee9e81eaf4
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-typecheck/snap.txt
@@ -0,0 +1,3 @@
+> vp check
+pass: All 4 files are correctly formatted (<variable>ms, <variable> threads)
+pass: Found no warnings, lint errors, or type errors in 2 files (<variable>ms, <variable> threads)
diff --git a/packages/cli/snap-tests/check-pass-typecheck/src/index.js b/packages/cli/snap-tests/check-pass-typecheck/src/index.js
new file mode 100644
index 0000000000..13305bd3e9
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-typecheck/src/index.js
@@ -0,0 +1,5 @@
+function hello() {
+  return "hello";
+}
+
+export { hello };
diff --git a/packages/cli/snap-tests/check-pass-typecheck/steps.json b/packages/cli/snap-tests/check-pass-typecheck/steps.json
new file mode 100644
index 0000000000..d9c26d5a29
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-typecheck/steps.json
@@ -0,0 +1,6 @@
+{
+  "env": {
+    "VITE_DISABLE_AUTO_INSTALL": "1"
+  },
+  "commands": ["vp check"]
+}
diff --git a/packages/cli/snap-tests/check-pass-typecheck/vite.config.ts b/packages/cli/snap-tests/check-pass-typecheck/vite.config.ts
new file mode 100644
index 0000000000..0de3ca3b64
--- /dev/null
+++ b/packages/cli/snap-tests/check-pass-typecheck/vite.config.ts
@@ -0,0 +1,9 @@
+export default {
+  fmt: {},
+  lint: {
+    options: {
+      typeAware: true,
+      typeCheck: true,
+    },
+  },
+};
diff --git a/packages/cli/snap-tests/check-pass/snap.txt b/packages/cli/snap-tests/check-pass/snap.txt
index 05d852fbdb..f1f39efc3a 100644
--- a/packages/cli/snap-tests/check-pass/snap.txt
+++ b/packages/cli/snap-tests/check-pass/snap.txt
@@ -1,3 +1,3 @@
 > vp check
 pass: All 3 files are correctly formatted (<variable>ms, <variable> threads)
-pass: Found no warnings, lint errors, or type errors in 1 file (<variable>ms, <variable> threads)
+pass: Found no warnings or lint errors in 1 file (<variable>ms, <variable> threads)
diff --git a/packages/cli/src/config/bin.ts b/packages/cli/src/config/bin.ts
index 397d98618a..717cdd0619 100644
--- a/packages/cli/src/config/bin.ts
+++ b/packages/cli/src/config/bin.ts
@@ -33,6 +33,7 @@ async function main() {
     const helpMessage = renderCliDoc({
       usage: 'vp config [OPTIONS]',
       summary: 'Configure Vite+ for the current project (hooks + agent integration).',
+      documentationUrl: 'https://viteplus.dev/guide/commit-hooks',
       sections: [
         {
           title: 'Options',
diff --git a/packages/cli/src/create/__tests__/initial-template-options.spec.ts b/packages/cli/src/create/__tests__/initial-template-options.spec.ts
new file mode 100644
index 0000000000..fc0d8778f9
--- /dev/null
+++ b/packages/cli/src/create/__tests__/initial-template-options.spec.ts
@@ -0,0 +1,40 @@
+import { describe, expect, it } from 'vitest';
+
+import { getInitialTemplateOptions } from '../initial-template-options.js';
+
+describe('getInitialTemplateOptions', () => {
+  it('shows only built-in monorepo, application, and library options outside a monorepo', () => {
+    expect(getInitialTemplateOptions(false)).toEqual([
+      {
+        label: 'Vite+ Monorepo',
+        value: 'vite:monorepo',
+        hint: 'Create a new Vite+ monorepo project',
+      },
+      {
+        label: 'Vite+ Application',
+        value: 'vite:application',
+        hint: 'Create vite applications',
+      },
+      {
+        label: 'Vite+ Library',
+        value: 'vite:library',
+        hint: 'Create vite libraries',
+      },
+    ]);
+  });
+
+  it('shows only built-in application and library options inside a monorepo', () => {
+    expect(getInitialTemplateOptions(true)).toEqual([
+      {
+        label: 'Vite+ Application',
+        value: 'vite:application',
+        hint: 'Create vite applications',
+      },
+      {
+        label: 'Vite+ Library',
+        value: 'vite:library',
+        hint: 'Create vite libraries',
+      },
+    ]);
+  });
+});
diff --git a/packages/cli/src/create/bin.ts b/packages/cli/src/create/bin.ts
index 6048c8e2e0..25ee8a03b4 100644
--- a/packages/cli/src/create/bin.ts
+++ b/packages/cli/src/create/bin.ts
@@ -37,6 +37,7 @@ import {
 } from '../utils/workspace.js';
 import type { ExecutionResult } from './command.js';
 import { discoverTemplate, inferGitHubRepoName, inferParentDir, isGitHubUrl } from './discovery.js';
+import { getInitialTemplateOptions } from './initial-template-options.js';
 import {
   cancelAndExit,
   checkProjectDirExists,
@@ -57,6 +58,7 @@ import { formatTargetDir } from './utils.js';
 const helpMessage = renderCliDoc({
   usage: 'vp create [TEMPLATE] [OPTIONS] [-- TEMPLATE_OPTIONS]',
   summary: 'Use any builtin, local or remote template with Vite+.',
+  documentationUrl: 'https://viteplus.dev/guide/create',
   sections: [
     {
       title: 'Arguments',
@@ -132,6 +134,7 @@ const helpMessage = renderCliDoc({
 const listTemplatesMessage = renderCliDoc({
   usage: 'vp create --list',
   summary: 'List available builtin and popular project templates.',
+  documentationUrl: 'https://viteplus.dev/guide/create',
   sections: [
     {
       title: 'Vite+ Built-in Templates',
@@ -430,86 +433,16 @@ Use \`vp create --list\` to list all available templates, or run \`vp create --h
   let shouldSetupHooks = false;
 
   if (!selectedTemplateName) {
-    const templates: { label: string; value: string; hint: string }[] = [];
-    if (isMonorepo) {
-      // find local templates in the monorepo
-      for (const pkg of workspaceInfoOptional.packages) {
-        if (pkg.isTemplatePackage) {
-          templates.push({
-            label: pkg.name,
-            value: pkg.name,
-            hint: pkg.description ?? pkg.path,
-          });
-        }
-      }
-    } else {
-      templates.push({
-        label: 'Vite+ Monorepo',
-        value: BuiltinTemplate.monorepo,
-        hint: 'Create a new Vite+ monorepo project',
-      });
-    }
     const template = await prompts.select({
       message: '',
-      options: [
-        ...templates,
-        {
-          label: 'Vite+ Application',
-          value: BuiltinTemplate.application,
-          hint: 'Create vite applications',
-        },
-        {
-          label: 'Vite+ Library',
-          value: BuiltinTemplate.library,
-          hint: 'Create vite libraries',
-        },
-        // TODO: only support builtin generator template in monorepo for now
-        ...(isMonorepo
-          ? [
-              {
-                label: 'Vite+ Generator',
-                value: BuiltinTemplate.generator,
-                hint: 'Scaffold a new code generator',
-              },
-            ]
-          : []),
-        {
-          label: 'TanStack Start',
-          value: '@tanstack/create-start@latest',
-          hint: 'Create TanStack applications and libraries',
-        },
-        {
-          label: 'Others',
-          value: 'other',
-          hint: 'Enter a custom template package name',
-        },
-      ],
+      options: getInitialTemplateOptions(isMonorepo),
     });
 
     if (prompts.isCancel(template)) {
       cancelAndExit();
     }
 
-    // Handle custom template input
-    if (template === 'other') {
-      const customTemplate = await prompts.text({
-        message: 'Enter the template package name:',
-        placeholder: 'e.g., create-next-app, create-nuxt',
-        validate: (value) => {
-          if (!value || value.trim().length === 0) {
-            return 'Template name is required';
-          }
-        },
-      });
-
-      if (prompts.isCancel(customTemplate)) {
-        cancelAndExit();
-      }
-
-      selectedTemplateName = customTemplate;
-    } else {
-      selectedTemplateName = template;
-    }
+    selectedTemplateName = template;
   }
 
   const isBuiltinTemplate = selectedTemplateName.startsWith('vite:');
diff --git a/packages/cli/src/create/initial-template-options.ts b/packages/cli/src/create/initial-template-options.ts
new file mode 100644
index 0000000000..49980756b8
--- /dev/null
+++ b/packages/cli/src/create/initial-template-options.ts
@@ -0,0 +1,31 @@
+import { BuiltinTemplate } from './templates/types.js';
+
+export interface InitialTemplateOption {
+  label: string;
+  value: string;
+  hint: string;
+}
+
+export function getInitialTemplateOptions(isMonorepo: boolean): InitialTemplateOption[] {
+  return [
+    ...(!isMonorepo
+      ? [
+          {
+            label: 'Vite+ Monorepo',
+            value: BuiltinTemplate.monorepo,
+            hint: 'Create a new Vite+ monorepo project',
+          },
+        ]
+      : []),
+    {
+      label: 'Vite+ Application',
+      value: BuiltinTemplate.application,
+      hint: 'Create vite applications',
+    },
+    {
+      label: 'Vite+ Library',
+      value: BuiltinTemplate.library,
+      hint: 'Create vite libraries',
+    },
+  ];
+}
diff --git a/packages/cli/src/migration/bin.ts b/packages/cli/src/migration/bin.ts
index 5dd56b5494..3f807f7d16 100644
--- a/packages/cli/src/migration/bin.ts
+++ b/packages/cli/src/migration/bin.ts
@@ -170,6 +170,7 @@ const helpMessage = renderCliDoc({
   usage: 'vp migrate [PATH] [OPTIONS]',
   summary:
     'Migrate standalone Vite, Vitest, Oxlint, Oxfmt, and Prettier projects to unified Vite+.',
+  documentationUrl: 'https://viteplus.dev/guide/migrate',
   sections: [
     {
       title: 'Arguments',
@@ -219,6 +220,46 @@ const helpMessage = renderCliDoc({
         `  ${accent('vp migrate --no-interactive')}`,
       ],
     },
+    {
+      title: 'Migration Prompt',
+      lines: [
+        '  Give this to a coding agent when you want it to drive the migration:',
+        '',
+        '  Migrate this project to Vite+.',
+        '  Vite+ replaces the current split tooling around runtime management, package',
+        '  management, dev/build/test commands, linting, formatting, and packaging.',
+        '  Run `vp help` and `vp help migrate` before making changes.',
+        `  Use ${accent('vp migrate --no-interactive')} in the workspace root.`,
+        '  Make sure the project is using Vite 8+ and Vitest 4.1+ before migrating.',
+        '',
+        '  After the migration:',
+        '  - Confirm `vite` imports were rewritten to `vite-plus` where needed',
+        '  - Confirm `vitest` imports were rewritten to `vite-plus/test` where needed',
+        '  - Remove old `vite` and `vitest` dependencies only after those rewrites',
+        '    are confirmed',
+        '  - Move remaining tool-specific config into the appropriate blocks in',
+        '    `vite.config.ts`',
+        '',
+        '  Command mapping:',
+        '  - `vp run <script>` is the equivalent of `pnpm run <script>`',
+        '  - `vp test` runs the built-in test command, while `vp run test` runs the',
+        '    `test` script from `package.json`',
+        '  - `vp install`, `vp add`, and `vp remove` delegate through the package',
+        '    manager declared by `packageManager`',
+        '  - `vp dev`, `vp build`, `vp preview`, `vp lint`, `vp fmt`, `vp check`,',
+        '    and `vp pack` replace the corresponding standalone tools',
+        '  - Prefer `vp check` for validation loops',
+        '',
+        '  Finally, verify the migration by running:',
+        `  - ${accent('vp install')}`,
+        `  - ${accent('vp check')}`,
+        `  - ${accent('vp test')}`,
+        `  - ${accent('vp build')}`,
+        '',
+        '  Summarize the migration at the end and report any manual follow-up still',
+        '  required.',
+      ],
+    },
   ],
 });
 
diff --git a/packages/cli/src/staged/bin.ts b/packages/cli/src/staged/bin.ts
index 8bf1264744..fa4f28658c 100644
--- a/packages/cli/src/staged/bin.ts
+++ b/packages/cli/src/staged/bin.ts
@@ -16,7 +16,7 @@ import mri from 'mri';
 import { vitePlusHeader } from '../../binding/index.js';
 import { resolveViteConfig } from '../resolve-vite-config.js';
 import { renderCliDoc } from '../utils/help.js';
-import { log } from '../utils/terminal.js';
+import { errorMsg, log } from '../utils/terminal.js';
 
 const args = mri(process.argv.slice(3), {
   alias: {
@@ -48,6 +48,7 @@ if (args.help) {
   const helpMessage = renderCliDoc({
     usage: 'vp staged [options]',
     summary: 'Run linters on staged files using staged config from vite.config.ts.',
+    documentationUrl: 'https://viteplus.dev/guide/commit-hooks',
     sections: [
       {
         title: 'Options',
@@ -151,7 +152,8 @@ if (args.help) {
   if (stagedConfig) {
     options.config = stagedConfig as Configuration;
   } else {
-    log('No "staged" config found in vite.config.ts. Please add a staged config:');
+    log(vitePlusHeader() + '\n');
+    errorMsg('No "staged" config found in vite.config.ts. Please add a staged config:');
     log('');
     log('  // vite.config.ts');
     log('  export default defineConfig({');
diff --git a/packages/cli/src/utils/__tests__/help.spec.ts b/packages/cli/src/utils/__tests__/help.spec.ts
index b6a9184dd0..6cd1bfa6ef 100644
--- a/packages/cli/src/utils/__tests__/help.spec.ts
+++ b/packages/cli/src/utils/__tests__/help.spec.ts
@@ -1,3 +1,5 @@
+import { stripVTControlCharacters } from 'node:util';
+
 import { describe, expect, it } from 'vitest';
 
 import { renderCliDoc } from '../help.js';
@@ -68,4 +70,16 @@ describe('renderCliDoc', () => {
       "
     `);
   });
+
+  it('renders documentation footer when present', () => {
+    const output = renderCliDoc({
+      usage: 'vp demo',
+      documentationUrl: 'https://viteplus.dev/guide/demo',
+      sections: [{ title: 'Arguments', rows: [{ label: '<name>', description: 'Project name' }] }],
+    });
+
+    expect(stripVTControlCharacters(output)).toContain(
+      'Documentation: https://viteplus.dev/guide/demo',
+    );
+  });
 });
diff --git a/packages/cli/src/utils/editor.ts b/packages/cli/src/utils/editor.ts
index 5eff268f37..297dc82b21 100644
--- a/packages/cli/src/utils/editor.ts
+++ b/packages/cli/src/utils/editor.ts
@@ -18,7 +18,7 @@ const VSCODE_SETTINGS = {
 } as const;
 
 const VSCODE_EXTENSIONS = {
-  recommendations: ['oxc.oxc-vscode'],
+  recommendations: ['VoidZero.vite-plus-extension-pack'],
 } as const;
 
 export const EDITORS = [
diff --git a/packages/cli/src/utils/help.ts b/packages/cli/src/utils/help.ts
index 2240b8f493..4a9b9bfe1a 100644
--- a/packages/cli/src/utils/help.ts
+++ b/packages/cli/src/utils/help.ts
@@ -4,6 +4,7 @@ export type CliDoc = {
   usage?: string;
   summary?: readonly string[] | string;
   sections: readonly CliSection[];
+  documentationUrl?: string;
 };
 
 export type CliSection = {
@@ -66,7 +67,13 @@ function renderRows(rows: readonly CliRow[]): string[] {
 }
 
 function heading(label: string, color: boolean): string {
-  return color ? styleText('bold', `${label}:`) : `${label}:`;
+  if (!color) {
+    return `${label}:`;
+  }
+
+  return label === 'Usage'
+    ? styleText('bold', `${label}:`)
+    : styleText(['blue', 'bold'], `${label}:`);
 }
 
 export function renderCliDoc(doc: CliDoc, options: RenderCliDocOptions = {}): string {
@@ -102,6 +109,13 @@ export function renderCliDoc(doc: CliDoc, options: RenderCliDocOptions = {}): st
     }
   }
 
+  if (doc.documentationUrl) {
+    if (output.length > 0) {
+      output.push('');
+    }
+    output.push(`${heading('Documentation', color)} ${doc.documentationUrl}`);
+  }
+
   output.push('');
   return output.join('\n');
 }
diff --git a/packages/core/package.json b/packages/core/package.json
index 2fb038c5b5..1a4999ed1b 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -32,56 +32,56 @@
     "./internal": "./dist/vite/node/internal.js",
     "./module-runner": "./dist/vite/node/module-runner.js",
     "./pack": {
-      "types": "./dist/tsdown/index-types.d.ts",
-      "default": "./dist/tsdown/index.js"
+      "default": "./dist/tsdown/index.js",
+      "types": "./dist/tsdown/index-types.d.ts"
     },
     "./package.json": "./package.json",
     "./rolldown": {
-      "types": "./dist/rolldown/index.d.mts",
-      "default": "./dist/rolldown/index.mjs"
+      "default": "./dist/rolldown/index.mjs",
+      "types": "./dist/rolldown/index.d.mts"
     },
     "./rolldown/config": {
-      "types": "./dist/rolldown/config.d.mts",
-      "default": "./dist/rolldown/config.mjs"
+      "default": "./dist/rolldown/config.mjs",
+      "types": "./dist/rolldown/config.d.mts"
     },
     "./rolldown/experimental": {
-      "types": "./dist/rolldown/experimental-index.d.mts",
-      "default": "./dist/rolldown/experimental-index.mjs"
+      "default": "./dist/rolldown/experimental-index.mjs",
+      "types": "./dist/rolldown/experimental-index.d.mts"
     },
     "./rolldown/experimental/runtime-types": {
       "types": "./dist/rolldown/experimental-runtime-types.d.ts"
     },
     "./rolldown/filter": {
-      "types": "./dist/rolldown/filter-index.d.mts",
-      "default": "./dist/rolldown/filter-index.mjs"
+      "default": "./dist/rolldown/filter-index.mjs",
+      "types": "./dist/rolldown/filter-index.d.mts"
     },
     "./rolldown/getLogFilter": {
-      "types": "./dist/rolldown/get-log-filter.d.mts",
-      "default": "./dist/rolldown/get-log-filter.mjs"
+      "default": "./dist/rolldown/get-log-filter.mjs",
+      "types": "./dist/rolldown/get-log-filter.d.mts"
     },
     "./rolldown/parallelPlugin": {
-      "types": "./dist/rolldown/parallel-plugin.d.mts",
-      "default": "./dist/rolldown/parallel-plugin.mjs"
+      "default": "./dist/rolldown/parallel-plugin.mjs",
+      "types": "./dist/rolldown/parallel-plugin.d.mts"
     },
     "./rolldown/parseAst": {
-      "types": "./dist/rolldown/parse-ast-index.d.mts",
-      "default": "./dist/rolldown/parse-ast-index.mjs"
+      "default": "./dist/rolldown/parse-ast-index.mjs",
+      "types": "./dist/rolldown/parse-ast-index.d.mts"
     },
     "./rolldown/plugins": {
-      "types": "./dist/rolldown/plugins-index.d.mts",
-      "default": "./dist/rolldown/plugins-index.mjs"
+      "default": "./dist/rolldown/plugins-index.mjs",
+      "types": "./dist/rolldown/plugins-index.d.mts"
     },
     "./rolldown/pluginutils": {
-      "types": "./dist/pluginutils/index.d.ts",
-      "default": "./dist/pluginutils/index.js"
+      "default": "./dist/pluginutils/index.js",
+      "types": "./dist/pluginutils/index.d.ts"
     },
     "./rolldown/pluginutils/filter": {
-      "types": "./dist/pluginutils/filter/index.d.ts",
-      "default": "./dist/pluginutils/filter/index.js"
+      "default": "./dist/pluginutils/filter/index.js",
+      "types": "./dist/pluginutils/filter/index.d.ts"
     },
     "./rolldown/utils": {
-      "types": "./dist/rolldown/utils-index.d.mts",
-      "default": "./dist/rolldown/utils-index.mjs"
+      "default": "./dist/rolldown/utils-index.mjs",
+      "types": "./dist/rolldown/utils-index.d.mts"
     },
     "./types/*": {
       "types": "./dist/vite/types/*"
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index ca1e0817fb..e345c72047 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -342,8 +342,8 @@ importers:
         version: 0.16.0(vue@3.5.27(typescript@5.9.3))
     devDependencies:
       '@voidzero-dev/vitepress-theme':
-        specifier: 4.8.0
-        version: 4.8.0(focus-trap@7.8.0)(typescript@5.9.3)(vite@packages+core)(vitepress@2.0.0-alpha.15(oxc-minify@0.110.0)(postcss@8.5.6)(typescript@5.9.3))(vue@3.5.27(typescript@5.9.3))
+        specifier: 4.8.2
+        version: 4.8.2(focus-trap@7.8.0)(typescript@5.9.3)(vite@packages+core)(vitepress@2.0.0-alpha.15(oxc-minify@0.110.0)(postcss@8.5.6)(typescript@5.9.3))(vue@3.5.27(typescript@5.9.3))
       oxc-minify:
         specifier: ^0.110.0
         version: 0.110.0
@@ -5174,8 +5174,8 @@ packages:
   '@vitest/utils@4.1.0-beta.5':
     resolution: {integrity: sha512-yDobPgmVL/4YhVXsbBcmeUb5CIdZiJkoonPnuJXKOxmnj0XZyu7OgIX3KLOcRStbia3nJZ9VIIBWoSv+HS+wVA==}
 
-  '@voidzero-dev/vitepress-theme@4.8.0':
-    resolution: {integrity: sha512-upydmVGsJxUjgAITlYWEsc/w0gA9vDkSs7FPgYn/2rTjcVrZ39LGxkWibrI/i5yJ/Sxhs3UPnWfmKB8Do7C0EA==}
+  '@voidzero-dev/vitepress-theme@4.8.2':
+    resolution: {integrity: sha512-M3LfcjJCFv9wQYzMhhvQJbpQZaJ9zUGuWCIvP8g4hMP52vHtJ10AG1/bHctInFglRr90txL+rbdhpVwcNGkcjA==}
     peerDependencies:
       vitepress: ^2.0.0-alpha.16
       vue: ^3.5.0
@@ -5551,6 +5551,7 @@ packages:
   basic-ftp@5.0.5:
     resolution: {integrity: sha512-4Bcg1P8xhUuqcii/S0Z9wiHIrQVPMermM1any+MX5GeGD7faD3/msQUDGLol9wOcz4/jbg/WJnGqoJF6LiBdtg==}
     engines: {node: '>=10.0.0'}
+    deprecated: Security vulnerability fixed in 5.2.0, please upgrade
 
   before-after-hook@4.0.0:
     resolution: {integrity: sha512-q6tR3RPqIB1pMiTRMFcZwuG5T8vwp+vUvEG0vuI6B+Rikh5BfPp2fQ82c925FOs+b0lcFQ8CFrL+KbilfZFhOQ==}
@@ -12756,7 +12757,7 @@ snapshots:
       convert-source-map: 2.0.0
       tinyrainbow: 3.0.3
 
-  '@voidzero-dev/vitepress-theme@4.8.0(focus-trap@7.8.0)(typescript@5.9.3)(vite@packages+core)(vitepress@2.0.0-alpha.15(oxc-minify@0.110.0)(postcss@8.5.6)(typescript@5.9.3))(vue@3.5.27(typescript@5.9.3))':
+  '@voidzero-dev/vitepress-theme@4.8.2(focus-trap@7.8.0)(typescript@5.9.3)(vite@packages+core)(vitepress@2.0.0-alpha.15(oxc-minify@0.110.0)(postcss@8.5.6)(typescript@5.9.3))(vue@3.5.27(typescript@5.9.3))':
     dependencies:
       '@docsearch/css': 4.6.0
       '@docsearch/js': 4.6.0
diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
index eed2e53f65..352ec8670a 100644
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -41,7 +41,7 @@ catalog:
   '@vitejs/plugin-react': ^5.1.2
   '@vitest/browser': ^4.0.9
   '@vitest/browser-playwright': ^4.0.9
-  '@voidzero-dev/vitepress-theme': 4.8.0
+  '@voidzero-dev/vitepress-theme': 4.8.2
   '@vueuse/core': ^14.0.0
   '@yarnpkg/fslib': ^3.1.3
   '@yarnpkg/shell': ^4.1.3
@@ -141,6 +141,7 @@ minimumReleaseAgeExclude:
   - '@types/*'
   - '@vitejs/*'
   - '@vitest/*'
+  - '@voidzero-dev/*'
   - oxc-minify
   - oxc-parser
   - oxc-transform
diff --git a/rfcs/env-command.md b/rfcs/env-command.md
index feb9c469e1..062495e8cb 100644
--- a/rfcs/env-command.md
+++ b/rfcs/env-command.md
@@ -866,7 +866,7 @@ The global CLI installation script (`packages/global/install.sh`) will be update
 5. If already configured, skip silently
 
 ```bash
-$ curl -fsSL https://viteplus.dev/install.sh | sh
+$ curl -fsSL https://vite.plus | sh
 
 Setting up VITE+...
 
diff --git a/rfcs/global-cli-rust-binary.md b/rfcs/global-cli-rust-binary.md
index 2ecee4363b..a4706cfffc 100644
--- a/rfcs/global-cli-rust-binary.md
+++ b/rfcs/global-cli-rust-binary.md
@@ -68,7 +68,7 @@ npm install -g vite-plus-cli
 vp create my-app
 
 # After (no Node.js required)
-curl -fsSL https://viteplus.dev/install.sh | bash
+curl -fsSL https://vite.plus | bash
 # or
 brew install vite-plus
 # or download binary directly
@@ -723,7 +723,7 @@ For users who prefer standalone installation without npm:
 
 ```bash
 #!/bin/bash
-# https://viteplus.dev/install.sh
+# https://vite.plus
 #
 # Environment variables:
 #   VITE_PLUS_VERSION - Version to install (default: latest)
@@ -774,7 +774,7 @@ See [`packages/global/install.sh`](../packages/global/install.sh) for the full i
 For Windows users, provide a PowerShell script:
 
 ```powershell
-# https://viteplus.dev/install.ps1
+# https://vite.plus/ps1
 #
 # Environment variables:
 #   VITE_PLUS_VERSION - Version to install (default: latest)
@@ -825,7 +825,7 @@ See [`packages/global/install.ps1`](../packages/global/install.ps1) for the full
 1. **PowerShell one-liner:**
 
    ```powershell
-   irm https://viteplus.dev/install.ps1 | iex
+   irm https://vite.plus/ps1 | iex
    ```
 
 2. **npm (if Node.js is available):**
@@ -1168,7 +1168,7 @@ Rewriting these in Rust would be significant effort with limited benefit. Instea
 - run: npm install -g vite-plus-cli
 
 # After (recommended)
-- run: curl -fsSL https://viteplus.dev/install.sh | bash
+- run: curl -fsSL https://vite.plus | bash
 # or
 - uses: voidzero-dev/setup-vite-plus-action@v1
 ```
diff --git a/rfcs/init-editor-configs.md b/rfcs/init-editor-configs.md
index b0efa4065b..796b42e8ab 100644
--- a/rfcs/init-editor-configs.md
+++ b/rfcs/init-editor-configs.md
@@ -54,7 +54,7 @@ Based on [oxc-vscode's own `.vscode/settings.json`](https://github.com/oxc-proje
 
 ```json
 {
-  "recommendations": ["oxc.oxc-vscode"]
+  "recommendations": ["VoidZero.vite-plus-extension-pack"]
 }
 ```
 
diff --git a/rfcs/merge-global-and-local-cli.md b/rfcs/merge-global-and-local-cli.md
index b12a2d9d80..548d928b8b 100644
--- a/rfcs/merge-global-and-local-cli.md
+++ b/rfcs/merge-global-and-local-cli.md
@@ -89,7 +89,7 @@ This decouples the `vp` binary from vite-plus's internal file layout.
 
 **Install flows:**
 
-- **Production** (`curl -fsSL https://viteplus.dev/install.sh | bash`):
+- **Production** (`curl -fsSL https://vite.plus | bash`):
   Downloads CLI platform tarball from `@voidzero-dev/vite-plus-cli-{platform}` (extracts only `vp` binary),
   generates wrapper `package.json`, runs `vp install --silent` which installs `vite-plus` + all transitive deps via npm.
 
diff --git a/rfcs/upgrade-command.md b/rfcs/upgrade-command.md
index 786bc06b86..ba77076c96 100644
--- a/rfcs/upgrade-command.md
+++ b/rfcs/upgrade-command.md
@@ -6,7 +6,7 @@ Draft
 
 ## Background
 
-Vite+ is distributed as a standalone Rust binary via bash installation (`curl -fsSL https://viteplus.dev/install.sh | bash`). Currently, users must re-run the full install script to update to a new version. This is friction-heavy and unfamiliar to users who expect a built-in update mechanism (like `rustup update`, `volta fetch`, or `brew upgrade`).
+Vite+ is distributed as a standalone Rust binary via bash installation (`curl -fsSL https://vite.plus | bash`). Currently, users must re-run the full install script to update to a new version. This is friction-heavy and unfamiliar to users who expect a built-in update mechanism (like `rustup update`, `volta fetch`, or `brew upgrade`).
 
 A native `vp upgrade` command would allow users to update the CLI in-place with a single command, improving the upgrade experience significantly.