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.

referencesdashboard-pageIMAGE_RENDERING.md

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

Images in collection and detail pages

This applies to every data source: CMS, Stores, Bookings, and other SDK or custom collections. An image value is not necessarily a browser URL. A wix:image:// URI passed directly to WDS Image or a native <img> produces a broken image even when the page builds and its data loads.

Use the field renderer when the schema supplies one

Keep the source's image field type and original value when using schema-driven Patterns collections or entity fields. Their image renderers handle the supported URI and structured image formats. Do not replace them with a custom WDS renderer just to show an image.

Custom image rendering

Read the source's image field declaration before mapping it. Select the image value, not the whole media container: a media item can also be a video or document. Check its media type before using a generic url as an image, or use its documented image thumbnail field.

Use the installed SDK's return type, not the raw REST response shape. SDK decoding can turn a REST image object into a wix:image:// string. Reading .url from that string returns undefined, so the page shows its empty state without ever rendering an image. Do not copy REST field access into an SDK mapper or hide this mismatch with a type assertion.

For custom WDS or native image rendering, extract a string from the image value and convert Wix URIs with the documented SDK helper. Preserve ordinary HTTP(S) URLs and missing values:

import { media } from '@wix/sdk';

type ImageValue = string | { uri?: string; url?: string } | null | undefined;

export function toBrowserImageUrl(value: ImageValue): string | undefined {
  const source = typeof value === 'string' ? value : value?.uri || value?.url;
  return source?.startsWith('wix:image://')
    ? media.getImageUrl(source).url
    : source;
}

This accepts image URI strings and structured image values with uri or url. Extract nested image fields according to their own types before calling it. Do not stringify a media object, hand-build a CDN URL, or send a video URI to an image renderer.

Use the derived URL in collection thumbnails, grid cards, and detail previews. Show an empty state when it is absent. Keep it separate from the original entity and form value: saves must retain the source's image format, alt text, dimensions, and other metadata.

Normalize the source image value before choosing a fallback or an empty state, in both the list and the detail fetch paths. A working thumbnail does not establish that the detail query returns the same fields. Request any fields required by the fallback too. Stores' mapping is shown in STORES_VERSIONING.md.

Verify a Wix-hosted image in both the collection and detail views, an external image URL, and an item without an image. When browser access is available, open a row and check that its image actually loads (complete and naturalWidth > 0), rather than only checking that an <img> exists. If a known image shows an empty state, trace the SDK value through its mapper before reporting completion. A successful build or a raw REST response does not verify the rendered SDK result. If browser access is unavailable, report image rendering as unverified.

See Work with Wix Media for the SDK URI format and conversion API.

For editable entity images, follow IMAGE_EDITING.md.

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.