Wix Skills

A single repo containing multiple Wix AI skill plugins, using the marketplace pattern to support Claude Code, Cursor, and npx skills add.

Architecture

.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.

Plugins

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

---

Installation

Claude Code

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

---

Cursor

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.

---

npx skills add

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

---

Shared Skills

Some skills may be useful across multiple plugins (e.g., wds-docs for the Wix Design System). There are three approaches:

Option A: Self-Contained Plugins (Current)

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

Option B: Shared Skills with References

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

Option C: Shared Skills with Copy to Dist

Same shared/ directory, but build.sh copies shared skills into each plugin's dist/ output, producing fully self-contained plugins.

shared/                              # Source of truth for shared skills
  wds-docs/SKILL.md

plugins/
  wix-cli/
    plugin.yaml                      # Declares which shared skills to copy
    skills/

build.sh                            # Reads plugin.yaml, assembles dist/

dist/                                # Generated — fully self-contained
  wix-cli/
    .claude-plugin/plugin.json
    skills/
      wds-docs/SKILL.md             # <-- copied from shared/
      wix-cli-orchestrator/SKILL.md
      ...
  wix-headless/
    .claude-plugin/plugin.json
    skills/
      wds-docs/SKILL.md             # <-- copied from shared/
      wix-headless-designer/SKILL.md
      ...

Pros	Cons
Single source of truth for shared skills	Requires running build.sh after changes
Each dist plugin is fully self-contained	dist/ can get stale if build is forgotten
Works with all platforms — no unusual paths	More disk usage (copies)
Clean separation of source vs distribution	CI/CD should run build to keep dist in sync

Comparison

	A: Self-Contained	B: References	C: Copy to Dist
Build step	None	Update manifests	Copy files + manifests
Duplication	Full	None	In dist/ only
Complexity	Lowest	Medium	Highest
Platform compat	All	Needs testing	All
Best for	Few shared skills	Many shared, simple setup	Many shared, strict isolation

Recommendation: Start with Option A (current). Move to B or C when shared skill duplication becomes a maintenance burden.