Build, manage, and deploy Wix sites and apps. Includes CLI development skills and Wix MCP server for site management, eCommerce, CMS, dashboard extensions, and more.
Wix Design System component reference. Use when building UI with @wix/design-system, choosing components, or checking props and examples. Triggers on "what component", "how do I make", "WDS", "show me props", component names like Button, Card, Modal, Box, Text, or when importing from @wix/design-system or @wix/wix-ui-icons-common. Also use when looking up spacing tokens (SP1-SP6) or icon names.
Use when testing app readiness, verifying runtime behavior, or validating before releases and after changes in the code. Triggers include validate, test, verify, check readiness, preview validation, build verification, TypeScript compilation.
Creates HTTP endpoints for Wix CLI apps. Use only when the user specifically asks for a backend endpoint. Use when building REST API endpoints, backend HTTP handlers, or server-side logic. Triggers include backend API, HTTP endpoint, HTTP methods, form handling, file uploads.
Create backend event extensions that respond to Wix events. Use when implementing handlers that run when specific conditions occur on a site. Triggers include event extension, backend event, webhook handler.
Creates context provider extensions for Wix CLI apps — logical components (no UI) that expose shared state, functions, and configuration to child site components via React hooks and Editor Binding. Use when building a context provider, sharing state between components, creating a context hook (useContext), building a provider/consumer pattern, wiring contextDependencies, or using Editor Binding for context. Only site components can consume context providers — do NOT use for site widgets or site plugins.
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A single repo containing multiple Wix AI skill plugins, using the marketplace pattern to support Claude Code, Cursor, and npx skills add.
.claude-plugin/marketplace.json # Plugin registry (Claude Code)
.cursor-plugin/marketplace.json # Plugin registry (Cursor)
plugins/
wix-cli/ # Plugin: Wix CLI app development
.claude-plugin/plugin.json
.cursor-plugin/plugin.json
.mcp.json
assets/logo.svg
skills/
wix-cli-orchestrator/ # 18 skills total
wix-cli-dashboard-page/
wix-cli-site-widget/
...
wix-headless/ # Plugin: Wix Managed Headless
.claude-plugin/plugin.json
.cursor-plugin/plugin.json
.mcp.json
hooks/hooks.json
skills/
shared/ # Headless-specific shared references
wix-headless-designer/ # 8 skills total
wix-headless-stores/
...
How it works: The root marketplace.json acts as a registry that points to self-contained plugins under plugins/. Each plugin has its own manifests, MCP config, and skills. Users install whichever plugins they need.
| Plugin | Skills | Description |
|---|---|---|
| wix-cli | 18 | Dashboard extensions, backend APIs, site widgets, service plugins, embedded scripts |
| wix-headless | 8 | Astro + React + Wix SDK — from business discovery to live deployment |
Register the marketplace, then install plugins individually:
/plugin marketplace add https://github.com/wix-playground/skills-architecture-test
Select which plugin to install:
/plugin install wix-cli
/plugin install wix-headless

In the Cursor Agent chat, type:
/add-plugin
Search for the plugin by name or provide the GitHub URL. Then connect the MCP server in Cursor Settings > Tools & MCP Servers.

Install all skills from both plugins:
npx skills add wix-playground/skills-architecture-test
Skills appear grouped by plugin — select the ones you need:
Wix Cli
[x] wix-cli-orchestrator
[x] wix-cli-dashboard-page
[ ] wix-cli-site-widget
...
Wix Headless
[x] wix-headless-designer
[x] wix-headless-stores
...
Install only a specific plugin's skills:
npx skills add wix-playground/skills-architecture-test/plugins/wix-cli
npx skills add wix-playground/skills-architecture-test/plugins/wix-headless
Install a single skill by name:
npx skills add wix-playground/skills-architecture-test --skill wix-cli-orchestrator

Some skills may be useful across multiple plugins (e.g., wds-docs for the Wix Design System). There are three approaches:
Each plugin is fully independent. If a skill is needed by both plugins, it's duplicated.
| Pros | Cons |
|---|---|
| Zero complexity — no build step, no config | Duplication if skills overlap |
| Each plugin works standalone | Changes to shared content must be updated in multiple places |
| Simple git history — each plugin is a plain directory |
Shared skills live in a shared/ directory and stay there. A build.sh script reads a config and updates each plugin's marketplace.json skills arrays to reference the shared location — no copying.
shared/ # Shared skills live here permanently
wds-docs/SKILL.md
plugins/
wix-cli/
plugin.yaml # Declares which shared skills this plugin uses
skills/ # Plugin-owned skills (unchanged)
wix-headless/
plugin.yaml
skills/
plugin.yaml example:
name: wix-cli
shared_skills:
- wds-docs
build.sh updates marketplace.json to include shared paths:
{
"name": "wix-cli",
"source": "./plugins/wix-cli",
"skills": [
"./skills/wix-cli-orchestrator/",
"../../shared/wds-docs/"
]
}
| Pros | Cons |
|---|---|
| Single source of truth — edit once | Requires build.sh to update manifests |
| No file duplication or copying | Shared skills live outside the plugin directory (unusual) |
No dist/ directory to keep in sync | Platform loaders must support paths outside plugin root |
| Lightweight — only JSON gets updated |
npx claudepluginhub wix-playground/skills-architecture-test --plugin wix-cliBuild and deploy Wix Managed Headless projects with CLI management, SDK integration, and Astro framework development skills
Build, manage, and deploy Wix sites and apps. Includes CLI development skills and Wix MCP server for site management, eCommerce, CMS, dashboard extensions, and more.
Claude Code skill pack for Webflow (24 skills)
Production-ready skills for managing Webflow CMS content, auditing site health, optimizing assets, and safely publishing changes
Manage WordPress sites: content creation, blog posts, media, Elementor page editing, and WP-CLI workflows.
Full RampStack catalog of website-lifecycle skills across research, brand, build, and audit.
Create skills from documentation folders and project codebases. Review, test, and package Anthropic Agent Skills for Claude.ai and Claude Code. 13 commands including from-docs, from-project, beginner tutorial, interactive wizard, templates, quality auditing, and distribution packaging.