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.

referencescontext-providerLOADING.md

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

Loading and Async Data

Applies to every promise, without exception — any Wix SDK call, any fetch, any backend or service-plugin call, any await. A fast promise is not an exemption: it still resolves after the first render, so the gate still closes. Only a provider whose state is entirely synchronous — a counter, a toggle, the current date — needs nothing here; for one of those see Counter with a goal-gated banner.

Section Read it for
The Render Gate Why an async provider blanks its whole subtree
Why not useEffect The obvious alternative, and why it loses SSR
The Pattern The complete provider and registration — copy this
Name the Entity Type, Do Not Derive It The one type-derivation trap; it breaks against every SDK
Why It Splits Into Three Components What use() forces, and the two bugs it causes
The fallback is a provider, not children Why a bare fallback breaks the section permanently
Lock the initial promise Where the promise must live, and the substitutes that fail
Does the provider refetch? What to leave out when it does not — including the data state
Commit later fetches only when the data is ready Why the ordering is what keeps stale content on screen
Values that describe the data Why a label must not run ahead of the rows it labels
Read the clock once, next to the fetch Why new Date() in a render body discards the server render
The Loading Pair Is Mandatory isPlaceholderHidden / isContentHidden — what each means and what to bind
Server Rendering and the Fallback When the fallback is visitor-facing
The Fetch Wrapper Must Never Reject Error handling that does not take down the subtree

The Render Gate

A context provider makes one binary decision for its entire subtree: render everything, or render nothing. While its initial data is unresolved nothing inside it renders, and that decision is not scoped to the bindings — the provider cannot tell which children read its data, so an unbound "Contact Us" button disappears along with the service name it has nothing to do with. Only the page shell outside the provider keeps rendering.

There is no platform-level loading mechanism. No skeleton, no spinner, no phased reveal. Any loading experience a page has was built by the provider.

Why not useEffect

Fetching in a useEffect and writing the result to state also avoids the blank subtree, with none of the machinery below — no polyfill, no split, no fallback. It is the obvious move, and it is the wrong one here: effects do not run on the server. The server would render the provider with no data and ship that HTML, so the visitor gets the content popping in after hydration, and a crawler that does not execute JavaScript sees an empty section. Resolving the promise with use() is what lets the server render real content — that is the whole point of the pattern, and the reason it is worth the extra components.

Use useEffect for side effects that genuinely belong on the client. Do not use it to load the data a context provider exposes.

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.