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-componentPROPS-VS-CSS.md

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

Props vs CSS

Use this reference to decide whether a value belongs in the public React contract, component logic, or editable CSS.

Decision Table

Value controls Put it in Examples
User-authored content or data React prop label, items, image, link
Stable runtime behavior React prop disabled, required, autoPlay, loop
Value derived from props or state Component logic subtotal, active count, formatted label
Appearance or layout CSS spacing, alignment, orientation, icon position
Breakpoint-specific visibility CSS/editor controls show label, compact layout, mobile visibility
Direction React prop plus logical CSS direction?: Direction

Ask in this order:

  1. Can the value be derived? Compute it internally.
  2. Does it select content or stable behavior? Use a prop.
  3. Could a site owner reasonably vary it by breakpoint? Use CSS/editor controls.
  4. Otherwise, keep visual and layout choices in CSS.

Visibility Rules

Do not add showLabel, showIcon, hideOnMobile, displayMode, or similar props for purely presentational visibility. Render the named part and let the editor control that part per breakpoint.

Use this pattern:

<div
  {...elementProps?.progressBar}
  className={classNames(
    'audio-player-progress-bar',
    styles.progressBar,
    elementProps?.progressBar?.className,
  )}
>
  {/* progress UI */}
</div>

Do not interpret this rule as "never conditionally render." Conditional output is valid when data, semantics, or runtime behavior requires it—for example an empty-state message, a loading branch, or content that does not exist.

Behavior-critical visibility may also be a prop when visibility itself changes the interaction contract. pauseButtonVisibility in an autoplaying component is the canonical exception: the editor preview must be able to force the play/pause control visible.

Examples

Content and Behavior Props

export type AudioPlayerProps = {
  title?: string;
  audioUrl?: string;
  disabled?: boolean;
  autoPlay?: boolean;
};

Visual Decisions Kept Out of Props

// Do not add these to the public contract:
// showIcon?: boolean
// orientation?: 'horizontal' | 'vertical'
// compact?: boolean
// hideOnMobile?: boolean

Define their resting appearance in the CSS Module and expose independently editable elements as named parts with global/module classes and elementProps wiring.

Checklist

  • Props represent authored data or stable behavior.
  • Derived values are computed internally.
  • Visual and layout choices live in CSS.
  • Breakpoint visibility uses a named part, not a show/hide prop.
  • Conditional rendering is used only for real data, semantic, or behavioral branches.

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.