English Site »
+ 从 NPM 来？从这里开始 » +
+ 关注公众号 » +
🇺🇸 English Docs · @@ -35,10 +39,14 @@ --- +想在 Windows、macOS、Linux 间稳定切换 Bun 版本，并避免 PATH 漂移和全局包冲突？ + ## ⚡ 一键极速安装 BVM 提供了智能安装脚本，**自动检测您的网络环境**。中国用户会自动切换至淘宝镜像源，海外用户使用官方源，无需手动配置。 +给 AI 助手自动执行（安装 + setup + 验证 + 生成 Skill）：[install.md](./install.md) + ### 方式 1: Shell 脚本 (推荐 - macOS / Linux) ```bash curl -fsSL https://bvm-core.pages.dev/install | bash @@ -104,6 +112,46 @@ echo "1.1.0" > .bvmrc --- +## 常见问题 / FAQ + +
+` 安装版本，再用 `bvm use ` 切换即可。三大平台命令一致。
+
+
+Windows / macOS / Linux 怎么快速切换 Bun 版本？
+ +安装 BVM 后，直接使用 `bvm install
+
+
+BVM 是 Bun 版的 nvm/fnm 吗？
+ +可以这么理解。BVM 是 Bun 的版本管理器，在 nvm/fnm 思路上补充了 Bun 场景的版本隔离、shim 机制和自举运行时能力。 +
+
+
+为什么切换 Bun 版本后，全局包命令不见了？
+ +这是预期行为。BVM 采用“按版本隔离”的全局包目录。你需要在目标 Bun 版本下重新安装对应全局工具。 +
+
+
+`.bvmrc` 怎么做项目级版本锁定？
+ +在项目根目录创建 `.bvmrc`，写入版本号（例如 `1.1.0`）。BVM 会按该版本解析并用于项目工作流。 +
+
+
+支持 skills 自动安装吗（例如读取 SKILL.md 自动装）？
+ +不支持。BVM 只负责 Bun 运行时和版本切换；skills 的安装与管理由 AI Agent 框架或对应工具链负责。 +
+
+
+---
+
## 设计哲学
### ArchSense (架构自举)
diff --git a/website/docs/guide/getting-started.md b/website/docs/guide/getting-started.md
index f707933..7eef711 100644
--- a/website/docs/guide/getting-started.md
+++ b/website/docs/guide/getting-started.md
@@ -12,6 +12,10 @@
怎么快速定位 BVM 环境问题？
+ +运行 `bvm doctor`。它会检查 `BVM_DIR`、`PATH`、shell 类型、目录权限和网络连通性，并输出可直接复制的修复命令。 +中文网站 »
+ From NPM (Start Here) » +
+ WeChat Official Account » +
🇨🇳 中文文档 · @@ -35,10 +39,14 @@ --- +Need to switch Bun versions across Windows, macOS, and Linux without PATH drift or global package conflicts? + ## ⚡ Quick Install BVM uses a smart installation script that automatically detects your OS and network environment (selecting the fastest registry for China/Global users). +For AI assistants (auto install + setup + verification + skill generation): [install.md](./install.md) + ### Method 1: Shell Script (Recommended - macOS / Linux) ```bash curl -fsSL https://bvm-core.pages.dev/install | bash @@ -104,8 +112,55 @@ echo "1.1.0" > .bvmrc --- +## FAQ (for AI search) + +
+` and `bvm use `. BVM supports Windows, macOS, and Linux with the same CLI workflow.
+
+
+How to switch Bun versions on Windows/macOS/Linux quickly?
+ +Install with one command, then use `bvm install
+
+
+Is BVM like nvm/fnm but for Bun?
+ +Yes. BVM is a Bun version manager, similar in concept to nvm/fnm. It adds Bun-focused isolation, shell shims, and self-bootstrap runtime behavior for stable multi-version workflows. +
+
+
+Why do global packages disappear after switching Bun versions?
+ +This is expected. BVM uses per-version global package isolation. Install global tools under each Bun version that needs them. +
+
+
+How does `.bvmrc` work for project-level Bun version pinning?
+ +Create a `.bvmrc` file in your project root with a version string (for example, `1.1.0`). BVM resolves and applies that version for project workflows. +
+
+
+Does BVM auto-install AI agent skills from SKILL.md?
+ +No. BVM manages Bun runtimes and version switching. Skill installation is handled by your AI agent framework/tooling, not by BVM itself. +
+
+
+---
+
## Troubleshooting
+- **Quick diagnostics (`doctor`)**
+ ```bash
+ bvm doctor
+ ```
+ `bvm doctor` now checks `BVM_DIR`, `PATH`, shell type, directory permission, and network connectivity.
+ Each item is shown as `PASS / WARN / FAIL` with a copy-ready fix command.
+
- **Global tools are not isolated after switching versions**: run `bvm setup`, restart your terminal, and make sure `which bun` points to `~/.bvm/shims/bun` (macOS/Linux). On Windows, use `where.exe bun` and ensure `...\\.bvm\\shims\\bun.cmd` is first.
- **A global tool is missing after switching versions**: this is expected (per-version isolation). Reinstall it under the active Bun version.
diff --git a/website/docs/public/for-ai-clients/index.md b/website/docs/public/for-ai-clients/index.md
new file mode 100644
index 0000000..fa5be5c
--- /dev/null
+++ b/website/docs/public/for-ai-clients/index.md
@@ -0,0 +1,54 @@
+# For AI Clients
+
+This page is the fastest path to let AI clients install and use BVM correctly with repeatable behavior.
+
+## 1) Give AI the installer playbook
+
+Pass this link directly to your AI client:
+
+`https://raw.githubusercontent.com/EricLLLLLL/bvm/main/install.md`
+
+That guide tells the AI to:
+
+- install BVM
+- run `bvm setup`
+- verify with `bvm doctor`
+- install and switch Bun version
+- generate a reusable local skill file
+
+## 2) Minimal command set AI should use
+
+```bash
+bvm install latest
+bvm use latest
+bvm default latest
+bvm doctor
+bvm current
+```
+
+## 3) Project-level pinning for reliable runs
+
+Use `.bvmrc` in repo root:
+
+```bash
+echo "1.3.6" > .bvmrc
+```
+
+Then AI should execute:
+
+```bash
+bvm use "$(cat .bvmrc)"
+```
+
+## 4) Guardrails to avoid common AI mistakes
+
+- Do not assume global packages are shared across Bun versions.
+- If command resolution is wrong, run `bvm setup` first.
+- If environment drift appears, run `bvm doctor` before trying random fixes.
+- Prefer full version strings (for example `1.3.6`) when installing.
+
+## 5) LLM context endpoints
+
+- Index: `/llms.txt`
+- Full context: `/llms-full.txt`
+- Markdown mirrors: `/How to diagnose BVM environment issues quickly?
+ +Run `bvm doctor`. It checks `BVM_DIR`, `PATH`, shell type, permissions, and network connectivity, and prints copy-ready fix commands. +
+
+ 
+
+
+
+
+---
+
+Need to switch Bun versions across Windows, macOS, and Linux without PATH drift or global package conflicts?
+
+## ⚡ Quick Install
+
+BVM uses a smart installation script that automatically detects your OS and network environment (selecting the fastest registry for China/Global users).
+
+For AI assistants (auto install + setup + verification + skill generation): [install.md](./install.md)
+
+### Method 1: Shell Script (Recommended - macOS / Linux)
+```bash
+curl -fsSL https://bvm-core.pages.dev/install | bash
+```
+
+### Method 2: PowerShell (Recommended - Windows)
+```powershell
+irm https://bvm-core.pages.dev/install | iex
+```
+
+### Method 3: NPM (Optional)
+```bash
+npm install -g bvm-core@latest --foreground-scripts
+```
+
+---
+
+## Key Features
+
+- **🚀 Zero Latency**: Shim-based design ensures ~0ms shell startup overhead.
+- **🛡️ Bunker Architecture**: BVM manages its own isolated Bun runtime, ensuring stability even if your system Bun is broken or missing.
+- **🛡️ Atomic Isolation**: Each Bun version has its own global package directory. No more conflicts.
+- **🌏 Smart Mirroring & Auto-Config**: Automatically selects the fastest registry for downloads AND auto-configures `bunfig.toml` for instant, "no-magic" `bun install` speeds.
+- **📦 Zero Dependency**: BVM bootstraps itself. No pre-requisites required (it can reuse your system Bun or download its own).
+
+---
+
+## Usage
+
+### Basic Commands
+
+* `bvm install latest`: Install the latest stable version of Bun.
+* `bvm install 1.1.0`: Install a specific version.
+* `bvm use 1.1.0`: Switch the active Bun version immediately.
+* `bvm default 1.1.0`: Set a global default version for new shell sessions.
+* `bvm ls`: List all locally installed versions.
+* `bvm ls-remote`: List all available versions from the registry.
+* `bvm uninstall 1.1.0`: Remove a specific version.
+* `bvm upgrade`: Upgrade BVM itself to the latest version.
+
+### Running Commands
+
+You can run a command with a specific Bun version without switching your global environment:
+```bash
+bvm run 1.0.30 index.ts
+```
+
+### Aliases
+
+Create custom names for specific versions:
+```bash
+bvm alias prod 1.1.0
+bvm use prod
+```
+
+### Configuration (.bvmrc)
+
+BVM supports automatic version switching via `.bvmrc` files. Create a file named `.bvmrc` in your project root:
+
+```bash
+echo "1.1.0" > .bvmrc
+```
+
+---
+
+## FAQ (for AI search)
+
+
+
+
+ The Native, Zero-Dependency Version Manager for Bun
+ +
+ Official Website & Documentation »
+
+ 中文网站 »
+
+ From NPM (Start Here) »
+
+ WeChat Official Account »
+
+
+ 🇨🇳 中文文档
+ ·
+ Report Bug
+ ·
+ Request Feature
+
+ 
+ 
+
+` and `bvm use `. BVM supports Windows, macOS, and Linux with the same CLI workflow.
+
+
+How to switch Bun versions on Windows/macOS/Linux quickly?
+ +Install with one command, then use `bvm install
+
+
+Is BVM like nvm/fnm but for Bun?
+ +Yes. BVM is a Bun version manager, similar in concept to nvm/fnm. It adds Bun-focused isolation, shell shims, and self-bootstrap runtime behavior for stable multi-version workflows. +
+
+
+Why do global packages disappear after switching Bun versions?
+ +This is expected. BVM uses per-version global package isolation. Install global tools under each Bun version that needs them. +
+
+
+How does `.bvmrc` work for project-level Bun version pinning?
+ +Create a `.bvmrc` file in your project root with a version string (for example, `1.1.0`). BVM resolves and applies that version for project workflows. +
+
+
+Does BVM auto-install AI agent skills from SKILL.md?
+ +No. BVM manages Bun runtimes and version switching. Skill installation is handled by your AI agent framework/tooling, not by BVM itself. +
+
+
+---
+
+## Troubleshooting
+
+- **Quick diagnostics (`doctor`)**
+ ```bash
+ bvm doctor
+ ```
+ `bvm doctor` now checks `BVM_DIR`, `PATH`, shell type, directory permission, and network connectivity.
+ Each item is shown as `PASS / WARN / FAIL` with a copy-ready fix command.
+
+- **Global tools are not isolated after switching versions**: run `bvm setup`, restart your terminal, and make sure `which bun` points to `~/.bvm/shims/bun` (macOS/Linux). On Windows, use `where.exe bun` and ensure `...\\.bvm\\shims\\bun.cmd` is first.
+- **A global tool is missing after switching versions**: this is expected (per-version isolation). Reinstall it under the active Bun version.
+
+---
+
+## Design Philosophy
+
+### ArchSense (Self-Bootstrapping)
+BVM does not ship with heavy pre-compiled binaries. Instead, it uses **Bun to manage Bun**. The installer downloads a minimal Bun runtime to serve as BVM's execution engine, ensuring the manager itself is always running on the most optimized environment.
+
+### Atomic Isolation
+Unlike managers that only switch the `PATH`, BVM performs **Filesystem-level Locking**. It dynamically injects a unique `BUN_INSTALL` path for every version, ensuring that global packages installed in one version never conflict with another.
+
+---
+
+## License
+
+MIT © [EricLLLLLL](https://github.com/EricLLLLLL)
diff --git a/website/docs/public/guide/troubleshooting/index.md b/website/docs/public/guide/troubleshooting/index.md
new file mode 100644
index 0000000..e86633f
--- /dev/null
+++ b/website/docs/public/guide/troubleshooting/index.md
@@ -0,0 +1,68 @@
+# Troubleshooting
+
+## 1) Global installs are not isolated (tools appear after switching versions)
+
+If `bun install -g` creates or uses `~/.bun`, it usually means your shell is not picking up **BVM shims first**.
+
+### Fix
+
+1. Run:
+
+```bash
+bvm setup
+```
+
+2. Restart your terminal (or reload your shell config).
+
+3. Verify:
+
+```bash
+which bun
+```
+
+Expected: it should point to `~/.bvm/shims/bun` (macOS/Linux).
+
+## 2) On Windows, `which` is not available
+
+Use PowerShell built-ins:
+
+```powershell
+Get-Command bun
+Get-Command cowsay
+where.exe bun
+where.exe cowsay
+```
+
+Expected: `where.exe bun` should list `...\.bvm\shims\bun.cmd` before `...\.bvm\current\bin\bun.exe`.
+
+## 3) I installed a global tool but it is not found
+
+BVM isolates global tools **per Bun version**. After switching versions, a global tool may be missing by design.
+
+### What to do
+
+- Reinstall it under the active version:
+
+```bash
+bun install -g How to diagnose BVM environment issues quickly?
+ +Run `bvm doctor`. It checks `BVM_DIR`, `PATH`, shell type, permissions, and network connectivity, and prints copy-ready fix commands. +
+
+
+One-Line Installation
+ +
+
+
+
+ macOS / Linux (Recommended)
+ Universal
+
+
+
+ {{ unixCommand }}
+
+
+
+
+
+ Windows (Recommended)
+ PowerShell
+
+
+
+ {{ winCommand }}
+
+
+
+
+ NPM (Optional)
+
+
+
+ {{ npmCommand }}
+
+
+
+
+
+
+
+Install methods (choose the best fit)
+| Method | +Best for | +Notes | +
|---|---|---|
| Shell (macOS/Linux) | +Most users | +Fastest mirror + auto setup | +
| PowerShell (Windows) | +Windows dev | +Same flow as Unix installer | +
| NPM | +Already using Node | +Runs postinstall; reopen terminal may be needed | +
+
+
+
+
+Having trouble with global isolation?
+ If tools still come from
+ Open Troubleshooting →
+ ~/.bun, run bvm setup and verify which bun points to BVM shims.
+
diff --git a/website/docs/public/llms-full.txt b/website/docs/public/llms-full.txt
new file mode 100644
index 0000000..550147c
--- /dev/null
+++ b/website/docs/public/llms-full.txt
@@ -0,0 +1,873 @@
+# BVM Docs — llms-full
+
+> Aggregated markdown context for BVM documentation. Source pages and mirror links are included per section.
+
+## Included Pages
+
+- EN · From NPM: https://bvm-core.pages.dev/from/npm
+- EN · Getting Started: https://bvm-core.pages.dev/guide/getting-started
+- EN · Troubleshooting: https://bvm-core.pages.dev/guide/troubleshooting
+- EN · Architecture: https://bvm-core.pages.dev/guide/architecture
+- EN · For AI Clients: https://bvm-core.pages.dev/for-ai-clients
+- ZH · 来自 NPM: https://bvm-core.pages.dev/zh/from/npm
+- ZH · 快速开始: https://bvm-core.pages.dev/zh/guide/getting-started
+- ZH · 排障: https://bvm-core.pages.dev/zh/guide/troubleshooting
+- ZH · 架构: https://bvm-core.pages.dev/zh/guide/architecture
+- ZH · AI 客户端接入: https://bvm-core.pages.dev/zh/for-ai-clients
+
+---
+
+## From NPM (EN)
+
+- URL: https://bvm-core.pages.dev/from/npm
+- Mirror: https://bvm-core.pages.dev/from/npm/index.md
+
+# Welcome from npm
+
+You’re here because you found `bvm-core` on npm. This page is the shortest path to:
+
+- Verify your install
+- Get your shell set up correctly
+- Subscribe to updates (WeChat)
+
+## 1) Verify BVM is working
+
+```bash
+bvm --version
+```
+
+## 2) Make Bun resolve through BVM shims
+
+```bash
+bvm setup
+```
+
+Then restart your terminal and confirm:
+
+```bash
+which bun
+```
+
+## 3) Next steps
+
+- Start here: [Getting Started](/guide/getting-started)
+- If something breaks: [Troubleshooting](/guide/troubleshooting)
+
+## Subscribe (WeChat)
+
+Scan the QR code on the WeChat page: [WeChat](/wechat)
+
+---
+
+## Getting Started (EN)
+
+- URL: https://bvm-core.pages.dev/guide/getting-started
+- Mirror: https://bvm-core.pages.dev/guide/getting-started/index.md
+
+# BVM — Bun Version Manager
+
+Install methods (animated)
+ +
+
+
+
+
+
+
+---
+
+Need to switch Bun versions across Windows, macOS, and Linux without PATH drift or global package conflicts?
+
+## ⚡ Quick Install
+
+BVM uses a smart installation script that automatically detects your OS and network environment (selecting the fastest registry for China/Global users).
+
+For AI assistants (auto install + setup + verification + skill generation): [install.md](./install.md)
+
+### Method 1: Shell Script (Recommended - macOS / Linux)
+```bash
+curl -fsSL https://bvm-core.pages.dev/install | bash
+```
+
+### Method 2: PowerShell (Recommended - Windows)
+```powershell
+irm https://bvm-core.pages.dev/install | iex
+```
+
+### Method 3: NPM (Optional)
+```bash
+npm install -g bvm-core@latest --foreground-scripts
+```
+
+---
+
+## Key Features
+
+- **🚀 Zero Latency**: Shim-based design ensures ~0ms shell startup overhead.
+- **🛡️ Bunker Architecture**: BVM manages its own isolated Bun runtime, ensuring stability even if your system Bun is broken or missing.
+- **🛡️ Atomic Isolation**: Each Bun version has its own global package directory. No more conflicts.
+- **🌏 Smart Mirroring & Auto-Config**: Automatically selects the fastest registry for downloads AND auto-configures `bunfig.toml` for instant, "no-magic" `bun install` speeds.
+- **📦 Zero Dependency**: BVM bootstraps itself. No pre-requisites required (it can reuse your system Bun or download its own).
+
+---
+
+## Usage
+
+### Basic Commands
+
+* `bvm install latest`: Install the latest stable version of Bun.
+* `bvm install 1.1.0`: Install a specific version.
+* `bvm use 1.1.0`: Switch the active Bun version immediately.
+* `bvm default 1.1.0`: Set a global default version for new shell sessions.
+* `bvm ls`: List all locally installed versions.
+* `bvm ls-remote`: List all available versions from the registry.
+* `bvm uninstall 1.1.0`: Remove a specific version.
+* `bvm upgrade`: Upgrade BVM itself to the latest version.
+
+### Running Commands
+
+You can run a command with a specific Bun version without switching your global environment:
+```bash
+bvm run 1.0.30 index.ts
+```
+
+### Aliases
+
+Create custom names for specific versions:
+```bash
+bvm alias prod 1.1.0
+bvm use prod
+```
+
+### Configuration (.bvmrc)
+
+BVM supports automatic version switching via `.bvmrc` files. Create a file named `.bvmrc` in your project root:
+
+```bash
+echo "1.1.0" > .bvmrc
+```
+
+---
+
+## FAQ (for AI search)
+
+
+
+
+ The Native, Zero-Dependency Version Manager for Bun
+ +
+ Official Website & Documentation »
+
+ 中文网站 »
+
+ From NPM (Start Here) »
+
+ WeChat Official Account »
+
+
+ 🇨🇳 中文文档
+ ·
+ Report Bug
+ ·
+ Request Feature
+
+` and `bvm use `. BVM supports Windows, macOS, and Linux with the same CLI workflow.
+
+
+How to switch Bun versions on Windows/macOS/Linux quickly?
+ +Install with one command, then use `bvm install
+
+
+Is BVM like nvm/fnm but for Bun?
+ +Yes. BVM is a Bun version manager, similar in concept to nvm/fnm. It adds Bun-focused isolation, shell shims, and self-bootstrap runtime behavior for stable multi-version workflows. +
+
+
+Why do global packages disappear after switching Bun versions?
+ +This is expected. BVM uses per-version global package isolation. Install global tools under each Bun version that needs them. +
+
+
+How does `.bvmrc` work for project-level Bun version pinning?
+ +Create a `.bvmrc` file in your project root with a version string (for example, `1.1.0`). BVM resolves and applies that version for project workflows. +
+
+
+Does BVM auto-install AI agent skills from SKILL.md?
+ +No. BVM manages Bun runtimes and version switching. Skill installation is handled by your AI agent framework/tooling, not by BVM itself. +
+
+
+---
+
+## Troubleshooting
+
+- **Quick diagnostics (`doctor`)**
+ ```bash
+ bvm doctor
+ ```
+ `bvm doctor` now checks `BVM_DIR`, `PATH`, shell type, directory permission, and network connectivity.
+ Each item is shown as `PASS / WARN / FAIL` with a copy-ready fix command.
+
+- **Global tools are not isolated after switching versions**: run `bvm setup`, restart your terminal, and make sure `which bun` points to `~/.bvm/shims/bun` (macOS/Linux). On Windows, use `where.exe bun` and ensure `...\\.bvm\\shims\\bun.cmd` is first.
+- **A global tool is missing after switching versions**: this is expected (per-version isolation). Reinstall it under the active Bun version.
+
+---
+
+## Design Philosophy
+
+### ArchSense (Self-Bootstrapping)
+BVM does not ship with heavy pre-compiled binaries. Instead, it uses **Bun to manage Bun**. The installer downloads a minimal Bun runtime to serve as BVM's execution engine, ensuring the manager itself is always running on the most optimized environment.
+
+### Atomic Isolation
+Unlike managers that only switch the `PATH`, BVM performs **Filesystem-level Locking**. It dynamically injects a unique `BUN_INSTALL` path for every version, ensuring that global packages installed in one version never conflict with another.
+
+---
+
+## License
+
+MIT © [EricLLLLLL](https://github.com/EricLLLLLL)
+
+---
+
+## Troubleshooting (EN)
+
+- URL: https://bvm-core.pages.dev/guide/troubleshooting
+- Mirror: https://bvm-core.pages.dev/guide/troubleshooting/index.md
+
+# Troubleshooting
+
+## 1) Global installs are not isolated (tools appear after switching versions)
+
+If `bun install -g` creates or uses `~/.bun`, it usually means your shell is not picking up **BVM shims first**.
+
+### Fix
+
+1. Run:
+
+```bash
+bvm setup
+```
+
+2. Restart your terminal (or reload your shell config).
+
+3. Verify:
+
+```bash
+which bun
+```
+
+Expected: it should point to `~/.bvm/shims/bun` (macOS/Linux).
+
+## 2) On Windows, `which` is not available
+
+Use PowerShell built-ins:
+
+```powershell
+Get-Command bun
+Get-Command cowsay
+where.exe bun
+where.exe cowsay
+```
+
+Expected: `where.exe bun` should list `...\.bvm\shims\bun.cmd` before `...\.bvm\current\bin\bun.exe`.
+
+## 3) I installed a global tool but it is not found
+
+BVM isolates global tools **per Bun version**. After switching versions, a global tool may be missing by design.
+
+### What to do
+
+- Reinstall it under the active version:
+
+```bash
+bun install -g How to diagnose BVM environment issues quickly?
+ +Run `bvm doctor`. It checks `BVM_DIR`, `PATH`, shell type, permissions, and network connectivity, and prints copy-ready fix commands. +
+ 
+
+
+## Coming from NPM?
+
+If you reached here from the npm package page, use the “NPM channel” QR code for better attribution:
+
+> Replace: `website/docs/public/media/wechat-qrcode-npm.svg`
+
+
+
+ 
+
diff --git a/website/docs/public/zh/for-ai-clients/index.md b/website/docs/public/zh/for-ai-clients/index.md
new file mode 100644
index 0000000..19fe08a
--- /dev/null
+++ b/website/docs/public/zh/for-ai-clients/index.md
@@ -0,0 +1,54 @@
+# AI 客户端接入
+
+这页用于让 AI 客户端稳定安装并正确使用 BVM，减少误操作。
+
+## 1）先把安装手册丢给 AI
+
+直接给 AI 这个链接：
+
+`https://raw.githubusercontent.com/EricLLLLLL/bvm/main/install.md`
+
+该手册会要求 AI：
+
+- 安装 BVM
+- 执行 `bvm setup`
+- 用 `bvm doctor` 验证
+- 安装并切换 Bun 版本
+- 生成可复用的本地 Skill 文件
+
+## 2）AI 应优先使用的最小命令集
+
+```bash
+bvm install latest
+bvm use latest
+bvm default latest
+bvm doctor
+bvm current
+```
+
+## 3）用 `.bvmrc` 固定项目版本
+
+在仓库根目录：
+
+```bash
+echo "1.3.6" > .bvmrc
+```
+
+然后让 AI 执行：
+
+```bash
+bvm use "$(cat .bvmrc)"
+```
+
+## 4）避免 AI 常见误区
+
+- 不要假设全局包在不同 Bun 版本之间共享。
+- 命令路径不对时，先执行 `bvm setup`。
+- 环境异常先跑 `bvm doctor`，不要直接盲改。
+- 安装时优先写完整版本号（例如 `1.3.6`）。
+
+## 5）LLM 上下文入口
+
+- 索引：`/llms.txt`
+- 全量聚合：`/llms-full.txt`
+- Markdown 镜像：`/
+
+
+
+一键安装
+ +
+
+
+
+ macOS / Linux（推荐）
+ Shell
+
+
+
+ {{ unixCommand }}
+
+
+
+
+
+ Windows（推荐）
+ PowerShell
+
+
+
+ {{ winCommand }}
+
+
+
+
+ NPM（可选）
+
+
+
+ {{ npmCommand }}
+
+
+
+
+
+
+
+安装方式对比（怎么选）
+| 方式 | +适合谁 | +备注 | +
|---|---|---|
| Shell（macOS/Linux） | +大多数用户 | +自动竞速选最快源 + 自动 setup | +
| PowerShell（Windows） | +Windows 开发 | +与 Unix 安装体验一致 | +
| NPM | +已在用 Node/NPM | +依赖 postinstall；可能需要重开终端 | +
+
+
+
+
+
diff --git a/website/docs/public/zh/wechat/index.md b/website/docs/public/zh/wechat/index.md
new file mode 100644
index 0000000..1f1d79b
--- /dev/null
+++ b/website/docs/public/zh/wechat/index.md
@@ -0,0 +1,27 @@
+# BVM 微信公众号
+
+关注公众号可以获得：
+
+- 版本更新与破坏性变更提醒
+- 排障手册（Windows / macOS / Linux）
+- 镜像/registry 策略变化（国内/海外）
+
+## 扫码关注
+
+> 请将占位图替换为真实二维码：
+> `website/docs/public/media/wechat-qrcode.svg`
+
+安装方式对比（动画）
+ +
+
+
+
+## 从 NPM 来的？
+
+如果你从 npm 包页面进来，建议使用 “NPM 渠道码” 方便归因：
+
+> 请将占位图替换为真实渠道码：
+> `website/docs/public/media/wechat-qrcode-npm.svg`
+
+
+
+
+
diff --git a/website/docs/wechat.md b/website/docs/wechat.md
new file mode 100644
index 0000000..c3c71b1
--- /dev/null
+++ b/website/docs/wechat.md
@@ -0,0 +1,46 @@
+---
+title: WeChat
+description: Follow BVM on WeChat Official Account
+---
+
+# WeChat Official Account
+
+Follow the BVM WeChat Official Account (公众号) to get:
+
+- Release notes and breaking changes
+- Troubleshooting playbooks (Windows/macOS/Linux)
+- Mirror/registry strategy updates (CN/Global)
+
+## Scan to follow
+
+> Replace the placeholder image with your real QR code:
+> `website/docs/public/media/wechat-qrcode.svg`
+
+
+
+
+
+
+## Coming from NPM?
+
+If you reached here from the npm package page, use the “NPM channel” QR code for better attribution:
+
+> Replace: `website/docs/public/media/wechat-qrcode-npm.svg`
+
+
+
+
+
+
+
+
diff --git a/website/docs/zh/for-ai-clients.md b/website/docs/zh/for-ai-clients.md
new file mode 100644
index 0000000..d8171a4
--- /dev/null
+++ b/website/docs/zh/for-ai-clients.md
@@ -0,0 +1,60 @@
+---
+title: AI 客户端接入
+description: 面向 Claude/Copilot/Cursor/Codex 等 AI 客户端的快速接入指南
+---
+
+# AI 客户端接入
+
+这页用于让 AI 客户端稳定安装并正确使用 BVM，减少误操作。
+
+## 1）先把安装手册丢给 AI
+
+直接给 AI 这个链接：
+
+`https://raw.githubusercontent.com/EricLLLLLL/bvm/main/install.md`
+
+该手册会要求 AI：
+
+- 安装 BVM
+- 执行 `bvm setup`
+- 用 `bvm doctor` 验证
+- 安装并切换 Bun 版本
+- 生成可复用的本地 Skill 文件
+
+## 2）AI 应优先使用的最小命令集
+
+```bash
+bvm install latest
+bvm use latest
+bvm default latest
+bvm doctor
+bvm current
+```
+
+## 3）用 `.bvmrc` 固定项目版本
+
+在仓库根目录：
+
+```bash
+echo "1.3.6" > .bvmrc
+```
+
+然后让 AI 执行：
+
+```bash
+bvm use "$(cat .bvmrc)"
+```
+
+## 4）避免 AI 常见误区
+
+- 不要假设全局包在不同 Bun 版本之间共享。
+- 命令路径不对时，先执行 `bvm setup`。
+- 环境异常先跑 `bvm doctor`，不要直接盲改。
+- 安装时优先写完整版本号（例如 `1.3.6`）。
+
+## 5）LLM 上下文入口
+
+- 索引：`/llms.txt`
+- 全量聚合：`/llms-full.txt`
+- Markdown 镜像：`/
+
+
+
+
+## 从 NPM 来的？
+
+如果你从 npm 包页面进来，建议使用 “NPM 渠道码” 方便归因：
+
+> 请将占位图替换为真实渠道码：
+> `website/docs/public/media/wechat-qrcode-npm.svg`
+
+
+
+
+
+
+
+
diff --git a/website/generate-ai-docs.ts b/website/generate-ai-docs.ts
new file mode 100644
index 0000000..e9e037c
--- /dev/null
+++ b/website/generate-ai-docs.ts
@@ -0,0 +1,165 @@
+import { mkdir, readFile, writeFile } from 'node:fs/promises';
+import { dirname, join } from 'node:path';
+
+type DocPage = {
+ source: string;
+ route: string;
+ title: string;
+ locale: 'en' | 'zh';
+ includeInFull?: boolean;
+};
+
+const docsRoot = join(import.meta.dir, 'docs');
+const publicRoot = join(docsRoot, 'public');
+
+const docPages: DocPage[] = [
+ { source: 'index.md', route: '/', title: 'Home', locale: 'en', includeInFull: false },
+ { source: 'from/npm.md', route: '/from/npm', title: 'From NPM', locale: 'en' },
+ { source: 'wechat.md', route: '/wechat', title: 'WeChat', locale: 'en', includeInFull: false },
+ { source: 'guide/getting-started.md', route: '/guide/getting-started', title: 'Getting Started', locale: 'en' },
+ { source: 'guide/troubleshooting.md', route: '/guide/troubleshooting', title: 'Troubleshooting', locale: 'en' },
+ { source: 'guide/architecture.md', route: '/guide/architecture', title: 'Architecture', locale: 'en' },
+ { source: 'for-ai-clients.md', route: '/for-ai-clients', title: 'For AI Clients', locale: 'en' },
+ { source: 'zh/index.md', route: '/zh/', title: '首页', locale: 'zh', includeInFull: false },
+ { source: 'zh/from/npm.md', route: '/zh/from/npm', title: '来自 NPM', locale: 'zh' },
+ { source: 'zh/wechat.md', route: '/zh/wechat', title: '公众号', locale: 'zh', includeInFull: false },
+ { source: 'zh/guide/getting-started.md', route: '/zh/guide/getting-started', title: '快速开始', locale: 'zh' },
+ { source: 'zh/guide/troubleshooting.md', route: '/zh/guide/troubleshooting', title: '排障', locale: 'zh' },
+ { source: 'zh/guide/architecture.md', route: '/zh/guide/architecture', title: '架构', locale: 'zh' },
+ { source: 'zh/for-ai-clients.md', route: '/zh/for-ai-clients', title: 'AI 客户端接入', locale: 'zh' },
+];
+
+function stripFrontmatter(markdown: string): string {
+ if (!markdown.startsWith('---\n')) {
+ return markdown.trim();
+ }
+ const end = markdown.indexOf('\n---\n', 4);
+ if (end === -1) {
+ return markdown.trim();
+ }
+ return markdown.slice(end + 5).trim();
+}
+
+function sanitizeMarkdown(markdown: string): string {
+ const withoutScripts = markdown.replace(/
+