diff --git a/.agents/skills b/.agents/skills
new file mode 120000
index 00000000..454b8427
--- /dev/null
+++ b/.agents/skills
@@ -0,0 +1 @@
+../.claude/skills
\ No newline at end of file
diff --git a/.claude/skills/antd/SKILL.md b/.claude/skills/antd/SKILL.md
new file mode 100644
index 00000000..680bd1e9
--- /dev/null
+++ b/.claude/skills/antd/SKILL.md
@@ -0,0 +1,236 @@
+---
+name: antd
+description: >
+  Use when the user's task involves Ant Design (antd) — writing antd components,
+  debugging antd issues, querying antd APIs/props/tokens/demos, migrating between
+  antd versions, or analyzing antd usage in a project. Triggers on antd-related
+  code, imports from 'antd', or explicit antd questions.
+allowed-tools:
+  - Bash(antd *)
+  - Bash(antd bug*)
+  - Bash(antd bug-cli*)
+  - Bash(npx antd *)
+  - Bash(npx antd bug*)
+  - Bash(npx antd bug-cli*)
+---
+
+# 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.
+
+## Setup
+
+The CLI is installed as a dev dependency. Use `npx antd` to run it.
+
+**Always use `--format json` for structured output you can parse programmatically.**
+
+## Scenarios
+
+### 1. Writing antd component code
+
+Before writing any antd component code, look up its API first — don't rely on memory.
+
+```bash
+# Check what props are available
+npx antd info Button --format json
+
+# Get a working demo as starting point
+npx antd demo Button basic --format json
+
+# Check semantic classNames/styles for custom styling
+npx antd semantic Button --format json
+
+# Check component-level design tokens for theming
+npx antd token Button --format json
+```
+
+**Workflow:** `antd info` → understand props → `antd demo` → grab a working example → write code.
+
+### 2. Looking up full documentation
+
+When you need comprehensive component docs (not just props):
+
+```bash
+npx antd doc Table --format json        # full markdown docs for Table
+npx antd doc Table --lang zh            # Chinese docs
+```
+
+### 3. Debugging antd issues
+
+When code isn't working as expected or the user reports an antd bug:
+
+```bash
+# Collect full environment snapshot (system, deps, browsers, build tools)
+npx antd env --format json
+
+# Check if the prop exists for the user's antd version
+npx antd info Select --version 5.12.0 --format json
+
+# Check if the prop is deprecated
+npx antd lint ./src/components/MyForm.tsx --format json
+
+# Diagnose project-level configuration issues
+npx antd doctor --format json
+```
+
+**Workflow:** `antd env` → capture full environment → `antd doctor` → check configuration → `antd info --version X` → verify API against the user's exact version → `antd lint` → find deprecated or incorrect usage.
+
+### 4. Migrating between versions
+
+When the user wants to upgrade antd (e.g., v3 → v4 or v4 → v5):
+
+```bash
+# Get full migration checklist
+npx antd migrate 3 4 --format json    # v3 → v4
+npx antd migrate 4 5 --format json    # v4 → v5
+
+# Check migration for a specific component
+npx antd migrate 4 5 --component Select --format json
+
+# See what changed between two versions
+npx antd changelog 4.24.0 5.0.0 --format json
+
+# See changes for a specific component
+npx antd changelog 4.24.0 5.0.0 Select --format json
+```
+
+**Workflow:** `antd migrate` → get full checklist → `antd changelog <v1> <v2>` → understand breaking changes → apply fixes → `antd lint` → verify no deprecated usage remains.
+
+### 5. Analyzing project antd usage
+
+When the user wants to understand how antd is used in their project:
+
+```bash
+# Scan component usage statistics
+npx antd usage ./src --format json
+
+# Filter to a specific component
+npx antd usage ./src --filter Form --format json
+
+# Lint for best practice violations
+npx antd lint ./src --format json
+
+# Check only specific rule categories
+npx antd lint ./src --only deprecated --format json
+npx antd lint ./src --only a11y --format json
+npx antd lint ./src --only performance --format json
+```
+
+### 6. Checking changelogs and version history
+
+When the user asks about what changed in a version:
+
+```bash
+# Specific version changelog
+npx antd changelog 5.22.0 --format json
+
+# Version range (both ends inclusive)
+npx antd changelog 5.21.0..5.24.0 --format json
+```
+
+### 7. Exploring available components
+
+When the user is choosing which component to use:
+
+```bash
+# List all components with categories
+npx antd list --format json
+
+# List components for a specific antd version
+npx antd list --version 5.0.0 --format json
+```
+
+### 8. Collecting environment info
+
+When you need to understand the project's antd setup, or prepare info for a bug report:
+
+```bash
+# Full environment snapshot (text — paste into GitHub Issues)
+npx antd env
+
+# Structured JSON for programmatic use
+npx antd env --format json
+
+# Scan a specific project directory
+npx antd env ./my-project --format json
+```
+
+### 9. Reporting antd bugs
+
+When the user asks you to report an antd bug:
+
+```bash
+# Step 0: Collect environment info for reference (optional)
+npx antd env --format json
+
+# Step 1: Preview for user review
+npx antd bug --title "DatePicker crashes when selecting date" \
+  --reproduction "https://codesandbox.io/s/xxx" \
+  --steps "1. Open DatePicker 2. Click a date" \
+  --expected "Date is selected" \
+  --actual "Component crashes with error" \
+  --format json
+
+# Step 2: Show to user, ask for confirmation
+
+# Step 3: Submit after user confirms
+npx antd bug --title "DatePicker crashes when selecting date" \
+  --reproduction "https://codesandbox.io/s/xxx" \
+  --steps "1. Open DatePicker 2. Click a date" \
+  --expected "Date is selected" \
+  --actual "Component crashes with error" \
+  --submit
+```
+
+### 10. Reporting CLI issues
+
+When the user asks to report a CLI bug:
+
+```bash
+npx antd bug-cli --title "antd info Button returns wrong props" \
+  --description "When querying Button props for version 5.12.0, the output includes props that don't exist" \
+  --steps "1. Run: npx antd info Button --version 5.12.0 --format json" \
+  --expected "Props matching antd 5.12.0 Button API" \
+  --actual "Props include 'classNames' which was added in 5.16.0" \
+  --format json
+```
+
+Show the report to the user and confirm before submitting with `--submit`.
+
+**Opt-out:** If the environment variable `ANTD_NO_AUTO_REPORT=1` is set, skip all bug-reporting suggestions entirely.
+
+### 11. 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:
+
+```json
+{
+  "mcpServers": {
+    "antd": {
+      "command": "npx",
+      "args": ["antd", "mcp"]
+    }
+  }
+}
+```
+
+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.
+
+## Global Flags
+
+| Flag | Purpose |
+|---|---|
+| `--format json` | Structured output — always use this |
+| `--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) |
+
+## Key Rules
+
+1. **Always query before writing** — Don't guess antd APIs from memory. Run `antd info` first.
+2. **Match the user's version** — This project uses antd v6. The CLI auto-detects from `node_modules` if no flag is given.
+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.
+6. **Report antd bugs** — When the user asks to report an antd bug, use `antd bug`. Always preview first, get user confirmation, then submit.
+7. **Report CLI issues** — When the user asks about a CLI problem, use `antd bug-cli` to help them file a report. Always preview first, get user confirmation, then submit.
\ No newline at end of file
diff --git a/AGENTS.md b/AGENTS.md
new file mode 100644
index 00000000..d4d85f9e
--- /dev/null
+++ b/AGENTS.md
@@ -0,0 +1,5 @@
+# AGENTS.md
+
+This file provides guidance for AI coding agents when working with code in this repository.
+
+For full project guidance, see [CLAUDE.md](./CLAUDE.md).
\ No newline at end of file
diff --git a/CLAUDE.md b/CLAUDE.md
index 9e27038b..0472dd71 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -111,7 +111,7 @@ ProLayout is configured via the `layout` export in `src/app.tsx` (`RunTimeLayout
 
 ### Page Co-location Pattern
 
