wix-cli-orchestrator

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

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/yaelbro/Shelf-Control --skill wix-cli-orchestrator-yaelbro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-orchestrator
Source: https://github.com/yaelbro/Shelf-Control/tree/main/.agents/skills/wix-cli-orchestrator
Command: npx skills add https://github.com/yaelbro/Shelf-Control --skill wix-cli-orchestrator-yaelbro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the correct Wix CLI extension type (dashboard page, modal, plugin, service plugin, event, data collection, site widget, and more) is error-prone, and building one involves coordinating SDK discovery, implementation, and validation. This Skill acts as a decision-maker and orchestrator that routes each feature request to the right extension skill and enforces a complete build workflow. ## Core Features & Use Cases - Extension Type Decision Engine: Decision tables and flowcharts map requirements (admin UI, backend logic, data storage, site components) to the correct Wix CLI extension 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 implicit CMS collection needs, coordinates app namespaces, and propagates scoped collection IDs to all sub-agents. - 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 all manual setup steps. ## Quick Start Ask the assistant to build a Wix app feature, such as "add a dashboard page that displays my store products," and this Skill will load first to plan and orchestrate the implementation.

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?

Match your use case to the decision table: admin interfaces map to dashboard pages, modals, or plugins; backend logic maps to service plugins, event extensions, or HTTP endpoints; data storage maps to data collections; and site-facing UI maps to site widgets, components, or plugins.

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 Wix Data Collection extension?

You need one whenever app-specific data must be saved, a dashboard manages domain entities, or a service plugin reads app-configured data at runtime. It requires an app namespace from the Wix Dev Center, and collection IDs are scoped as namespace/idSuffix.

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 two incompatible catalog versions: V1 uses the products module while V3 uses productsV3. Every Stores operation must call getCatalogVersion() first and then use the matching module, since V1 and V3 are not backwards compatible.

Which Wix extension can consume a context provider extension?

Only site components built with the wix-cli-site-component skill can consume context provider extensions. Site widgets and site plugins do not support consuming context providers.