ant-design

Identify optimal Ant Design 6.x component usage and configuration choices.

152|32|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/lintendo/Axhub-Make --skill ant-design-lintendo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ant-design
Source: https://github.com/lintendo/Axhub-Make/tree/main/skills/third-party/ant-design
Command: npx skills add https://github.com/lintendo/Axhub-Make --skill ant-design-lintendo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces decision fatigue when integrating Ant Design by providing a concise, policy-driven guide that aligns component usage, theming, SSR/CSR decisions, and accessibility considerations with official docs.

Core Features & Use Cases

  • Policy-driven component selection: map component names to official routes and retrieve CN first, then EN documentation.
  • Theming and rendering guidance: establish token-first theming, SSR/CSR rendering choices, and accessibility checks.
  • Scope and validation: ensures usage stays within official APIs, with clear router/access/CRUD guidance for Pro/X variants.

Quick Start

Provide the recommended component, route, and theming approach for a given UI scenario.

Frequently Asked Questions about ant-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Ant Design 6.x components for SSR versus CSR scenarios?

Yes, Ant Design 6.x establishes a token-first theming approach to configure UI components, ensuring styling decisions align with official documentation and policy-driven constraints for consistent visual output.

How do I implement routing and accessibility checks for Ant Design Pro components?

Implementing routing and accessibility for Ant Design Pro components involves following clear router and access guidance to ensure UI interactions stay within official APIs and meet accessibility validation requirements.

What is the best way to configure CRUD operations using Ant Design 6.x?

Configuring CRUD operations with Ant Design 6.x involves applying policy-driven component selection to map scenarios to official APIs, ensuring data interactions align with Pro/X variant constraints and official documentation.

Does Ant Design 6.x enforce any limitations on custom component usage outside official APIs?

Yes, Ant Design 6.x enforces scope and validation limitations by ensuring component usage stays strictly within official APIs, preventing deviations and guaranteeing alignment with official documentation and policy-driven constraints.