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.

referencesAPP_VALIDATION.md

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

Wix App Validation

Validates Wix CLI applications through a four-step sequential workflow: package installation, TypeScript compilation check, build, and preview.

Validation Workflow

Execute these steps sequentially. Stop and report errors if any step fails.

Step 1: Package Installation

Ensure all dependencies are installed before proceeding with the build.

Detect package manager:

  • Check for package-lock.json → use npm
  • Check for yarn.lock → use yarn
  • Check for pnpm-lock.yaml → use pnpm
  • Default to npm if no lock file is found

Run installation command:

# For npm
npm install

# For yarn
yarn install

# For pnpm
pnpm install

Success criteria:

  • Exit code 0
  • All dependencies installed successfully
  • No missing peer dependencies warnings (unless expected)
  • node_modules directory exists and contains expected packages

On failure: Report the installation errors, check the debug log for detailed diagnostics, and stop validation. Common issues:

  • Network connectivity problems
  • Corrupted lock files
  • Version conflicts
  • Missing Node.js or package manager

Step 2: TypeScript Compilation Check

Run TypeScript compiler to check for type errors.

npx tsc --noEmit -p .

Run it from the app root, and check the whole project rather than just the files you generated — a type error in generated code usually surfaces in the file that consumes it. -p . is what holds that line: adding a file path to it is an error, whereas adding one to a bare npx tsc --noEmit silently discards tsconfig.json (strict, paths, jsx) and checks against compiler defaults instead.

Success criteria:

  • Exit code 0
  • No TypeScript compilation errors
  • All type checks pass

On failure: Report the specific TypeScript errors and stop validation. Common issues:

  • Type mismatches between expected and actual types
  • Missing type declarations for imported modules
  • Incorrect generic type parameters
  • Properties not existing on declared types
  • Incompatible function signatures

Step 3: Build Validation

Run the build command and check for compilation errors:

npx wix build

Success criteria:

  • Exit code 0
  • No TypeScript errors
  • No missing dependencies

On failure: Report the specific compilation errors, check the debug log for detailed diagnostics, and stop validation.

Step 4: Preview Deployment

npx wix preview is a one-shot command, not a server: it uploads a preview build, prints the preview URLs and exits on its own, in seconds. Run it in the foreground and read its output:

npx wix preview

Don't wrap it in timeout (macOS has none, so the call fails before preview runs), background it, sleep or poll a log for it, or kill it afterwards. There is no process left to wait for or stop.

Success criteria:

  • The command exits 0
  • It printed ✔ Preview created successfully! and the preview URLs

URL extraction: the URLs follow Open the preview on:, one per line, each in parentheses:

  › Site (https://www.wix.com/app-installer?appId=...)
  › Editor (https://www.wix.com/app-installer?appId=...)
  › Dashboard (https://www.wix.com/app-installer?appId=...)

A long URL wraps across several lines. Join the lines up to the closing ) before using it. Give the Site and Dashboard URLs to the user for manual verification.

On failure: Report the preview errors, check the debug log for detailed diagnostics, and stop validation.

Validation Report

After completing all steps, provide a summary:

Pass:

  • Dependencies: ✓ All packages installed successfully
  • TypeScript: ✓ No compilation errors
  • Build: ✓ Compiled successfully
  • Preview: ✓ Created — [Dashboard URL]

Fail:

  • Identify which step failed
  • Provide specific error messages
  • Suggest remediation steps

Debug Log on Errors

When a validation step fails (non-zero exit code, error output, or the CLI crashes/hangs), check .wix/debug.log in the project root for the full error trace. Only read this file when errors occur — skip it when steps pass or when the terminal output already makes the error clear (e.g. a straightforward TypeScript type error).

The .wix/ directory is automatically created by the Wix CLI and contains internal configuration and log files. Don't edit it, but reading debug.log for troubleshooting is expected.

Read: .wix/debug.log

# If the file is large, read the last 100 lines for the most recent errors
Read: .wix/debug.log (with offset to the end)

Common Issues

Issue Cause Solution
Package installation fails Missing lock file, network issues, or corrupted node_modules Delete node_modules and lock file, then reinstall
TypeScript compilation fails Type mismatches, missing declarations, or incorrect types Fix TypeScript errors shown in npx tsc --noEmit -p . output
Build fails TypeScript errors, missing dependencies, or internal CLI error Fix TypeScript errors in source; for non-obvious failures, check .wix/debug.log
Preview fails Config issue, not logged in, or internal CLI error Check wix.config.json; if unclear, check .wix/debug.log for details
Console errors in preview Runtime exceptions Check browser console output
UI not rendering Component errors Review component code and imports
CLI error with no clear message Truncated terminal output Read .wix/debug.log for the full error trace and stack details
Mysterious failures after config change Stale CLI state Read .wix/debug.log to confirm, then delete .wix/ and rebuild

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 yesterday
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.