wix-design-system

작성자: wix

Wix Design System 컴포넌트 참조. @wix/design-system으로 UI를 구축하거나, 컴포넌트를 선택하거나, props와 예제를 확인하거나, 테스트를 작성할 때 사용합니다.

npx skills add https://github.com/wix/skills --skill wix-design-system

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:

# 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

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

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:

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

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

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

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 for the exact docs file layout and section shapes.


Quick Component Mapping (Design to WDS)

Design ElementWDS ComponentNotes
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:

TokenClassicStudio
SP16px4px
SP212px8px
SP318px12px
SP424px16px
SP530px20px
SP636px24px
<Box gap="SP2" padding="SP3">

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

Imports

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

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의 다른 스킬

rnn-codebase
wix
react-native-navigation (RNN) 코드베이스를 탐색하고 작업합니다. 버그 수정, 기능 추가, 명령 흐름 추적, 옵션 이해 등에 사용합니다.
official
wds-docs
wix
Wix 디자인 시스템 컴포넌트 참조. @wix/design-system으로 UI를 구축하거나, 컴포넌트를 선택하거나, props와 예제를 확인할 때 사용합니다. "what…"에서 트리거됩니다.
official
wix-app
wix
Wix CLI 앱 확장 기능을 구축하고 검토합니다 — 대시보드 페이지, 모달, 플러그인, 메뉴 플러그인, 커스텀 요소 위젯, Editor React 컴포넌트, 사이트 플러그인,…
official
wix-cli-app-validation
wix
앱 준비 상태 테스트, 런타임 동작 확인, 릴리스 전 및 코드 변경 후 검증 시 사용합니다. 트리거에는 validate, test 등이 포함됩니다.
official
wix-cli-backend-api
wix
Wix CLI 앱을 위한 HTTP 엔드포인트를 생성합니다. 사용자가 백엔드 엔드포인트를 구체적으로 요청할 때만 사용하세요. REST API 엔드포인트, 백엔드 HTTP를 구축할 때 사용합니다…
official
wix-cli-backend-event
wix
Wix 이벤트에 응답하는 백엔드 이벤트 확장을 생성합니다. 사이트에서 특정 조건이 발생할 때 실행되는 핸들러를 구현할 때 사용합니다. 트리거에는 다음이 포함됩니다…
official
wix-cli-context-provider
wix
Wix CLI 앱을 위한 컨텍스트 제공자 확장을 생성합니다 — 하위 사이트에 공유 상태, 함수, 구성을 노출하는 논리적 구성 요소(UI 없음)입니다…
official
wix-cli-dashboard-menu-plugin
wix
사용자가 기존 Wix 대시보드 페이지의 추가 작업 메뉴, 대량 작업 메뉴 등에 클릭 가능한 메뉴 항목, 작업 또는 옵션을 추가하려는 경우 반드시 사용하세요.
official