wix-cli-orchestrator

To orchestrate Wix CLI extension development, you need a workflow that determines the extension type, checks existing references for APIs, spawns discovery for missing contexts, implements via parallel sub-agents, and runs final app validation.

Automating Wix CLI extension implementation is best handled by coordinating parallel sub-agents that work on independent frontend UI and backend services simultaneously, accelerating delivery while ensuring all steps are documented.

API discovery for Wix CLI extensions works by first checking skill references to reuse existing APIs, then spawning targeted discovery sub-agents only for missing APIs to collect the required SDK context before implementation begins.

Yes, you need to run wix-cli-app-validation after creating a Wix CLI extension. The orchestration flow requires executing this validation skill to verify the implementation and report completion with test guidance.

Yes, you can use Wix CLI orchestration to build different extension types. It determines the appropriate extension type, such as a Dashboard Page, Site Widget, or Service Plugin, based directly on your specific user requirements.

Wix CLI extension orchestration skips the discovery phase for certain APIs because it checks skill references first to reuse existing APIs, spawning discovery only for APIs not already covered by those references.