Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Skill for efficiently building React UIs using Ant Design v5+ with layouts, forms, tables, modals, theming via ConfigProvider, and consistent component patte...
Skill for efficiently building React UIs using Ant Design v5+ with layouts, forms, tables, modals, theming via ConfigProvider, and consistent component patte...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill when you are building a React UI with Ant Design (antd) and want consistent, non-ugly screens fast.
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)
Confirm stack: React + antd version (v5+ assumed). Choose page pattern: CRUD list (Table) + filters (Form) + actions (Modal/Drawer) Wizard (Steps) Settings (Form + Cards) Dashboard (Grid + Cards + Charts) Build layout skeleton first: Layout + Sider + Header + Content Navigation with Menu Build the main interaction component: Forms: Form, Form.Item, Input, Select, DatePicker, Switch Tables: Table + column definitions + row actions Add feedback loop: message, notification, Modal.confirm Apply theming/tokens via ConfigProvider (global) and component-level overrides. Verify: Empty states Loading states Error states Mobile responsiveness (at least: 360px layout sanity)
Use Layout with Sider (collapsible), Header for top actions, Content scroll. Put page title + primary CTA in a Flex (or Space) row.
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.
Columns: left: identifier/name middle: important attributes right: actions (Edit/Delete) Use rowKey always. Use server-side pagination for real apps.
Modal for short forms. Drawer for longer forms or when you want context kept.
Ant Design v5 uses Design Tokens and CSS-in-JS.
Wrap your app in ConfigProvider: 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, }, components: { Button: { controlHeight: 40 }, Layout: { headerBg: '#ffffff' }, }, }} > {children} </ConfigProvider> ); }
Use theme.darkAlgorithm and keep tokens consistent: const isDark = true; <ConfigProvider theme={{ algorithm: isDark ? theme.darkAlgorithm : theme.defaultAlgorithm, token: { colorPrimary: '#7c3aed' }, }} />
Use components.<ComponentName> for specific tweaks (Button, Input, Table, etc.).
Read README.md for the full βhow-toβ (setup + patterns + examples). Use protocols/ when you want LLM-first contracts (describe UIs as data, then generate code deterministically). Read references/tokens.md for a tokens cookbook. Read references/components.md for practical page recipes (CRUD, Settings, Wizard). Use examples/ when you want ready-to-copy AntD screens. Use starter/ when you need a runnable Vite + React + AntD skeleton.
Assume Ant Design v5+ (tokens). If project is v4 (Less variables), stop and ask. Prefer built-in components and patterns over custom CSS. Avoid over-theming: set a small set of tokens and only override components when needed.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.