wix-cli-orchestrator

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

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/thisisjaymehta/login-with-email-test --skill wix-cli-orchestrator-thisisjaymehta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-orchestrator
Source: https://github.com/thisisjaymehta/login-with-email-test/tree/main/.agents/skills/wix-cli-orchestrator
Command: npx skills add https://github.com/thisisjaymehta/login-with-email-test --skill wix-cli-orchestrator-thisisjaymehta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the correct Wix CLI extension type (dashboard, backend, site, or data collection) and coordinating its implementation is error-prone, often leading to wrong extension choices, missed data collection needs, and unvalidated builds. ## Core Features & Use Cases - Extension Type Decision Support: Decision tables and flowcharts map requirements (admin UI, backend logic, site components, data storage) to the correct extension type and its corresponding skill. - Sub-Agent Orchestration: Enforces a structured workflow of reference checking, optional SDK discovery, parallel implementation sub-agents, and mandatory validation via the wix-cli-app-validation skill. - Data Collection Inference: Automatically detects implicit CMS collection needs and coordinates app namespace and scoped collection IDs across sub-agents. - Use Case: When a user asks to build a dashboard page that manages fee rules applied at checkout, the skill recommends a Dashboard Page plus Service Plugin plus Data Collection, spawns implementation sub-agents in parallel, and validates the build. ## Quick Start Ask the assistant to build a Wix app feature, such as adding a dashboard page to manage product fees, and it will select the right extensions and coordinate 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 app feature?

Match your use case to the extension category: admin interfaces use Dashboard extensions, server-side logic uses Backend extensions, data storage uses Data Collection, and visitor-facing UI uses Site extensions. The skill's decision flow and quick reference table map placement, visibility, and functionality to the correct type.

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 supporting 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?

You need one whenever app-specific data must be saved or managed, such as a dashboard managing domain entities or a service plugin reading configured rules at runtime. It requires an app namespace from the Wix Dev Center and produces scoped collection IDs.

Can a Wix dashboard page open a modal?

Dashboard Pages cannot use the Modal component directly. You must create a separate Dashboard Modal extension and open it from the page using dashboard.openModal().

How does Wix Stores API versioning affect my app implementation?

All Wix Stores operations must first call getCatalogVersion() to determine the catalog version, then use productsV3 for V3 catalogs or products for V1. V1 and V3 are not backwards compatible, so the version check is mandatory.

Which Wix APIs require SDK discovery versus reference files?

Platform APIs like Wix Data, Dashboard SDK, common events, and Service Plugin SPIs are covered in reference files and need no discovery. Vertical APIs like Wix Stores, Bookings, Members, and Pricing Plans require a discovery sub-agent using MCP documentation search.