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.