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.

referencesBUSINESS_MANAGER_PATTERNS.md

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

Business Manager theme for @wix/patterns — the second wrapper

Companion to BUSINESS_MANAGER_THEME.md. That wrapper themes the design system; this one turns on the patterns shell's own Harmony layout. A page built on @wix/patterns needs both.

Verified against @wix/patterns 1.501.0 and @wix/dashboard 1.3.48.

1. Why the WDS theme isn't enough

Patterns does not take its Harmony layout from the WDS theme. Its toolbar, search, filters, page headers and side panels switch on the bmHarmonyTheme experiment, and no experiment crosses into an extension iframe: @wix/dashboard implements no experiments host, so patterns falls back to reading every experiment as false.

The result is a hybrid page — Harmony tokens and icons around the pre-redesign patterns layout. The tell is the collection toolbar: an outlined Filter button and a pill-shaped search, where Harmony has a borderless Filter button and a standard search field. tsc, wix build and wix preview all pass on it.

An experiment override on the Business Manager URL stays in the parent frame, and neither wix.config nor the CLI has a setting for this. The lever is the patterns container itself: WixPatternsContainerOverridesProvider is the documented container override, and patterns applies its values last when it builds the container.

2. The wrapper — write this file once per app

// src/extensions/dashboard/BusinessManagerPatternsTheme.tsx
import type { FC, ReactNode } from 'react';
import { WixPatternsContainerOverridesProvider } from '@wix/patterns';
import type { WixPatternsContainerParams } from '@wix/patterns/core';

const BM_HARMONY_THEME_EXPERIMENT = 'bmHarmonyTheme';

const HARMONY_CONTAINER_OVERRIDES: Partial<WixPatternsContainerParams> = {
  experiments: {
    enabled: (key) => key === BM_HARMONY_THEME_EXPERIMENT,
    get: (key) => (key === BM_HARMONY_THEME_EXPERIMENT ? 'true' : ''),
    ready: () => Promise.resolve(true),
  },
};

export const BusinessManagerPatternsTheme: FC<{ children: ReactNode }> = ({ children }) => (
  <WixPatternsContainerOverridesProvider value={HARMONY_CONTAINER_OVERRIDES}>
    {children}
  </WixPatternsContainerOverridesProvider>
);
  • A separate file, not part of BusinessManagerTheme. Plugins and most modals don't install @wix/patterns, and the shared wrapper has to compile without it.
  • It replaces the host's experiments outright. That costs nothing, because inside the iframe every other key already reads false. Don't add other keys to it: patterns' other experiments are its own rollouts, not app settings.

3. Where it goes

Every surface that renders WixPatternsProvider — in practice every page built from a patterns template — takes it directly inside BusinessManagerTheme, above WixPatternsProvider. Patterns reads the overrides once, when WixPatternsProvider first renders, so an override provider below it, or a value changed after mount, does nothing.

In a page template that is the entry file, around the template's app component:

<BusinessManagerTheme>
  <BusinessManagerPatternsTheme>
    {location ? <ItemsApp location={location} /> : null}
  </BusinessManagerPatternsTheme>
</BusinessManagerTheme>

Pickers and the other containers patterns nests inherit it, so they need no second override provider.

4. Verify

  • Every WixPatternsProvider sits below BusinessManagerPatternsTheme, which sits directly inside BusinessManagerTheme.
  • On a collection page in the dashboard, the toolbar's Filter button has no border and the search field is not pill-shaped. An outlined Filter button or a pill search means patterns never got the experiment: the override provider is missing, or it sits below WixPatternsProvider.

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.