Generic

What you’ve got in the skill

The docs were authored for one host stack (Vite + react-router, .jsx, files pre-copied into src/) — you may be on another, so adapt these assets to your stack; don’t copy the host’s setup. Everything is under .agents/skills/wix-vibe-headless/references/.

Shared transport — both files, used by every vertical (shared/app/rest/):

Every references/<vertical>/ holds the same four things:

• app/rest/wix-*.js — the vertical’s data layer: named calls carrying the exact request/response shapes, fieldsets, and paging.
• app/{components,pages,hooks,context}/… — a reference UI (+ hooks/providers) built on that data layer; the field shapes and route patterns it uses (e.g. /product/:slug) are the data contract.
• seed/seed-*.js — build-time seeding functions that create content.
• INSTRUCTIONS.md — the vertical’s build guide + field-shape snippets; seed/SEED.md — how the seed module is run.

The nine verticals — data layer (app/rest/) + seed module (seed/):

Anything in the docs about the host’s own setup — copying files into src/, its @/ alias, its import.meta.env flags, a theming file, its build/exec/connector tooling — is that host’s, not a rule: adapt it to your stack or ignore it. The SKILL.md “shared model” (public-client-id auth, money = objects → render formattedValue, visitor token = cart identity, member login swaps the token set) is universal — follow it as-is.

The flow — install → build client → seed → done

Run build the client (step 2) and seed (step 3) in parallel; parallelize independent work within each.

1 · Install the skills

Two skills, into .agents/skills/: wix-vibe-headless (this build guide + the seed modules — self-contained) and wix-docs (fallback to search/read the Wix API reference).

2 · Build the client

Pull the whole client reference into context in two reads — this is basically your prompt: it’s all the client code you need. Build the client from it in your own stack’s idiom (your router, file extensions, design tokens), and set WIX_CLIENT_ID + WIX_METASITE_ID in wix-config.

3 · Seed the content

⛔ NO CLEANUP — EVER. Strictly additive: never delete, reset, or overwrite anything on the user’s live site — not even apparent sample/demo content. If something looks wrong, leave it and tell the user.

Auth (the public client id won’t do): if your platform has a built-in Wix connector, use it (it holds the credential). Otherwise take a Wix API key into your secrets manager (never hardcode or commit) — create one at account API keys → Add key (opens in a new tab) (how-to (opens in a new tab)) — and send it raw as Authorization (no Bearer) with a wix-site-id header (wix-account-id only for account-level APIs — one, not both):

Pull the seed code into context — this is your seeding prompt: it’s all the code you need. Run these functions (adapting the exec + auth to your platform) to create the content:

They encode the Wix API sequences (incl. app-install + provisioning-race handling); use wix-docs for anything they don’t cover. Content queries return REQUIRED_APP_NOT_INSTALLED until the app is installed + seeded (expected; the seed modules install it first). Image seeding = two Wix Media calls (generate-upload-url → PUT the bytes) before attaching.

4 · Done

Mount the dev-only manage banner (regenerate WixManageBanner for your stack — it reads WIX_METASITE_ID from wix-config, already set in step 2, and self-hides while it’s still the placeholder; mount above the header, SSR-safe, portable dev-gate, never in production), then tell the user to open https://manage.wix.com/dashboard/{metaSiteId} to finish setup in Wix (payments, content).