-Each page directory contains its own `index.tsx`, optional `service.ts`, `_mock.ts`, `data.d.ts` (types), and `style.style.ts` or CSS files. This is the primary organizational pattern — keep page-specific code with the page.
+Each page directory contains its own index.tsx, optional service.ts, _mock.ts, data.d.ts (types), and style.ts or CSS files. This is the primary organizational pattern — keep page-specific code with the page.
 
 ### Cloudflare Worker Backend
 
diff --git a/package.json b/package.json
index 17e3df95..ff4f5ade 100644
--- a/package.json
+++ b/package.json
@@ -52,12 +52,14 @@
     "topojson-client": "^3.1.0"
   },
   "devDependencies": {
+    "@ant-design/cli": "^6.3.7",
     "@biomejs/biome": "^2.4.13",
     "@commitlint/cli": "^20.5.2",
     "@commitlint/config-conventional": "^20.5.0",
     "@tailwindcss/postcss": "^4.2.4",
     "@testing-library/dom": "^10.4.1",
     "@testing-library/react": "^16.3.2",
+    "@types/d3": "^7.4.3",
     "@types/express": "^5.0.6",
     "@types/jest": "^30.0.0",
     "@types/node": "^25.6.0",
@@ -65,7 +67,6 @@
     "@types/react-dom": "^19.2.3",
     "@types/react-helmet": "^6.1.11",
     "@types/topojson-client": "^3.1.5",
-    "@types/d3": "^7.4.3",
     "@types/topojson-specification": "^1.0.5",
     "@umijs/lint": "^4.6.49",
     "@umijs/max": "^4.6.49",