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-componentDIRECTIONALITY.md

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

Directionality (RTL/LTR)

Use these rules for component direction, logical layout, nested content, and direction-dependent JavaScript.

Contents

Root Contract

Every component accepts direction?: Direction. Put dir={direction} and the fallback class on the elected root; do not add a wrapper for them. Apply the fallback class unconditionally so it works whenever dir is absent. Preserve the scaffolded dir, root class, and .fallbackDirection:not([dir]) wiring; the generated component already demonstrates this contract.

Do not set fallback direction with a React condition or a custom direction CSS variable.

Logical CSS

Use logical inline-axis properties instead of physical left/right properties:

.element {
  inset-inline-start: 0;
  padding-inline-start: 8px;
  margin-inline-end: 4px;
  border-inline-end: 1px solid currentColor;
}

Block-axis properties such as top, bottom, and padding-block do not need directional conversion.

Direction-Dependent Transforms

For directional transforms, use the platform multiplier:

.arrow {
  scale: var(--wix-opt-in-direction-multiplier, 1) 1;
}

Direction-Dependent JavaScript

Use useLanguageDirection() only when direction changes JavaScript behavior, such as arrow-key order, scroll math, animation direction, or conditional rendering. Purely visual direction belongs in logical CSS.

import { useLanguageDirection } from '@wix/react-component-utils';

const siteDirection = useLanguageDirection();
const resolvedDirection = direction ?? siteDirection;
const isRtl = resolvedDirection === 'rtl';

Nested ReactNode Content

Put dir="ltr" on the element that renders a ReactNode content prop. This isolates arbitrary nested content from the parent component's direction so each nested component can resolve its own contract.

<div dir="ltr">{item.content}</div>

Checklist

  • Root props include direction?: Direction.
  • The elected root has dir={direction} and the unconditional fallback class.
  • Direction-sensitive CSS uses logical properties.
  • Runtime direction hooks are used only for JavaScript behavior.
  • Every ReactNode content slot renders under dir="ltr".

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.