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.

referencesEXTENSION_METADATA.md

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

Extension Metadata: name and aiContext

wix generate scaffolds builder files without the metadata Wix uses for logs and for its AI. Finish each scaffolded *.extension.ts by adding it:

  • name on a backend event or service plugin — a short title-case label of what the extension does, trigger first, then action: "New Member Created", "Order Paid Send Receipt", "Weekend Delivery Fee". In a @wix/custom-extensions project the build slugifies it into the URL site monitoring logs show: /_wix/extensions/webhooks/new-member-created/<id> for an event, /_wix/extensions/service-plugins/weekend-delivery-fee/<id> for a service plugin; an event with no name logs as /_wix/extensions/webhooks/webhook/<id>. A service plugin's scaffolded name is its folder path, so replace it.
  • aiContext: { description } — one or two plain sentences on what the extension does for the site owner and when it runs. Wix's AI reads it to understand the extension.

Read the scaffolded import first

The builder package decides which fields exist:

  • import { extensions } from '@wix/custom-extensions' — follow the table below.
  • import { extensions } from '@wix/astro/builders' — its builders declare no aiContext and no name on an event, and its URLs carry no name. Replace the service plugin's folder-path name with the title-case label and add nothing else.

Where each field goes (@wix/custom-extensions 1.0.6)

extensionType Builder name aiContext
EVENT extensions.event() add it (optional in the type) top level
SERVICE_PLUGIN — eCom (ecomAdditionalFees, ecomShippingRates, ecomDiscountTriggers, ecomValidations, ecomPaymentSettings, ecomGiftCards) and bookingsStaffSortingProvider per SPI replace the folder path top level
SERVICE_PLUGIN — the other Bookings providers, realtimePermissionsProvider, toolsProvider per SPI replace the folder path not accepted
DATA_COLLECTION extensions.dataCollections() keep the scaffolded value top level
DASHBOARD_PAGE extensions.dashboardPage() — metaData.aiContext, beside the scaffolded searchable and description
DASHBOARD_MODAL extensions.dashboardModal() — metaData: { aiContext }
DASHBOARD_PLUGIN extensions.dashboardPlugin() — top level
DASHBOARD_MENU_PLUGIN extensions.dashboardMenuPlugin() — top level

Versions 1.0.5 and earlier take neither name on an event nor any aiContext. The installed builder's options type is the authority: add a field only where it declares one.

Example

Scaffolded values (…) stay as the CLI wrote them.

import { extensions } from '@wix/custom-extensions';

export default extensions.event({
  id: '…',
  name: 'Order Paid Send Receipt',
  aiContext: {
    description: 'Emails the buyer a branded receipt as soon as an order is paid.',
  },
  source: '…',
});
export default extensions.dashboardPage({
  id: '…',
  title: 'Delivery Fees',
  routePath: 'delivery-fees',
  component: '…',
  fullPage: false,
  metaData: {
    searchable: true,
    description: 'Manage Delivery Fees in your dashboard.',
    aiContext: {
      description: 'Lets the site owner set the weekend delivery fee amount and the days it applies.',
    },
  },
});

Done when

npx tsc --noEmit passes and every extension this run scaffolded carries each field its builder declares. A tsc error like Object literal may only specify known properties, and 'aiContext' does not exist means that builder version lacks the field: remove it from that file and keep the rest.

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.