ant-design

- Target: antd@^6 + React 18-19, with ant-design-pro@^5 / @ant-design/pro-components and @ant-design/x@^2 when needed.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ant-design" with this command: npx skills add rolling-scopes/rsschool-app/rolling-scopes-rsschool-app-ant-design

Ant Design

S - Scope

  • Target: antd@^6
  • React 18-19, with ant-design-pro@^5 / @ant-design/pro-components and @ant-design/x@^2 when needed.
  • Focus: decision guidance only; no end-user tutorials.

  • Source policy: official docs only; no undocumented APIs or internal .ant-* coupling.

Default assumptions

  • Language: TypeScript.

  • Styling: tokens first, then classNames /styles ; avoid global overrides.

  • Provider: one root ConfigProvider unless strict isolation is required.

Mandatory rules

  • For component questions, first map the component name to the official route slug {components} (lowercase kebab-case, e.g. TreeSelect -> tree-select , Button -> button ), then request docs in this order (CN first, EN fallback):

  • https://ant.design/components/{components}-cn

  • https://ant.design/components/{components}

  • Examples: tree-select-cn -> tree-select , button-cn -> button .

  • Use only documented antd/Pro/X APIs.

  • Do not invent props/events/component names.

  • Do not rely on internal DOM or .ant-* selectors.

  • Theme priority: global tokens -> component tokens -> alias tokens.

P - Process

  1. Classify
  • Identify layer: core antd, Pro, or X.

  • Confirm version, rendering mode (CSR/SSR/streaming), and data scale.

  1. Request docs
  • For each component, request -cn.md first, then .md fallback.

  • If multiple components are involved, request each component page before deciding.

  1. Decide
  • Provider baseline: CSR -> ConfigProvider ; SSR -> ConfigProvider
  • StyleProvider .
  • Theming baseline: global tokens -> component tokens -> classNames /styles .

  • Output recommendation + risk + verification points (SSR/a11y/perf).

O - Output

  • Provide short decision rationale (1-3 sentences).

  • Include minimal provider/theming strategy.

  • Include concrete SSR/a11y/perf checks.

  • For Pro: include route/menu/access and CRUD schema direction.

  • For X: include message/tool schema and streaming state direction.

Regression checklist

  • One root ConfigProvider ; SSR style order/hydration verified.

  • Tokens first; no broad global .ant-* overrides.

  • Table has stable rowKey ; sort/filter/pagination entry is unified.

  • Select remote mode disables local filter when using remote search.

  • Upload controlled/uncontrolled mode is explicit with failure/retry path.

  • Pro route/menu/access remain consistent with backend enforcement.

  • X streaming supports stop/retry and deterministic tool rendering.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

nestjs-best-practices

No summary provided by upstream source.

Repository SourceNeeds Review
General

typeorm

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

typescript-advanced-types

No summary provided by upstream source.

Repository SourceNeeds Review