wix-cli-extension-registration

Registers Wix CLI extensions with the app builder in src/extensions.ts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @wix/astro.

What problem does it solve? Newly created Wix CLI extensions do not appear or function until they are registered in the central src/extensions.ts file, and a missing .use() call is the most common cause of extensions silently failing. ## Core Features & Use Cases - Extension Registration: Import extension builders and chain them with .use() calls in src/extensions.ts so dashboard pages, site widgets, service plugins, event handlers, and embedded scripts are discovered by the build system. - Simple and Advanced Patterns: Use direct import-and-chain registration for small apps, or programmatic registration via a re-export index file for large apps with many extensions. - Naming and Troubleshooting Guidance: Apply the {extensiontype}{CamelCaseName} export naming convention and diagnose issues like missing .use() calls, wrong import paths, and export name mismatches. - Use Case: After generating a new dashboard page extension, add its import and .use(dashboardpageMyPage) call to src/extensions.ts so the page appears in the Wix dashboard sidebar. ## Quick Start Register my new extension by adding its import and .use() call to src/extensions.ts.

Frequently Asked Questions about wix-cli-extension-registration

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

FAQPage Schema
How do I register a Wix CLI extension in my app?

Import the extension from its extensions.ts file into src/extensions.ts and add a .use(extensionName) call to the app() builder chain. The Wix CLI discovers extensions only through this single entry point.

Why is my Wix extension not appearing after I created it?

The most common cause is a missing .use() call in src/extensions.ts. Without registration, dashboard pages won't appear in the sidebar, widgets won't show in the Editor, and plugins won't be invoked.

Which Wix extension types do not require registration in extensions.ts?

Backend API extensions do not require registration because Astro server endpoints are auto-discovered by the build system. All other extension types must be registered via .use() calls.

What naming convention should Wix extension exports follow?

Export names follow the pattern {extensiontype}{CamelCaseName}, where the type prefix is lowercase with no separators. Examples include dashboardpageCartPopupManager, embeddedscriptCouponPopup, and sitewidgetCountdownWidget.

How do I register many Wix extensions in a large app?

Re-export all extensions from a central src/index.ts file, then import the module namespace in src/extensions.ts and loop over Object.values() calling appBuilder.use() for each extension programmatically.