Ant Design Skill

# Ant Design (React) — Practical Front-end Design Skill

Use this skill when you are building a React UI with **Ant Design (antd)** and want **consistent, non-ugly** screens fast.

## When to use
- The project uses **React** + **Ant Design**
- You need to design/implement pages with: **Layout**, **Menu**, **Form**, **Table**, **Modal**, **Drawer**, **Steps**, **Tabs**, **Pagination**
- You need to implement **theme tokens** (colors, radius, typography, spacing)
- You want predictable UI patterns (CRUD screens, dashboards, settings pages)

## Default workflow (do this order)
1) Confirm stack: React + antd version (v5+ assumed).
2) Choose page pattern:
   - CRUD list (Table) + filters (Form) + actions (Modal/Drawer)
   - Wizard (Steps)
   - Settings (Form + Cards)
   - Dashboard (Grid + Cards + Charts)
3) Build layout skeleton first:
   - `Layout` + `Sider` + `Header` + `Content`
   - Navigation with `Menu`
4) Build the main interaction component:
   - Forms: `Form`, `Form.Item`, `Input`, `Select`, `DatePicker`, `Switch`
   - Tables: `Table` + column definitions + row actions
5) Add feedback loop:
   - `message`, `notification`, `Modal.confirm`
6) Apply theming/tokens via `ConfigProvider` (global) and component-level overrides.
7) Verify:
   - Empty states
   - Loading states
   - Error states
   - Mobile responsiveness (at least: 360px layout sanity)

## Component patterns (copy/paste mental models)
### Layout
- Use `Layout` with `Sider` (collapsible), `Header` for top actions, `Content` scroll.
- Put page title + primary CTA in a `Flex` (or `Space`) row.

### Forms
- Keep forms vertical; align labels consistently.
- Use `Form` + `Form.Item` rules for validation; avoid custom validation unless necessary.
- Use `Form.useForm()` and `form.setFieldsValue()` for edit flows.

### Tables (CRUD)
- Columns:
  - left: identifier/name
  - middle: important attributes
  - right: actions (Edit/Delete)
- Use `rowKey` always.
- Use server-side pagination for real apps.

### Modals...

# ant_design_skill — Ant Design skill for OpenClaw

A practical skill to help an AI agent (OpenClaw/Codex-style) build **React UIs** using **Ant Design (antd)** with:
- reliable UI patterns (CRUD, Settings, Wizard)
- consistent layout/spacing
- Ant Design v5 **Design Tokens** (global + component overrides)

Repo purpose: when you ask “make a screen with Ant Design”, the agent follows the workflow/patterns here instead of generating random ugly UI.

## What is Ant Design?
Ant Design is a React UI library with a large set of enterprise-ready components.

- Official repo: https://github.com/ant-design/ant-design
- Docs: https://ant.design/

## Installation (React)

```bash
npm i antd
```

Add antd styles (depends on your setup):

### Vite / CRA / Next.js (typical)
```ts
import 'antd/dist/reset.css';
```

> Ant Design v5 recommends `reset.css`.

## Minimal App Example

```tsx
import 'antd/dist/reset.css';
import { Button, Space, Typography } from 'antd';

export default function App() {
  return (
    <div style={{ padding: 24 }}>
      <Typography.Title level={3}>Hello AntD</Typography.Title>
      <Space>
        <Button type="primary">Primary</Button>
        <Button>Default</Button>
      </Space>
    </div>
  );
}
```

## Theming / Tokens (Ant Design v5)
AntD v5 uses **design tokens** via `ConfigProvider`.

### Global theme tokens

```tsx
import { ConfigProvider, theme } from 'antd';

export function AppProviders({ children }: { children: React.ReactNode }) {
  return (
    <ConfigProvider
      theme={{
        algorithm: theme.defaultAlgorithm,
        token: {
          colorPrimary: '#1677ff',
          borderRadius: 10,
          fontSize: 14,
          // spacing tokens exist too (padding, margin patterns are often via layout)
        },
      }}
    >
      {children}
    </ConfigProvider>
  );
}
```

### Dark mode

```tsx
const isDark = true;

<ConfigProvider
  theme={{
    algorithm: isDark ? theme.darkAlgorithm : theme.defaultAlgorithm,
    token: { color...