Skip to main content
skill CX Codex

wix-design-system — Claude Code skill: what it does, how to install

Inspects @wix/design-system components, props, code examples, and testkit drivers directly inside your project.

MIT 218 installs ★ 40 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add wix/skills --skill wix-design-system -a claude-code
Open on GitHub

What wix-design-system does

The skill bundles scripts/wds.cjs, a Node.js helper that locates @wix/design-system inside node_modules across standard setups and monorepos. Your agent runs this script to search components with keywords, fetch prop definitions, pull JSX usage samples, and look up icons from @wix/wix-ui-icons-common.

For end-to-end testing, the helper extracts driver methods and import snippets for Playwright, Puppeteer, Unidriver, or vanilla DOM. When the helper script cannot run, the skill falls back to reading documentation files stored in node_modules/@wix/design-system/dist/docs/.

Running queries fails if @wix/design-system is not installed in the target repository. If components appear completely unstyled, import @wix/design-system/styles.global.css once at your application root.

What it helps with

  • look up component prop types and JSX code snippets
  • search UI elements by keyword across @wix/design-system
  • retrieve testkit driver methods for Playwright or Puppeteer
  • convert pixel values to WDS SP spacing tokens
  • find icon names from @wix/wix-ui-icons-common

Example prompts for the agent

  • Show me props and a loading state example for the Button component
  • Find the right WDS component for a responsive dialog layout
  • Get testkit imports and the click driver method for Button in Playwright

How to install wix-design-system

1Skills CLI (Vercel)

npx skills add wix/skills --skill wix-design-system -a claude-code

2Manually: put the files in place

~/.claude/skills/wix-design-system/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wix-design-system/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wix-design-system

How to install wix-design-system in Claude Code?

Run npx skills add wix/skills --skill wix-design-system -a claude-code in your terminal. This creates the skill file at ~/.claude/skills/wix-design-system/SKILL.md.

What does wix-design-system do?

It gives your coding agent instant access to Wix Design System props, layout tokens, JSX examples, and testkit driver APIs.

What is required before using this skill?

The @wix/design-system package must be installed in your project via npm i @wix/design-system or yarn add @wix/design-system, as the helper script searches local node_modules.

Source text

SKILL.md · MIT
---
name: wix-design-system
description: Wix Design System component reference. Use when building UI with @wix/design-system, choosing components, checking props and examples, or writing tests with component testkits. Triggers on "what component", "how do I make", "WDS", "show me props", "testkit", "driver", or component names like Button, Card, Modal, Box, Text.
metadata:
  verified: true
---

# WDS Documentation Navigator

**Prerequisite:** `@wix/design-system` must be installed (`npm i @wix/design-system` or `yarn add @wix/design-system`).

## Helper Script

This skill bundles `scripts/wds.cjs` — a Node.js helper that auto-discovers `@wix/design-system` in node_modules (handles monorepos and workspaces) and provides focused lookups. Run it from the user's project directory using the absolute path to the bundled script:

```bash
# WDS is the absolute path to this skill's scripts/wds.cjs
WDS="<this-skill-dir>/scripts/wds.cjs"

node $WDS search <keyword>                 # Find components by keyword
node $WDS component <Name>                 # Get props + example list (one component)
node $WDS components <Name1> <Name2>...    # Same as `component`, but for several at once
node $WDS example <Name> "<ExampleName>"   # Get a specific example
node $WDS testkit <Name> [method]          # Get testkit imports + driver API
node $WDS icons <query>                    # Search for icons
```

## Workflow

### Step 1: Find the right component

```bash
node $WDS search table
node $WDS search form input validation
node $WDS search modal dialog popup
```

Multiple keywords are OR-matched. Returns component names, descriptions, and usage guidance.

### Step 2: Get props and available examples

```bash
node $WDS component Button
```

Returns the full props list (types and descriptions) plus a list of all available examples. For large prop files (>200 lines), returns a summary with prop names and types.

If you already know which several components you'll need (e.g. after Step 1 returned a shortlist), prefer the batch form to avoid one round-trip per component:

```bash
node $WDS components Button Card Table Input Text Thumbnail
```

Output is each component's props block separated by `---`. Missing components are logged to stderr and skipped; the command only fails if every requested component is missing.

### Step 3: Get a specific example

```bash
node $WDS example Button "Loading state"
```

Returns the example description and JSX code. Matching is case-insensitive and supports substrings (e.g., "loading" matches "Loading state").

### Step 4: Write tests with the component testkit

```bash
node $WDS testkit Button             # Imports + full driver API for Button
node $WDS testkit Button click       # Just the click() method details
```

