wds-docs

Navigate Wix Design System docs to locate components, props, and usage examples.

25|31|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/wix/skills --skill wds-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wds-docs
Source: https://github.com/wix/skills/tree/main/wix-cli/skills/wds-docs
Command: npx skills add https://github.com/wix/skills --skill wds-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Wix Design System Documentation Navigator accelerates UI development by turning vast WDS docs into focused, actionable references for components, props, and examples.

Core Features & Use Cases

  • Component discovery: locate components by keyword across the WDS docs path.
  • Props & usage: extract prop definitions and example usage without loading entire docs.
  • Guided workflow: move from Stage 1 discovery to Stage 2 props and examples, then Stage 3 fetch of a specific example.

Quick Start

Find a Wix Design System component by keyword and retrieve its props and usage examples.

Frequently Asked Questions about wds-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find Wix Design System component props and usage examples?

To find Wix Design System component props and examples, use a guided component discovery workflow that searches by keyword, extracts prop definitions, and retrieves specific usage examples selectively to keep performance high.

What is the best way to navigate Wix Design System documentation for UI development?

The best way to navigate Wix Design System docs is through a staged workflow: discover components by keyword, list their props and examples, then fetch specific examples to turn vast documentation into focused, actionable references.

Can I search WDS docs for specific components without loading the entire documentation?

Yes, you can search WDS docs for specific components without loading entire files by using selective file reads and grep-based extraction to locate component definitions, props, and examples efficiently.

How does the staged discovery workflow work for Wix Design System components?

The staged discovery workflow moves from Stage 1 component discovery by keyword, to Stage 2 prop and example listing, and finally Stage 3 retrieval of a specific example, ensuring efficient reference workflows.

Are there limitations to using grep-based extraction for Wix Design System documentation?

A limitation of using grep-based extraction for WDS documentation is that it enforces staged discovery through selective file reads, requiring multiple sequential queries to gather all desired props and examples across the documentation path.