Ant Design 6 native skills
Version baseline: Ant Design 6.x (6.4.3 current stable at this review) and the first-party antd skill published by ant-design/ant-design-cli. The upstream CLI contains metadata for v3 through v6, so select and validate v6 explicitly.
Inspect before installing
- Read the package manager files and determine the installed
antdversion. - Inspect project and user skill locations supported by the active agent; do not assume one global path.
- If the first-party skill is already installed, read its
SKILL.md, source metadata, and any recorded revision before recommending an update. - Read the current Ant Design For Agents page and the upstream
antdskill.
Do not treat llms.txt, design.md, an MCP server, or a community skill as the native agent skill. They are useful companion resources, but the first-party Agent Skills source is ant-design/ant-design-cli.
Enforce v6 compatibility
- Require the host project to use
antd6.x for this operator. If it uses another major, stop and report the mismatch. - Confirm the upstream skill still documents or queries Ant Design v6 before installing it.
- When using
@ant-design/cli, pass or infer the installed project version and reject v5 examples or migrations as a v6 implementation baseline. - Inspect v6 deprecations with
antd lint, component details withantd info, and exact documentation withantd docwhen the CLI is available. - Never upgrade
antd, React, or the native skill merely to make the versions agree unless the user requested that upgrade.
Install only on request
Use the documented interactive installer from the project root:
npx skills add ant-design/ant-design-cli
Let the user choose the agent and project/user scope. Do not add --all, overwrite an existing skill, or install the global @ant-design/cli package unless requested. Review the upstream SKILL.md and scripts before granting them shell access.
Verify
After installation:
- Locate the installed skill and confirm its name is
antd. - Confirm its recorded source is the first-party repository.
- Re-read its version guidance and prove it exposes v6 documentation.
- Confirm the active agent discovers the destination directory.
- Report the source, revision or release when available, destination, scope, Ant Design project version, and compatibility result.
If compatibility cannot be established, leave the existing installation unchanged and explain what evidence is missing.