Returns import snippets for unidriver, vanilla, puppeteer, and playwright flavors plus the driver method API (name, args, return type, description). Method name matching is case-insensitive substring.

### Step 5: Find icons

```bash
node $WDS icons Add Edit Delete
```

Icons are from `@wix/wix-ui-icons-common`. Each icon has a `Small` variant (e.g., `Add` + `AddSmall`).

## Fallback: Direct File Access

If the script is unavailable, docs are at `node_modules/@wix/design-system/dist/docs/`:

- `components.md` — component catalog (~978 lines, grep only)
- `components/{Name}Props.md` — props per component
- `components/{Name}Examples.md` — examples per component (grep `^### ` for section list)
- `components/{Name}Testkit.md` — testkit imports + driver API per component (grep `^### ` for method list)
- `testkits.md` — testkit catalog (list of components with generated testkit docs)
- `icons.md` — icon catalog (~818 lines, grep only)

Don't read these files fully. Grep for keywords, then read specific sections with offset/limit. See [references/file-structure.md](references/file-structure.md) for the exact docs file layout and section shapes.

---

## Quick Component Mapping (Design to WDS)

| Design Element      | WDS Component                     | Notes             |
| ------------------- | --------------------------------- | ----------------- |
| Rectangle/container | `<Box>`                           | Layout wrapper    |
| Text button         | `<TextButton>`                    | Secondary actions |
| Input with label    | `<FormField>` + `<Input>`         | Wrap inputs       |
| Toggle              | `<ToggleSwitch>`                  | On/off settings   |
| Modal               | `<Modal>` + `<CustomModalLayout>` | Use together      |
| Grid                | `<Layout>` + `<Cell>`             | Responsive        |

## Spacing (px to SP conversion)

When designer specifies pixels, convert to the nearest SP token:

| Token | Classic | Studio |
| ----- | ------- | ------ |
| `SP1` | 6px     | 4px    |
| `SP2` | 12px    | 8px    |
| `SP3` | 18px    | 12px   |
| `SP4` | 24px    | 16px   |
| `SP5` | 30px    | 20px   |
| `SP6` | 36px    | 24px   |

```tsx
<Box gap="SP2" padding="SP3">
```

Only use SP tokens for `gap`, `padding`, `margin` — not for width/height.

## Imports

```tsx
import { Button, Card, Image } from "@wix/design-system";
import { Add, Edit, Delete } from "@wix/wix-ui-icons-common";
```

## GUIDELINES

1. Don't ever override WDS CSS tokens. Only if it's not possible otherwise, mention that very clearly to the prompter, that this is an anti-pattern and should be avoided at all costs.

### Troubleshooting

- **Components render unstyled** (plain HTML look, missing WDS spacing/typography): add `import "@wix/design-system/styles.global.css";` once to the root/main component (e.g. `page.tsx`, modal entry) — not child/tab/helper files.

© wix · MIT · wix/skills

Similar skills

All skills for Frontend and UI →

From the same set9

wix-docs wix-docs verifies exact Wix API endpoints and schemas via curl or MCP tools. Keeps agents from inventing parameters from memory. CX Codex +1 841installs wix-manage wix-manage — a skill for Claude Code and five other platforms that handles Wix site configuration and business tools through REST API. Runs administration, SEO tasks, app setups, and analytics queries. CX Codex +1 803installs wix-headless-kit wix-headless-kit — a skill for Claude Code, Codex, and Cursor that builds Wix Headless sites and deploys web projects online. Connects pre-built store, booking, or blog backends to your frontend code. CX Codex +1 482installs wix-vibe-headless wix-vibe-headless connects an existing frontend to a live Wix site using client-side REST and a public client ID. Runs straight from the browser without an SDK or custom backend. CX Codex +1 422installs wix-headless wix-headless wires Wix services into a headless frontend: installs the apps, seeds backend content, and returns an SDK integration guide. Managed projects also get the frontend built and released. CX Codex +1 338installs wix-headless-templates wix-headless-templates is a Claude Code skill with ready Wix Headless code for business solutions: data layers, pages, and seeds. It supports agent-built sites based on templates. CX Codex +1 301installs wix-app Assists in building Wix CLI app extensions, dashboard pages, widgets, and backend APIs. Prepares applications for Wix App Market review. CX Codex +1 261installs wix Agent skills and an MCP server to build Wix app extensions, wire headless frontends, and manage Wix Studio 2 sites. ★ 40repo stars

Project sponsors

Companies that keep this analytics open