antdv

name	antdv
description	Use when the user's task involves antdv-next — writing antdv-next components, debugging antdv-next issues, querying antdv-next props/events/slot/tokens/demos, migrating between antdv-next versions, or analyzing antdv-next usage in a project. Triggers on antdv-next-related code, imports from 'antdv-next', or explicit antdv-next questions.
allowed-tools	["Bash(antdv *)","Bash(antdv bug*)","Bash(antdv bug-cli*)","Bash(npm install -g @antdv-next/cli*)","Bash(which antdv)"]

Ant Design CLI

You can visit @antdv-next/cli - a local cli tool that contains metadata about the current, latest version of antdv-next. Use it to query component knowledge, analyze projects, and guide migrations. All data is offline and does not require a network.

Setup

Before first use, check if the CLI is installed. If not, install it automatically:

which antdv || npm install -g @antdv-next/cli

After running any command, if the output contains an "Update available" notice, run antdv upgrade to update before continuing.

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.

# Check what props are available
antdv info Button --format json

# Get a working demo as starting point
antdv demo Button basic --format json

# Check semantic classNames/styles for custom styling
antdv semantic Button --format json


antdv token Button --format json


antdv design.md --format json