All skills
wix avatar

/wix-app

@dc6f1fa official
by Wix.comwix/skills33 stars
33

Build and review Wix CLI app extensions — dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, 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, checkout, shipping, tax, discount, SPI, CMS, schema, tracking, popup, 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

This session only. Nothing lands on disk.

referenceseditor-react-componentCOMPONENT-PREVIEW.md

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

Editor Preview Entry

Use this when creating a component or changing its data, root, or editor-only behavior.

Preserve the Structure, Synchronize the Contract

The Wix CLI scaffold generates component.preview.tsx and wires its URL into the extension's editor resource. It includes withDefaults, withFallbackPlaceholder, required-data fields, and the root class name.

Keep the wrapper structure and synchronize its values. The renderer detects preview defaults only when withDefaults wraps the result of withFallbackPlaceholder. The calls may be nested directly:

export default withDefaults(
  withFallbackPlaceholder(ComponentPreview, {
    requiredDataFields: ['animationUrl'],
    rootClassName: 'component-root',
  }),
  defaultProps,
);
  • Wrap the preview adapter when one exists; otherwise wrap Component.
  • In requiredDataFields, normally use only the one prop crucial to meaningful rendering, such as animationUrl. Use more only when each is essential.
  • Set rootClassName to the elected root's exact global class, not styles.root.

Never remove either wrapper, export withFallbackPlaceholder(...) directly, or invert their order. Preserve the equivalent of withDefaults(withFallbackPlaceholder(...), defaultProps) even when editing the preview component or fallback options. Assigning either wrapped component to a variable is valid as long as that outer-to-inner order stays intact.

Detect Editor Design Mode

Use useIsEditMode() from @wix/react-component-utils:

const isEditMode = useIsEditMode();
  • true: editor design mode
  • false: editor preview mode or live-equivalent rendering

Call the hook inside a React component, never at module scope or conditionally.

Modify Only When Needed

Keep the generated passthrough unchanged unless the component requires editor-specific runtime behavior. The primary case is suppressing autoplay, timers, or network activity while a site owner is designing.

For autoplaying components, force autoplay off in editor design mode and keep the live/preview prop values unchanged.

Pass the adapter to withFallbackPlaceholder, then pass that wrapped component to withDefaults. This may be written inline as shown above or through component variables. Synchronize the data field and root class either way.

Checklist

  • Generated wrappers target the preview adapter when one exists.
  • The default export resolves to withDefaults outside withFallbackPlaceholder, whether inline or through component variables.
  • Normally one crucial data field and the exact root global class are set.
  • The extension still loads the preview URL as its editor resource.
  • useIsEditMode() is called inside a component.
  • Live/preview behavior still receives the site owner's original props.

Source: SKILL.md on GitHub

1 warningtoday4 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill is a specialized development toolkit for building extensions on the Wix platform. It provides comprehensive instructions for creating dashboard pages, backend APIs, and site plugins using the Wix CLI and SDKs. No malicious patterns were detected; the skill's behaviors, such as dependency management, command execution for builds, and local script execution for code reviews, are entirely consistent with its purpose as a developer productivity tool for the Wix ecosystem.

  • Sockettoday

    1 alert: gptAnomaly

  • Snyktoday

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub yesterday.

Activeupdated 2 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.