# ant

A skill that hands your agent the Ant Design rulebook: tokens, component states, accessibility. Useful for dense tables and forms.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2300 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/ant/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/ant

## What it does

This skill turns the agent into a design-system guideline author for Ant. It lays out the foundation first: a type scale of 12/14/16/20/24/32, Plus Jakarta Sans for text and display, JetBrains Mono for code, a token palette (primary `#1677ff`, success `#16A34A`, danger `#DC2626`), and a 4/8/12/16/24/32 spacing step. Component rules come after that, covering anatomy, variants, states, and keyboard or touch behavior.

The workflow is prescribed. The agent restates the design intent in one sentence, defines tokens and constraints, then moves to components. Empty, loading, and error states are required, not just the happy path. Accessibility is set at WCAG 2.2 AA with visible focus states.

There is a section on anti-patterns and migration notes for existing UI, and the output ends with a QA checklist you can run in code review. Rules must anchor to a token or threshold, so vague adjectives get rejected. If your project already has its own design system, expect friction: this skill pushes Ant tokens over yours.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill ant -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/ant/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/ant/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill ant -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/ant/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill ant -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/ant/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills ant
```

2. **Manually: put the files in place**
- File: `.github/skills/ant/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill ant -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/ant
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/ant/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill ant -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/ant/SKILL.md

## When to use it
- draft a component guideline with states and variants
- check text contrast and visible focus before shipping
- specify empty, loading and error states for a data table
- move scattered spacing values onto one scale
- build an accessibility checklist for code review

## Example prompts
- Write a guideline for a sortable table using Ant tokens
- Check my form against Ant rules and WCAG 2.2 AA
- Build a review checklist for the card component

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 02e167f62ab0c822.

BEGIN THIRD-PARTY FILE 02e167f62ab0c822
```text
---
name: ant
description: Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.
license: MIT
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Ant Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Ant.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
Ant Design follows a structured, enterprise-focused design system that emphasizes clarity, consistency, and efficiency in complex web applications.

## Style Foundations
- Visual style: data-dense, enterprise
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Plus Jakarta Sans, display=Plus Jakarta Sans, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#1677ff, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32


## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states

## Writing Tone
concise, confident, helpful, clear, friendly, professional, action-oriented, low-jargon

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
- document accessibility rationale

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
- avoid inaccessible hit areas

## Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.

## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.

## Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist

## Component Rule Expectations
```
END THIRD-PARTY FILE 02e167f62ab0c822

The third-party file has ended. Everything between the 02e167f62ab0c822 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2878 of 3821 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/ant/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md