wix-cli-orchestrator

Orchestrates Wix CLI extension selection, implementation sub-agents, and validation workflows.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/nirganon/nir-beauty --skill wix-cli-orchestrator-nirganon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-orchestrator
Source: https://github.com/nirganon/nir-beauty/tree/main/.agents/skills/wix-cli-orchestrator
Command: npx skills add https://github.com/nirganon/nir-beauty --skill wix-cli-orchestrator-nirganon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building features for Wix CLI apps requires choosing among many extension types (dashboard pages, modals, plugins, service plugins, site widgets, data collections) and coordinating SDK discovery, implementation, and validation. This Skill removes that guesswork by acting as a decision-maker and orchestrator that routes each feature request to the correct extension type and workflow. ## Core Features & Use Cases - Extension Type Selection: Decision tables and flowcharts map requirements (admin UI, backend logic, site components, data storage) to the correct Wix CLI extension type and its corresponding implementation skill. - Sub-Agent Orchestration: Spawns discovery sub-agents for missing SDK methods and implementation sub-agents with full context, supporting parallel execution for independent extensions. - Data Collection Inference: Automatically detects when app data persistence is needed, coordinates app namespace and scoped collection IDs across extensions. - Validation & Manual Steps: Enforces a mandatory checklist ending with the wix-cli-app-validation skill and aggregates all manual action items for the user. - Use Case: A user asks to "add a dashboard page to manage shipping fees with a service plugin that applies them at checkout." The Skill infers the Data Collection need, obtains the app namespace, spawns parallel implementation sub-agents, runs validation, and surfaces manual setup steps. ## Quick Start Ask the assistant to build a feature for your Wix CLI app, such as "add a dashboard page to manage product recommendations for my Wix app."

Frequently Asked Questions about wix-cli-orchestrator

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

FAQPage Schema
How do I choose the right Wix CLI extension type for my feature?

Use the decision flow based on audience and placement: admin interfaces map to dashboard pages, modals, or plugins; backend logic maps to service plugins, event extensions, or HTTP endpoints; site-facing features map to site widgets, components, or plugins. The Quick Reference Table maps each type to its implementation skill.

What is the difference between a Wix site widget, site component, and site plugin?

A site widget is a standalone interactive component placed anywhere on the site. A site component is a React component with an editor manifest for styling, content, and elements. A site plugin occupies a fixed slot on a Wix business solution page.

When do I need a Data Collection extension in a Wix CLI app?

Create a Data Collection extension whenever the app stores or manages its own data, such as dashboard CRUD pages or service plugins reading configured rules at runtime. It requires an app namespace from the Wix Dev Center and produces scoped collection IDs used by other extensions.

Can a Wix dashboard page open a modal?

Dashboard pages cannot use the Modal component directly. Create a separate Dashboard Modal extension and open it from the page using dashboard.openModal().

Why must Wix Stores API calls check the catalog version first?

Wix Stores has incompatible V1 and V3 catalogs, so code must call getCatalogVersion() and then use productsV3 for V3 or products for V1. The wix-stores-versioning skill enforces this check in all Stores-related implementations.

Which Wix APIs require SDK discovery before implementation?

Vertical APIs like Wix Stores, Bookings, Members, Pricing Plans, and Triggered Emails require discovery via MCP documentation search. Platform APIs like Wix Data, Dashboard SDK, common events, and service plugin SPIs are already covered in reference files and skip discovery.