Ant Design CLI
Offline Ant Design reference for agents: props, tokens, demos and changelogs for antd v3 to v6, queried by command.
- 261 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- `antd setup` writes MCP configuration and skill files into the project, and `antd upgrade` updates the CLI itself.
- `antd bug --submit` sends a report with environment data to GitHub.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ant-design-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- `antd setup` writes MCP configuration and skill files into the project, and `antd upgrade` updates the CLI itself.
- `antd bug --submit` sends a report with environment data to GitHub.
This is third-party code. Review the repository files before installing.
What it does
The `antd` command gives an agent exact Ant Design component data without touching the network. Props tables with types and defaults, documentation, demo sources, design tokens, the `classNames` and `styles` structure and changelog entries ship inside the package. There are per-minor snapshots for antd 3, 4, 5 and 6, so the agent queries the API of the version the project uses. Another group of commands analyses the project. `antd usage` counts imports, `antd lint` finds deprecated APIs and accessibility gaps, `antd doctor` runs ten diagnostic checks, and `antd migrate 4 5 --apply ./src` prepares a migration prompt for the agent. Every command accepts `--format json`. The `antd mcp` mode starts a stdio MCP server with eight tools.
Who it is for. React developers on Ant Design who ask an agent to build or migrate interfaces for a specific antd version.
Good fit when
- The agent mixes up Table or Form props between versions and needs the exact API of the project.
- The project moves from antd 4 to 5 and the list of deprecated calls should come from the code.
- Component tokens and semantic slots are needed for a custom theme without reading docs by hand.
- Before a release you want to run `antd lint` over `src` and see accessibility problems.
- The IDE supports MCP and an Ant Design reference should be at hand with no network.
Not a fit when
- The project uses another component library: the reference covers only Ant Design.
- You need docs for third-party antd extensions: the package holds the library's own data.
- The project is on a fresh minor antd release while the CLI has not been updated for a long time: the data ships with the package version.
Example request
Show the Select props for antd 5.20.0 and find deprecated calls in src before moving to version 6.Limitations
The data works offline, but fresh antd releases reach it only with a new CLI release, which `antd upgrade` installs. The `antd setup` command writes MCP configuration or skill files into the project, and `antd bug` with `--submit` sends a report through gh to the Ant Design repository together with collected environment data. The `skills/antd/SKILL.md` skill only tells the agent when to call the commands, so the `@ant-design/cli` package must be installed separately. Bilingual component descriptions print in English or Chinese, switched with `--lang zh`.
How to disable. Remove the package with `npm uninstall -g @ant-design/cli`, then delete the skill and the antd entry from `.mcp.json` or the client configuration.
FAQ
How do I install Ant Design CLI for Claude Code?
Run `npm install -g @ant-design/cli`, then `npx skills add ant-design/ant-design-cli`. The `antd setup --client claude` command additionally writes the MCP config to `.mcp.json`.
Does it need a network or an API key?
No, all data ships with the package and no keys are needed. The network is used only by `antd upgrade` and by `antd bug --submit` when sending a report.
How do I get component props for a specific version?
Add the `--version` flag, for example `antd info Button --version 4.24.0`. For differences between releases use `antd changelog 4.24.0 5.0.0 Select`.
Which tools does the MCP mode provide?
Eight: `antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_token`, `antd_design_md`, `antd_semantic` and `antd_changelog`. There are also two prompts, `antd-expert` and `antd-page-generator`.
How do I move a project from version 4 to 5?
`antd migrate 4 5` prints a checklist split into automatic and manual fixes. With `--apply ./src` the command prepares a prompt for an agent that carries out the migration.
Discussion
No questions or reviews yet.
Related
CLI toolsTwo official Ant Design skills: a guide to antd 6, Pro 5 and X 2 plus an offline antd reference workflow for code and migrations
Ant Design Components MCP
antd-components-mcp
An MCP server that hands an agent Ant Design component docs, API, code examples and changelogs so it stops inventing props
DESIGN.md by Google Labs
DESIGN.md
The DESIGN.md format for agents and a CLI: lint contrast and references, diff versions, export tokens to Tailwind and DTCG
An MCP server and skill for interfaces: 31 design systems for shadcn/ui, UI and UX principles and accessibility review for agent-written code
A CLI that lets an agent inspect a running React app: component tree, props, state, hooks and render profiling
designlang
designlang (design-extract)
A CLI and MCP server that reads a live website and pulls out its design system: DTCG tokens, a Tailwind config, Figma variables and a brand book
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Ant Design CLI (this card) | no | 261 | |
| Material UI agent skills | no | 99,298 | four Material UI skills with styling and theming practices; here a CLI with data for every Ant Design version and project analysis |
| shadcn/ui | no | 127,489 | a skill and MCP for shadcn component registries; here a reference and migrations for the ready-made Ant Design library |
README in short
The authors build the CLI on the idea that an agent writes better antd code when the reference is at hand. Every command returns structured errors with codes and suggestions, and a typo in a component name is corrected by Levenshtein distance.