Index of every page on this site: llms.txt
All skills
wix avatar

/wix-app

@e2bc48e official
by Wix.comwix/skills40 stars
42
Run it yourself

Build and review Wix CLI app extensions — dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, context providers, function libraries, lightbox (popup) behavior, page onLoad contexts, backend APIs, backend events, service plugins, data collections, and App Market readiness. Use when building ANY feature or extension for a Wix CLI app or preparing a Wix app for App Market review. Triggers on: add, build, create, implement, help me, dashboard, widget, plugin, backend, API, event, collection, embedded script, service plugin, Editor React component, context provider, function library, onLoad, on page load, checkout, shipping, tax, discount, SPI, CMS, schema, tracking, popup, lightbox, admin panel, menu item, modal, validate, test, verify, register extension, App Market, app review, submission readiness.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-app

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesfunction-libraryTROUBLESHOOTING.md

≈695 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Troubleshooting

Function not found at runtime

Cause: The exported function name in the library's {library-name}.ts does not match the key in the functions map.

Solution: Ensure every key in the functions map has an identically-named named export in the library's {library-name}.ts. The match is case-sensitive.

Text renders blank after binding a function

Possible cause: The function declares returns: { dataType: 'richText' } but returns an HTML string. The function can execute successfully while the target element receives a value without the required html field.

Solution: Match the implementation to the declaration. For richText, return a typed RichText object containing text, html, and linkList; see RichText values. For plain text, return a string and declare text instead.

Error: Parameter has both dataType and domEvent

Cause: A function parameter was defined with both dataType and domEvent.

Solution: Each parameter must have exactly one of dataType or domEvent, never both. Use dataType for data values and domEvent for browser events.

Error: Disallowed data type

Cause: A parameter or return type uses a deprecated or disallowed dataType such as onClick or onChange.

Solution: Replace deprecated event-handler data types with the corresponding domEvent value:

  • onClick → domEvent: 'POINTER'
  • onChange → domEvent: 'CHANGE'
  • onKeyPress/onKeyUp/onKeyDown → domEvent: 'KEYBOARD'
  • onFocus → domEvent: 'FOCUS'
  • onSubmit → domEvent: 'SUBMIT'

Error: Error during component specifier upsert

The checkpoint fails when a moduleSpecifier is already registered by another app (module specifiers are unique across all of Wix) or when an existing one was changed (a registered module specifier cannot be renamed). For a function library added since the last checkpoint, set resources.moduleSpecifier to <moduleSpecifierPrefix><its current value> (@/ by default, or the prefix the user gives you). For a library that already existed, restore the moduleSpecifier it had before (git log -p -- <its .extension.ts>). Change only that string; type, id and the files stay as they are.

Error: componentType already exists (code 2018)

Component type '<type>' is already registered by another component (code 2018, componentType already exists). The platform's background preview reports it. The type is built from name (<codeIdentifier>.<camelCaseName>) and is globally unique, so a second extension with the same name is rejected. Give the new extension a different name and type, and a different moduleSpecifier (never rename one that was already released).

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warningstoday4 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill provides a comprehensive environment and set of tools for building Wix CLI app extensions. It includes detailed instructions, API references, and local utility scripts for development tasks like SDK lookup and accessibility auditing. All operations and dependencies are standard for the Wix developer platform.

  • Sockettoday

    1 alert: gptAnomaly

  • Snyktoday

    Risk: MEDIUM · 1 issue

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e2bc48e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 6 days ago
compatibility
requires `@wix/cli` >= 1.1.192.

README badge

README badge for wix/skills/wix-app

Builds dashboard pages, modals, plugins, custom widgets, Editor React components, backend APIs, events, service plugins, and data collections for Wix CLI apps. Provides decision logic, API patterns, and validation workflows; scaffolding is owned by the Wix CLI via `wix generate --params`.

Generated from the current SKILL.md.

What extension types does this skill cover?
All Wix CLI app extension types: dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, backend APIs, backend events, service plugins, and data collections.
Does this skill scaffold the extension files for me?
The Wix CLI owns scaffolding via `wix generate --params` for all extension types except Backend API. This skill provides decision logic, API guidance, and business-logic patterns to fill in the generated stubs. Backend API files must be created manually.
What Wix CLI version is required?
The skill requires @wix/cli >= 1.1.192.
Do I need to create a Data Collection extension for app-specific data?
Yes, if you're saving or persisting app-specific data, managing domain entities in a dashboard, or running a service plugin that reads app-configured data. The skill infers this automatically—you don't need to explicitly request it.
Does this skill cover Wix Stores API usage?
Yes. When using any Wix Stores API (products, inventory, orders), the skill requires dual V1/V3 catalog support and references the Stores Versioning guide for module selection and field mapping.

Generated from the current SKILL.md. These answers refresh after source changes.