@ant-design/cli 6.4.2 → 6.4.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ant-design/cli",
-  "version": "6.4.2",
+  "version": "6.4.4",
   "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
   "type": "module",
   "bin": {
@@ -44,17 +44,23 @@
   },
   "overrides": {
     "fast-uri": "^3.1.2",
-    "hono": "^4.12.18",
+    "hono": "^4.12.23",
     "ip-address": "^10.1.1"
   },
   "dependencies": {
-    "oxc-parser": "^0.130.0"
+    "fast-glob": "^3.3.3",
+    "fast-levenshtein": "^3.0.0",
+    "oxc-parser": "^0.134.0",
+    "semver": "^7.8.0",
+    "string-width": "^8.2.1"
   },
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
+    "@types/fast-levenshtein": "^0.0.4",
     "@types/node": "^25.5.0",
+    "@types/semver": "^7.7.1",
     "@vitest/coverage-v8": "^4.1.2",
-    "commander": "^14.0.3",
+    "commander": "^15.0.0",
     "conf": "^15.1.0",
     "env-paths": "^4.0.0",
     "envinfo": "^7.21.0",

package/skills/antd/SKILL.md

@@ -9,13 +9,14 @@ allowed-tools:
   - Bash(antd *)
   - Bash(antd bug*)
   - Bash(antd bug-cli*)
+  - Bash(antd upgrade*)
   - Bash(npm install -g @ant-design/cli*)
   - Bash(which antd)
 ---
 
 # Ant Design CLI
 
-You have access to `@ant-design/cli` — a local CLI tool with bundled antd metadata for v3/v4/v5/v6. Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
+You have access to `@ant-design/cli` — a local CLI tool with bundled antd metadata for v4/v5/v6 (plus migration guides for v3 → v4, v4 → v5, v5 → v6). Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
 
 ## Setup
 
@@ -25,7 +26,7 @@ Before first use, check if the CLI is installed. If not, install it automaticall
 which antd || npm install -g @ant-design/cli
 ```
 
-After running any command, if the output contains an "Update available" notice, run `npm install -g @ant-design/cli` to update before continuing.
+After running any command, if the output contains an "Update available" notice, run `antd upgrade` to update before continuing.
 
 
 **Always use `--format json` for structured output you can parse programmatically.**
@@ -48,6 +49,9 @@ antd semantic Button --format json
 
 # Check component-level design tokens for theming
 antd token Button --format json
+
+# Get the overall design language (design.md): colors, typography, spacing, radius + principles
+antd design.md --format json
 ```
 
 **Workflow:** `antd info` → understand props → `antd demo` → grab a working example → write code.
@@ -93,6 +97,9 @@ antd migrate 4 5 --format json    # v4 → v5
 # Check migration for a specific component
 antd migrate 4 5 --component Select --format json
 
+# Generate agent-friendly auto-migration prompt (does not modify files)
+antd migrate 4 5 --apply ./src --format json
+
 # See what changed between two versions
 antd changelog 4.24.0 5.0.0 --format json
 
@@ -218,7 +225,18 @@ antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
 
 **Opt-out:** If the environment variable `ANTD_NO_AUTO_REPORT=1` is set, skip all bug-reporting suggestions entirely — do not suggest `antd bug` or `antd bug-cli` unless the user directly asks.
 
-### 11. Using as MCP server
+### 11. Upgrading the CLI
+
+When the user wants to update `@ant-design/cli` to the latest version, or when an "Update available" notice appears:
+
+```bash
+# Upgrade to the latest version (auto-detects package manager)
+antd upgrade
+```
+
+The command detects which package manager installed the CLI (npm, yarn, pnpm, bun, cnpm, utoo) and runs the appropriate upgrade command. If detection fails, it suggests the manual command.
+
+### 12. Using as MCP server
 
 If working in an IDE that supports MCP (Claude Desktop, Cursor, etc.), the CLI can also run as an MCP server, exposing all knowledge-query tools directly:
 
@@ -233,21 +251,22 @@ If working in an IDE that supports MCP (Claude Desktop, Cursor, etc.), the CLI c
 }
 ```
 
-This provides 7 tools (`antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_token`, `antd_semantic`, `antd_changelog`) and 2 prompts (`antd-expert`, `antd-page-generator`) via MCP protocol.
+This provides 8 tools (`antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_token`, `antd_design_md`, `antd_semantic`, `antd_changelog`) and 2 prompts (`antd-expert`, `antd-page-generator`) via MCP protocol.
 
 ## Global Flags
 
 | Flag | Purpose |
 |---|---|
-| `--format json` | Structured output — always use this |
+| `--format <format>` | Output format: `json`, `text`, or `markdown` (agents should prefer `json`) |
 | `--version <v>` | Target a specific antd version (e.g. `5.20.0`) |
 | `--lang zh` | Chinese output (default: `en`) |
 | `--detail` | Include extra fields (description, since, deprecated, FAQ) |
+| `-V, --cli-version` | Print CLI version and exit |
 
 ## Key Rules
 
 1. **Always query before writing** — Don't guess antd APIs from memory. Run `antd info` first.
-2. **Match the user's version** — If the project uses antd 3.x or 4.x, pass `--version 3.26.0` or `--version 4.24.0`. The CLI auto-detects from `node_modules` if no flag is given.
+2. **Match the user's version** — Knowledge queries (`list/info/doc/demo/token/semantic/changelog`) support antd v4+. If the project uses antd 4.x/5.x/6.x, pass `--version 4.24.0` / `5.24.0` / `6.x`. For antd v3 projects, use `antd migrate 3 4` first.
 3. **Use `--format json`** — Every command supports it. Parse the JSON output rather than regex-matching text output.
 4. **Check before suggesting migration** — Run `antd changelog <v1> <v2>` and `antd migrate` before advising on version upgrades.
 5. **Lint after changes** — After writing or modifying antd code, run `antd lint` on the changed files to catch deprecated or problematic usage.