Frontend
streamband/hydra-srt
A skill your agent uses for frontend work in webapp (React/TypeScript, UI implementation, tests, and refactors).
Looks up antd component props, docs, demos and changelogs with the offline @ant-design/cli, and helps debug, migrate between versions and audit usage in a project.
$ npx skills add ant-design/antd-skill --skill antd -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ant-design/antd-skill antd --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ant-design/antd-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/antd .claude/skills/antd && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "antd" agent skill from https://github.com/ant-design/antd-skill/tree/main/skills/antd into .claude/skills/antd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antd", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ant-design/antd-skill/tree/main/skills/antdType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ant-design/antd-skill --skill antd -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ant-design/antd-skill antd --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ant-design/antd-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/antd .agents/skills/antd && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "antd" agent skill from https://github.com/ant-design/antd-skill/tree/main/skills/antd into .agents/skills/antd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antd", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ant-design/antd-skill --skill antd -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ant-design/antd-skill antd --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ant-design/antd-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/antd .cursor/skills/antd && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "antd" agent skill from https://github.com/ant-design/antd-skill/tree/main/skills/antd into .cursor/skills/antd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antd", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ant-design/antd-skill.git --path skills/antd--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ant-design/antd-skill --skill antd -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ant-design/antd-skill antd --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ant-design/antd-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/antd .gemini/skills/antd && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "antd" agent skill from https://github.com/ant-design/antd-skill/tree/main/skills/antd into .gemini/skills/antd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antd", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ant-design/antd-skill antdInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ant-design/antd-skill --skill antd -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ant-design/antd-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/antd .github/skills/antd && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "antd" agent skill from https://github.com/ant-design/antd-skill/tree/main/skills/antd into .github/skills/antd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antd", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ant-design/antd-skill --skill antd -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ant-design/antd-skill antd --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ant-design/antd-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/antd .opencode/skills/antd && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "antd" agent skill from https://github.com/ant-design/antd-skill/tree/main/skills/antd into .opencode/skills/antd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "antd", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
antdLooks up antd component props, docs, demos and changelogs with the offline @ant-design/cli, and helps debug, migrate between versions and audit usage in a project.
The skill relies on @ant-design/cli, a local command-line tool with bundled antd metadata for v4, v5 and v6, so lookups work offline. The agent installs it globally if the antd command is missing and asks for JSON output so results can be parsed. Before writing any component code it checks the real API with antd info, then pulls a working example with antd demo instead of relying on memory.
Other scenarios follow the same pattern: antd doc for full documentation, with a Chinese option; antd doctor and antd lint to find environment problems and deprecated or incorrect usage against the exact version in the project; antd migrate and antd changelog for moving between versions such as v4 to v5; antd usage to scan which components a source folder uses; and commands for browsing the available components.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e65d2d3. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
Bash(antd *)Bash(antd bug*)Bash(antd bug-cli*)Bash(npm install -g @ant-design/cli*)Bash(which antd)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
codesandbox.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ant Design CLI loads about 2.2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 733 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ant-design/antd-skill at commit e65d2d3, republished under its MIT licence (© ant-design). 733 words, ~2,161 tokens.
.claude/skills/antd/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You have access to @ant-design/cli — a local CLI tool with bundled antd metadata for v4/v5/v6. Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
Before first use, check if the CLI is installed. If not, install it automatically:
which antd || npm install -g @ant-design/cliAfter running any command, if the output contains an "Update available" notice, run npm install -g @ant-design/cli to update before continuing.
Always use --format json for structured output you can parse programmatically.
Before writing any antd component code, look up its API first — don't rely on memory.
# Check what props are available
antd info Button --format json
# Get a working demo as starting point
antd demo Button basic --format json
# Check semantic classNames/styles for custom styling
antd semantic Button --format json
# Check component-level design tokens for theming
antd token Button --format jsonWorkflow: antd info → understand props → antd demo → grab a working example → write code.
When you need comprehensive component docs (not just props):
antd doc Table --format json # full markdown docs for Table
antd doc Table --lang zh # Chinese docsWhen code isn't working as expected or the user reports an antd bug:
# Check if the prop exists for the user's antd version
antd info Select --version 5.12.0 --format json
# Check if the prop is deprecated
antd lint ./src/components/MyForm.tsx --format json
# Diagnose project-level configuration issues
antd doctor --format jsonWorkflow: antd doctor → check environment → antd info --version X → verify API against the user's exact version → antd lint → find deprecated or incorrect usage.
When the user wants to upgrade antd (e.g., v4 → v5):
# Get full migration checklist
antd migrate 4 5 --format json
# Check migration for a specific component
antd migrate 4 5 --component Select --format json
# See what changed between two versions
antd changelog 4.24.0 5.0.0 --format json
# See changes for a specific component
antd changelog 4.24.0 5.0.0 Select --format jsonWorkflow: antd migrate → get full checklist → antd changelog <v1> <v2> → understand breaking changes → apply fixes → antd lint → verify no deprecated usage remains.
When the user wants to understand how antd is used in their project:
# Scan component usage statistics
antd usage ./src --format json
# Filter to a specific component
antd usage ./src --filter Form --format json
# Lint for best practice violations
antd lint ./src --format json
# Check only specific rule categories
antd lint ./src --only deprecated --format json
antd lint ./src --only a11y --format json
antd lint ./src --only performance --format jsonWhen the user asks about what changed in a version:
# Specific version changelog
antd changelog 5.22.0 --format json
# Version range (both ends inclusive)
antd changelog 5.21.0..5.24.0 --format jsonWhen the user is choosing which component to use:
# List all components with categories
antd list --format json
# List components for a specific antd version
antd list --version 5.0.0 --format jsonWhen you encounter a confirmed antd component bug that can't be resolved locally:
# Step 1: Preview for user review
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
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" \
--submitIMPORTANT: Whenever you use any antd CLI command and notice something wrong, you should proactively initiate a bug report using antd bug-cli.
Trigger conditions — report a CLI bug when you observe any of these:
antd info Button shows wrong props, missing props, or props from the wrong version)--format json returns non-JSON, --version X is ignored)antd demo Button returns no demos, antd token Button returns no tokens for v5+)antd list shows a component but antd info says it doesn't exist)Workflow:
antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
--description "When querying Button props for version 5.12.0, the output includes props that don't exist in that version" \
--steps "1. Run: 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 jsonantd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
--description "..." \
--steps "..." \
--expected "..." \
--actual "..." \
--submitKey principle: You are a quality feedback loop for the CLI. Don't silently work around CLI issues — report them so they get fixed. Always confirm with the user before submitting.
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:
{
"mcpServers": {
"antd": {
"command": "antd",
"args": ["mcp", "--version", "5.20.0"]
}
}
}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.
| 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) |
antd info first.--version 4.24.0. The CLI auto-detects from node_modules if no flag is given.--format json — Every command supports it. Parse the JSON output rather than regex-matching text output.antd changelog <v1> <v2> and antd migrate before advising on version upgrades.antd lint on the changed files to catch deprecated or problematic usage.antd bug to report it. Always preview first, get user confirmation, then submit.antd command crashes, returns wrong data, or behaves inconsistently, proactively use antd bug-cli to report it. You are the quality feedback loop for the CLI — don't silently work around issues.© ant-design, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/antd of ant-design/antd-skill.
Open the folder on GitHubat commit e65d2d3
Ant Design CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ant Design CLI this skillant-design/antd-skill | 136 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Frontendstreamband/hydra-srt | 146 | — | ~582 | Automated safety check: Pass | Apache-2.0 | |
| Renovate Reviewcommercetools/ui-kit | 154 | — | ~907 | Automated safety check: Notes | MIT | |
| LobeHub Interactive Prototypelobehub/lobehub | 83k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Integrating shadcn/ui Componentsgoogle-labs-code/stitch-skills | 8.4k | 4 repos | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| GSAP for Reactgreensock/gsap-skills | 16k | 4 repos | ~1.6k | Automated safety check: Pass | MIT |
streamband/hydra-srt
A skill your agent uses for frontend work in webapp (React/TypeScript, UI implementation, tests, and refactors).
commercetools/ui-kit
Review Renovate dependency upgrade PRs to assess safety and effort.
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
google-labs-code/stitch-skills
Guides finding, installing, customizing and wiring up shadcn/ui components in a project, with MCP tools for the component catalog and registries.
greensock/gsap-skills
Shows how to run GSAP animations in React and Next.js with the useGSAP hook, refs, scoped selectors and automatic cleanup on unmount.
chakra-ui/chakra-ui
Guides an upgrade from Chakra UI v2 to v3: inspect the project, swap packages, run the official codemod, then fix provider, color mode, props, theming and Next.js code.
Works with
Categories
Looks up antd component props, docs, demos and changelogs with the offline @ant-design/cli, and helps debug, migrate between versions and audit usage in a project. The skill relies on @ant-design/cli, a local command-line tool with bundled antd metadata for v4, v5 and v6, so lookups work offline. The agent installs it globally if the antd command is missing and asks for JSON output so results can be parsed.
Ant Design CLI fits situations like: writing antd components and checking the real prop list first; debugging an antd prop that behaves differently on one version; planning an upgrade from antd v4 to v5; scanning a project to see which antd components it uses.
Run `npx skills add ant-design/antd-skill --skill antd -a claude-code`. Or copy the skill folder (skills/antd in ant-design/antd-skill) into .claude/skills/antd in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ant-design/antd-skill --skill antd -a codex`. Or copy the skill folder (skills/antd in ant-design/antd-skill) into .agents/skills/antd in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ant-design/antd-skill --skill antd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/antd, .gemini/skills/antd, .github/skills/antd and .opencode/skills/antd in your project.
Going by SKILL.md and its folder, Ant Design CLI needs the command-line tools its instructions call (npm). Our summary lists: Node.js and npm, to install @ant-design/cli globally. Its frontmatter pre-approves these tools: Bash(antd *), Bash(antd bug*), Bash(antd bug-cli*), Bash(npm install -g @ant-design/cli*), Bash(which antd).
SKILL.md names 1 domain. In commands or code: codesandbox.io; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Ant Design CLI is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ant Design CLI: Frontend (streamband/hydra-srt, 146 stars), Renovate Review (commercetools/ui-kit, 154 stars), LobeHub Interactive Prototype (lobehub/lobehub, 83k stars) and Integrating shadcn/ui Components (google-labs-code/stitch-skills, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ant-design (a GitHub organization) maintains it in ant-design/antd-skill, which has 136 GitHub stars. The repository was last updated on March 27, 2026.
Source: ant-design/antd-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.