@wix/agent-skills 1.36.0 → 1.36.1

package/skills/wix-vibe-headless/platforms/base44-ecom-light-seed.md

@@ -1,121 +0,0 @@
-# Wix Managed Headless — Base44 storefront client + seed
-
-You are building a **Wix Managed** headless storefront inside Base44 — the business is described in your
-initial prompt, and the Wix connector is already configured.
-
-The shipped client is already configured. Use its documented hooks and components; no ID lookup
-or configuration changes are needed.
-
-> **The installed Wix skills are the complete build and seed path for this app.** **Do NOT use the Base44 commerce kit (or any Base44 solution kit).**
-
-**Banner disabled for this entry flow:** do not add `<WixManageBanner/>`; skip the shared
-storefront instructions' optional banner integration.
-
-## STEP 0 — Setup already completed by Base44
-
-These skills are already installed under `.agents/skills/`:
-- **`wix-vibe-headless`** — storefront build instructions, hook/component contracts, and seeding modules.
-- **`wix-manage`** — REST recipes for managing and configuring the Wix site.
-- **`wix-base44-connector`** — Wix connector usage, API contracts, and documentation discovery.
-
-Base44 has also deployed the storefront hooks, cart components/context, image helpers, REST
-scaffolds and the nav adapter (`src/lib/nav.js`) into `src/`, configured the Wix connector/client,
-and added the Wix note to `AGENTS.md`. No installation, deployment, or AGENTS.md update is needed.
-
-The deployed implementation and configuration files do not need to be read; use the build and seed
-guides below for their contracts and usage.
-
-**Mount pages the way this app's template expects** — ask `src/routes/__root.jsx` first: present →
-TanStack Start, where pages mount as route files and the deployed `src/lib/nav.js` needs swapping
-for `_shared/nav/nav.tanstack.js`; absent → React Router, routes wired into `src/App.jsx`. Building for the wrong one
-renders a blank preview with no error to explain it:
-[`../references/_shared/routing.md`](../references/_shared/routing.md).
-
-Continue with STEP 1.
-
-Follow STEPs 1–3 below exactly. Fire product image generations first, then build the client
-(STEP 1), and seed (STEP 2) **after** the client is built — generation finishes while you build.
-
-## STEP 1 — Build the client
-
-Read `.agents/skills/wix-vibe-headless/references/storefront/INSTRUCTIONS.md` and follow it **EXACTLY** — the single source of truth for how the storefront client is built.
-
-The shipped storefront provides catalog, cart, and checkout. Identify the additional workflows
-in the user's request and implement them alongside the storefront. If a workflow needs an
-external service or missing information, continue the work you can complete and identify the
-remaining dependency.
-
-For code or actions not covered by this skill, read and follow the installed connector skill at
-`.agents/skills/wix-base44-connector/SKILL.md` to find Wix documentation and APIs.
-
-Build the client using the component outlines, interfaces, and theme guidance in `INSTRUCTIONS.md`.
-The shipped files are already deployed and configured; you do not need to read their source or
-rebuild them. If you encounter an error after building the client, read or change whatever you
-need to diagnose and fix it.
-
-## STEP 2 — Seed the storefront
-
-**Never delete or clean up anything on the user's site — seeding is additive only.** It's a live
-user-owned business, so never delete or overwrite existing content, even apparent sample data. If a
-cleanup truly seems needed, ask the user first.
-
-Seed by calling the storefront's ready-made seed module, `seed-store.cjs` — `require()` it and use its
-one-call `setupStore` (build-time exec_tool). Read
-`.agents/skills/wix-vibe-headless/references/storefront/seed/SEED.md` for the full `setupStore`
-contract — the `ctx` and the product/category shapes.
-
-```js
-const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/storefront/seed/seed-store.cjs"));
-const result = await seed.setupStore(ctx, { products, categories }); // one call: install → products → categories → images
-```
-
-For code or actions not covered by this skill, read and follow the installed connector skill at
-`.agents/skills/wix-base44-connector/SKILL.md` to find Wix documentation and APIs.
-
-**Auth for these admin calls is the already-configured Wix headless connector — nothing else.** Get its
-access token and send it as a bearer token:
-
-```js
-const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-// then: fetch(url, { headers: { Authorization: `Bearer ${accessToken}`, "Content-Type": "application/json" }, ... })
-```
-
-Inline via exec_tool, `base44` is already declared — use it directly; do **not** import
-`@base44/sdk`, re-declare it, or call `createClient()` (that's for standalone `.js` files only;
-inline it throws *"Identifier 'base44' has already been declared."*).
-
-**Product images.** Fire every `generate_image` **before you build the client**, and seed **after**
-it — generation finishes while you build, so by the time you write the seed call your images are
-ready: each finished result now reads `status: "completed"` with its final
-`https://media.base44.com/...` url. Read every `imageUrl` from the results **as they read at that
-moment** — not from what they said when you called the tool — and pass them in the single
-`setupStore` call. A result without a final url by then (still running, or failed) → seed that
-product **without** `imageUrl` and attach it afterwards with `attachProductImages`.
-
-## STEP 3 — Wrap up
-
-### Verify
-
-Verify **once, after the seed** — home, shop, and a product page against the populated catalog.
-
-Images that are still generating may show `/__generating__/…` placeholders;
-the platform replaces these automatically at turn end, with a stock fallback if generation
-fails. You can finish without waiting for those images or replacing their placeholder URLs.
-
-### Final text response
-
-**Never paste a Wix dashboard link or path.**
-
-**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders, inventory and payments?", prefer_dashboard=true)`. Use its handoff guidance, note that the seeded catalog is mock data they can edit, replace or delete, and state any requested workflows that remain unfinished and what is needed to complete them.
-
-**A payment ask is a store ask.** The store carries its own checkout, in every region, so
-nothing separate connects payments and no payment provider is installed alongside it — send
-the user to the same dashboard page the handoff call names. A note that Base44 Payments /
-Wix Payments is unavailable in their region is about a provider installed into the app, and
-says nothing about their store's checkout.
-
-## Additional Wix functionality
-
-During the initial build or later, use the installed connector skill at
-`.agents/skills/wix-base44-connector/SKILL.md` to find Wix documentation and APIs for writing code
-or performing actions not covered by this skill.

package/skills/wix-vibe-headless/platforms/base44-ecom-light.md

@@ -1,87 +0,0 @@
-# Wix Managed Headless — Base44 storefront client
-
-You are building a **Wix Managed** headless storefront inside Base44 — the business is described in your
-initial prompt, and the Wix connector is already configured.
-
-The shipped client is already configured. Use its documented hooks and components; no ID lookup
-or configuration changes are needed.
-
-> **The Wix skills installed below are the complete build path for this app.** **Do NOT use the Base44 commerce kit (or any Base44 solution kit).** **This flow builds the client only — there is no seeding step.**
-
-**Banner disabled for this entry flow:** do not add `<WixManageBanner/>`; skip the shared
-storefront instructions' optional banner integration.
-
-Follow STEPs 1–3 below exactly.
-
-## STEP 1 — Install the Wix skills and deploy the storefront vertical to the app
-
-Install three skills — they land under `.agents/skills/`:
-- **`wix-vibe-headless`** — storefront build instructions, hook/component contracts, and seeding modules.
-- **`wix-manage`** — REST recipes for managing and configuring the Wix site.
-- **`wix-base44-connector`** — Wix connector usage, API contracts, and documentation discovery.
-
-
-Run this through exec_tool, exactly as written — installs all three skills, deploys the `storefront` REST scaffolds + UI into `src/` (the nav adapter at `src/lib/nav.js` among them), and pins the AGENTS.md note. **Its `deploy` result reports this app's `template`** — `react-router` wires routes into `src/App.jsx`, `tanstack` mounts them as files under `src/routes/`; see [`../references/_shared/routing.md`](../references/_shared/routing.md).
-
-```js
-const { execSync } = require('child_process');
-const { existsSync, readdirSync } = require('fs');
-const results = {};
-for (const skill of ['wix-vibe-headless', 'wix-manage', 'wix-base44-connector']) {
-  if (existsSync(`/app/.agents/skills/${skill}/SKILL.md`)) { results[skill] = 'already_installed'; continue; }
-  try {
-    const out = execSync(`CI=1 npx -y skills add wix/skills/skills/${skill} --yes 2>&1`,
-      { cwd: '/app', timeout: 60000, shell: '/bin/bash' }).toString().replace(/\x1b\[[0-9;]*m/g, '');
-    results[skill] = /installed 1 skill|found 1 skill/i.test(out) ? 'success'
-      : out.includes('No valid skills') ? 'not_found' : 'unknown';
-  } catch (e) { results[skill] = 'error: ' + e.message; }
-}
-const deploy = execSync(`node /app/.agents/skills/wix-vibe-headless/install/deploy.cjs storefront`, { cwd: '/app' }).toString();
-const agentsMd = execSync(`node /app/.agents/skills/wix-vibe-headless/install/pin-agents-md.cjs`, { cwd: '/app' }).toString();
-return { results, installed: readdirSync('/app/.agents/skills'), deploy: JSON.parse(deploy), agentsMd: JSON.parse(agentsMd) };
-```
-
-## STEP 2 — Build the client
-
-Read `.agents/skills/wix-vibe-headless/references/storefront/INSTRUCTIONS.md` and follow it **EXACTLY** — the single source of truth for how the storefront client is built.
-
-The shipped storefront provides catalog, cart, and checkout. Identify the additional workflows
-in the user's request and implement them alongside the storefront. If a workflow needs an
-external service or missing information, continue the work you can complete and identify the
-remaining dependency.
-
-For code or actions not covered by this skill, read and follow the installed connector skill at
-`.agents/skills/wix-base44-connector/SKILL.md` to find Wix documentation and APIs.
-
-Build the client using the component outlines, interfaces, and theme guidance in `INSTRUCTIONS.md`.
-The shipped files are already deployed and configured; you do not need to read their source or
-rebuild them. If you encounter an error after building the client, read or change whatever you
-need to diagnose and fix it.
-
-## STEP 3 — Wrap up
-
-**No seeding in this flow** — the client is the only deliverable. Do not seed, populate, or write data to Wix.
-
-### Verify
-
-Images that are still generating may show `/__generating__/…` placeholders;
-the platform replaces these automatically at turn end, with a stock fallback if generation
-fails. You can finish without waiting for those images or replacing their placeholder URLs.
-
-### Final text response
-
-**Never paste a Wix dashboard link or path.**
-
-**Before writing your final text response, make one handoff call** — `search_base44_docs(query="how do I manage my store's products, orders, inventory and payments?", prefer_dashboard=true)`. Use its handoff guidance, state any requested workflows that remain unfinished and what is needed to complete them.
-
-**A payment ask is a store ask.** The store carries its own checkout, in every region, so
-nothing separate connects payments and no payment provider is installed alongside it — send
-the user to the same dashboard page the handoff call names. A note that Base44 Payments /
-Wix Payments is unavailable in their region is about a provider installed into the app, and
-says nothing about their store's checkout.
-
-## Additional Wix functionality
-
-During the initial build or later, use the installed connector skill at
-`.agents/skills/wix-base44-connector/SKILL.md` to find Wix documentation and APIs for writing code
-or performing actions not covered by this skill.

package/skills/wix-vibe-headless/platforms/base44.md

@@ -1,148 +0,0 @@
-# Wix Managed Headless — Base44 build instructions
-
-You are building a **Wix Managed** headless site inside Base44 — the business is described in your
-initial prompt, and the Wix connector is already configured; use it for all admin API calls.
-
-Your Wix client id is in your prompt — a public, buyer-facing credential (anonymous visitor tokens
-only), safe in the frontend; use it directly for the Wix client setup.
-
-> **The Wix skills installed below are the complete build and seed path for this app — the Wix connector supplies the token for admin API calls.** **Do NOT use the Base44 commerce kit (or any Base44 solution kit).**
-
-**Banner enabled for this entry flow:** mount `<WixManageBanner/>` once in the Layout, above
-the header in the fixed top region, per the vertical instructions. It is preview-only.
-
-Follow STEPs 1–5 below exactly (run STEP 4 in parallel with STEP 3 — **except `forms`**, see
-STEP 3, and **except a seed that attaches entity images**, which runs after the build; see STEP 4).
-
-## STEP 1 — Install the Wix skills locally
-
-Install three skills under `.agents/skills/`: **`wix-vibe-headless`** (the client build + seed guide — your main source of truth), **`wix-manage`** (REST recipes to manage/configure the site), and **`wix-base44-connector`** (site context + API-doc discovery).
-
-Run this through exec_tool, exactly as written — installs all three skills, deploys REST scaffolds + UI into `src/` (the nav adapter at `src/lib/nav.js` among them), writes `wix-config.js`, and pins the AGENTS.md note. **Its `deploy` result reports this app's `template`** (`react-router` or `tanstack`) — STEP 3 needs it.
-
-**Set `VERTICALS`** to what the prompt asks for — **list every vertical the app uses**, since several often join the main one (too vague to tell? do STEP 2 first, then set it). Adding one later: re-run with the extra name.
-
-| vertical | pick it when the app needs to |
-|---|---|
-| `storefront` | sell products |
-| `donations` | accept one-time or recurring contributions to Wix Donations campaigns — not a generic form or membership plan |
-| `bookings` | take appointments or service bookings |
-| `rentals` | rent out an item for a length the customer picks (by the hour or by the day) |
-| `blog` | publish articles |
-| `events` | publish events with RSVPs or ticket sales |
-| `portfolio` | showcase creative work |
-| `pricing-plans` | sell memberships or subscriptions, incl. paid enrollment/access to an online course or program — but an "online store selling courses" is still `storefront` |
-| `restaurants` | show a menu, take orders, book tables |
-| `members` | let visitors sign in — this is **auth** |
-| `forms` | any visitor-fillable form: contact, signup, waitlist, application, survey, quote request (an event RSVP is `events`; a per-service booking form is `bookings`) |
-| `cms` | structured content the app reads back — galleries, listings, "my submissions" (a visitor-fillable form is `forms`) |
-
-```js
-const { execSync } = require('child_process');
-const { existsSync, readdirSync } = require('fs');
-const VERTICALS = ['storefront'];         // ← set from the prompt; list every vertical the app uses (e.g. ['members','cms'])
-const WIX_CLIENT_ID = '<client id from the prompt>';   // copy both from the prompt — deploy writes them into src/rest/wix-config.js
-const WIX_METASITE_ID = '<site id from the prompt>';
-const results = {};
-for (const skill of ['wix-vibe-headless', 'wix-manage', 'wix-base44-connector']) {
-  if (existsSync(`/app/.agents/skills/${skill}/SKILL.md`)) { results[skill] = 'already_installed'; continue; }
-  try {
-    const out = execSync(`CI=1 npx -y skills add wix/skills/skills/${skill} --yes 2>&1`,
-      { cwd: '/app', timeout: 60000, shell: '/bin/bash' }).toString().replace(/\x1b\[[0-9;]*m/g, '');
-    results[skill] = /installed 1 skill|found 1 skill/i.test(out) ? 'success'
-      : out.includes('No valid skills') ? 'not_found' : 'unknown';
-  } catch (e) { results[skill] = 'error: ' + e.message; }
-}
-const deploy = execSync(`node /app/.agents/skills/wix-vibe-headless/install/deploy.cjs ${VERTICALS.join(' ')} --client-id ${WIX_CLIENT_ID} --metasite-id ${WIX_METASITE_ID}`, { cwd: '/app' }).toString();
-const agentsMd = execSync(`node /app/.agents/skills/wix-vibe-headless/install/pin-agents-md.cjs`, { cwd: '/app' }).toString();
-return { results, installed: readdirSync('/app/.agents/skills'), deploy: JSON.parse(deploy), agentsMd: JSON.parse(agentsMd) };
-```
-
-Read skills with **`read_file`** using workspace-relative paths (e.g. `.agents/skills/wix-vibe-headless/SKILL.md`) — absolute `/app/...` fails. Always read from `.agents/skills/` exactly on every turn; ignore stray copies like `agent/skills/`.
-
-## STEP 2 (optional) — Brief doesn't say what to build? Read the site
-
-Only when the business description is vague or missing (else skip to STEP 3). Don't guess the Wix
-Business Solution — **read the site in one call** via the connector (exec_tool):
-
-```js
-const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-const res = await fetch("https://www.wixapis.com/_api/dynamic-context/v1/dynamic-context/markdown", {
-  method: "POST",
-  headers: { Authorization: `Bearer ${accessToken}`, "Content-Type": "application/json" },
-  body: JSON.stringify({ siteId: "<metasite id from your prompt>" }),
-});
-return (await res.json()).markdown;
-```
-
-It returns a markdown report — installed apps (by name), status, URL, locale, CMS collections
-([docs](https://dev.wix.com/docs/api-reference/tools/dynamic-site-context/get-dynamic-context-markdown.md)).
-Build for the installed apps' solutions (several → prioritize by the user's words and which holds
-real, non-sample content); the same output drives STEP 4's seeding — never seed guessed ones. If it
-fails or shows nothing relevant, ask the user what they offer.
-
-## STEP 3 — Build the client
-
-Read `.agents/skills/wix-vibe-headless/SKILL.md` and follow it **EXACTLY** — the single source of
-truth for how the client is built.
-
-**REST scaffolds + `wix-config.js` are already in `src/rest/`** (STEP 1 wrote them). Some verticals also ship a ready UI client in `src/` — theme + wire it per `INSTRUCTIONS.md`, don't rebuild. **Don't `read_file` deployed files** — every field shape is in `INSTRUCTIONS.md`; read one only on a real error or gap.
-
-**⚠️ `forms` is the ONE vertical that does NOT run in parallel with STEP 4** — its UI is gated on a
-file the seed writes. Read its `INSTRUCTIONS.md` **Prerequisites** before building any form UI; seed
-it first (STEP 4) and build the rest of the app meanwhile.
-
-**Mount pages the way this app's template expects.** Base44 ships more than one and they route
-differently; building for the wrong one renders a blank preview with no error to explain it. STEP 1
-resolved which it is and reported it as `template`:
-
-- `tanstack` → **TanStack Start**: file-based routes under `src/routes/`, no `src/App.jsx`, no
-  `index.html`, build output in `.output/` rather than `dist/`. Pages mount as route files; chrome
-  and providers live in `__root.jsx`.
-- `react-router` → **React Router**: routes and providers are wired into `src/App.jsx`.
-
-Read the app's own `AGENTS.md` first either way — both templates ship one and it states their
-conventions. The mounting pattern for each, and what STEP 1 put in `src/lib/nav.js`:
-[`../references/_shared/routing.md`](../references/_shared/routing.md).
-
-**On the React Router template, `src/App.jsx` is edited surgically, never rewritten.** It carries
-required platform auth scaffolding (`AuthProvider`/`useAuth` from `@/lib/AuthContext`); a full
-rewrite drops them → the validator rejects the write. Wire routes/imports in with `find_replace`,
-leave the rest as-is. TanStack keeps the same scaffolding in `src/routes/__root.jsx` and
-`src/lib/AuthContext.jsx`, under the same rule: add around it, never replace it.
-
-## STEP 4 — Manage and seed the business
-
-Seed by calling your vertical's ready-made seed module — read
-`.agents/skills/wix-vibe-headless/references/<vertical>/seed/SEED.md` and follow it (the loader
-snippet, admin connector token, and every field shape are there). Gaps or an unexpected shape → the
-documentation skill available in your environment.
-
-**Entity images:** fire every image generation **before you build the client**, and run an
-image-carrying seed **after** the build — generation finishes while you build, and each finished
-result then reads `status: "completed"` with its final `https://media.base44.com/...` url. Read
-every image url from the results **as they read at that moment**, not from what they said when you
-called the tool. No final url by then (still running, or failed) → seed without that image and
-attach it afterwards per the vertical's `SEED.md`.
-Seeding is **admin-only** — not part of the client, which is built solely per the `wix-vibe-headless` skill.
-
-- **Additive only:** never delete or overwrite the user's content, even apparent sample data; ask first if a cleanup truly seems needed.
-- Inline in exec_tool, `base44` is already declared — use it directly; do **not** `import @base44/sdk`, re-declare it, or call `createClient()` (throws *"Identifier 'base44' has already been declared."*).
-
-## STEP 5 — Wrap up
-
-**Ask the user to open** `https://manage.wix.com/dashboard/{metaSiteId}` (your metasite id) to complete setup in Wix.
-
-**Don't chase images.** A `/__generating__/…` placeholder is swapped for the final url automatically at turn end — do **not** edit, re-seed, or debug image urls.
-
-## Later admin requests
-
-For any later admin/management request, work as in STEP 4: your vertical's seed module first, else
-consult official Wix API documentation using the documentation skill available in your environment.
-Keep admin calls on the connected Wix connector.
-
-**A change to what the business data COLLECTS is one of these, however UI it sounds** — a new form
-field, product option or service setting. Change it on Wix first per the vertical's `seed/SEED.md`,
-then edit the client against the verified result.
-
-version: v1341

package/skills/wix-vibe-headless/platforms/generic.md

@@ -1,132 +0,0 @@
-# Wix Managed Headless — build instructions (any stack)
-
-You are building a **Wix Managed** headless site — the business, your `WIX_CLIENT_ID`, and metasite
-id are in your prompt. This skill is **client-only REST** over the public `WIX_CLIENT_ID`
-(visitor-facing, safe in the browser) — no `@wix/sdk`, no backend, no build step.
-
-## 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/`):**
-
-| file | what's in it |
-|---|---|
-| `wix-client.js` | The transport: exchanges `WIX_CLIENT_ID` for an anonymous **visitor token**, persists + refreshes it (that token *is* the cart/session identity), and exposes `wixApiRequest(path, {method, body, query})` — plus the member-session swap (`setSessionTokens` / `clearSession` / `isMember`). Plain `fetch`; SSR-guards `window`/`localStorage`; maps 402 + error bodies. |
-| `wix-config.js` | Holds `WIX_CLIENT_ID` + `WIX_METASITE_ID` — the only values to fill in. |
-
-**Plus `shared/app/lib/nav.js`.** The reference UI imports `Link`, `useParams`, `useNavigate`,
-`useLocation` and `Navigate` from `@/lib/nav` rather than from a router, so one set of sources runs
-on any of them. Point that path at your own router's equivalents — the shipped file re-exports
-react-router's, and `_shared/nav/nav.tanstack.js` shows the kind of wrapping another router needs
-(params scoped to the current match, a `navigate` you call with a path).
-
-**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-*.cjs` — 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 verticals — data layer (`app/rest/`) + seed module (`seed/`):**
-
-| vertical | `app/rest/` data layer | seed module |
-|---|---|---|
-| storefront | `wix-store-catalog.js`, `wix-store-cart.js` — products & variants; server cart + checkout redirect | `seed-store.cjs` |
-| bookings | `wix-bookings-services.js`, `wix-bookings-checkout.js` — services/categories/slots; booking + checkout | `seed-bookings.cjs` |
-| blog | `wix-blog.js` — posts (list + by-slug), categories, tags | `seed-blog.cjs` |
-| events | `wix-events-browse.js`, `wix-events-registration.js` — events & categories; RSVP / ticketing + checkout | `seed-events.cjs` |
-| portfolio | `wix-portfolio.js` — collections, projects, galleries | `seed-portfolio.cjs` |
-| restaurants | `wix-restaurants-menu.js`, `-ordering.js`, `-reservations.js` — menu; online ordering; table reservations | `seed-restaurants.cjs` |
-| forms | `wix-forms.js`, `wix-forms-submissions.js` — any visitor-fillable form: read the schema; upload attachments, create a submission (schema accessors ship alongside in `lib/wix-form-schema-utils.js`) | *(none — REST shapes in `seed/SEED.md`)* |
-| cms | `wix-cms.js` — Wix Data collections: list / detail / filter | *(none — see `seed/SEED.md`)* |
-| pricing-plans | `wix-pricing-plans.js` — plans list + subscribe/checkout | `seed-pricing-plans.cjs` |
-| members | `wix-members-auth.js` — custom login/signup (email+password, social, SSO), session, account | *(none — members sign up at runtime; nothing to 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. **One exception — `forms` must be seeded before its UI is built; read that gate in
-`references/forms/INSTRUCTIONS.md` (Prerequisites) first.** Everything else still parallelizes.
-
-### 1 · Install the skills
-
-Two skills, into `.agents/skills/`: **`wix-vibe-headless`** (this build guide + the seed modules —
-self-contained) and **`wix-docs`** (search/read the Wix API reference).
-
-```bash
-CI=1 npx skills@latest add wix/skills/skills/wix-vibe-headless --yes
-CI=1 npx skills@latest add wix/skills/skills/wix-docs --yes
-```
-
-### 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`.
-
-```bash
-V=<vertical>   # the vertical you're building
-
-# utils — transport + data layer (plain fetch, already SSR-guarded; use ~as-is)
-find .agents/skills/wix-vibe-headless/references/shared/app/rest \
-     .agents/skills/wix-vibe-headless/references/$V/app/rest \
-     -type f -name '*.js' -exec tail -n +1 {} +
-
-# components/pages — a reference UI (rebuild for your framework; keep the field shapes + route patterns)
-find .agents/skills/wix-vibe-headless/references/$V/app \
-     -type f \( -name '*.jsx' -o -name '*.js' \) -not -path '*/rest/*' -exec tail -n +1 {} +
-```
-
-### 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](https://manage.wix.com/account/api-keys/addkey)**
-([how-to](https://dev.wix.com/docs/api-reference/articles/authentication/api-keys/generate-an-api-key)) —
-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):
-
-```bash
-curl -X POST 'https://www.wixapis.com/stores/v3/products/query' \
-  -H 'Authorization: <API_KEY>' -H 'wix-site-id: <METASITE_ID>' \
-  -H 'Content-Type: application/json' -d '{"query":{"cursorPaging":{"limit":10}}}'
-```
-
-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:
-
-```bash
-V=<vertical>
-find .agents/skills/wix-vibe-headless/references/$V/seed -name '*.js' -exec tail -n +1 {} +
-```
-
-They encode the Wix API sequences (incl. app-install + provisioning-race handling). For anything
-they don't cover, consult the official Wix API documentation using the documentation skill available
-in your environment. 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 preview-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 preview-gate, **never on the published
-site**), then tell
-the user to open `https://manage.wix.com/dashboard/{metaSiteId}` to finish setup in Wix (payments,
-content).

package/skills/wix-vibe-headless/references/_shared/nav/nav.tanstack.js

@@ -1,30 +0,0 @@
-// Navigation adapter — TanStack Start template (src/routes/ file-based routing).
-// Copy to src/lib/nav.js. Shipped components import Link/useParams/etc from here so the same
-// files run on either Base44 template; this file is the only place the router is named.
-//
-// Two shapes differ from react-router and are normalised here:
-//   useParams  — TanStack scopes params to a route; `strict: false` returns the current match's
-//                params, which is what a shared component wants.
-//   useNavigate — TanStack takes an object; this returns a function you call with a path, and
-//                 `navigate(-1)` still goes back.
-import {
-  Link as RouterLink,
-  Navigate,
-  useLocation,
-  useNavigate as useRouterNavigate,
-  useParams as useRouterParams,
-} from "@tanstack/react-router";
-
-// `to` is an already-resolved path (`/blog/my-post`); the router matches it at runtime.
-export const Link = RouterLink;
-export { Navigate, useLocation };
-
-export function useParams() {
-  return useRouterParams({ strict: false });
-}
-
-export function useNavigate() {
-  const navigate = useRouterNavigate();
-  return (to, options) =>
-    typeof to === "number" ? window.history.go(to) : navigate({ to, ...options });
-}

package/skills/wix-vibe-headless/references/_shared/routing.md

@@ -1,86 +0,0 @@
-# Mounting pages: which template is this app?
-
-Base44 ships more than one app template, and they route differently — so which one you are on
-decides how a page gets mounted. A page mounted the other template's way renders nothing, and the
-preview comes back blank with no error to explain it.
-
-**An install that ran `deploy.cjs` already told you** — its result carries the template it resolved
-from disk, as `{ "template": "react-router" }` or `{ "template": "tanstack" }`. Where the host
-deployed the tree itself there is no such line, and the same fact reads straight off the app —
-**ask `src/routes/__root.jsx` first**: present → TanStack Start (file-based routes, build output in
-`.output/` rather than `dist/`); absent → React Router SPA, routed from `src/App.jsx` with an
-`index.html` beside it. That order matters, because an `src/App.jsx` on a TanStack app is
-something an agent wrote believing the app was React Router — `__root.jsx` is never there by
-mistake. The app's own `AGENTS.md` (both templates ship one) states its conventions — worth a read
-before the first write.
-
-## On TanStack, four things differ from the React Router form
-
-Routing guidance you meet elsewhere — routes wired into `src/App.jsx`, `react-router-dom` imports,
-its `AuthProvider` / `QueryClientProvider` wrappers — describes the React Router template. On this
-one:
-
-- **There is no `src/App.jsx`, and that is the finished state.** Leave it absent; creating one
-  wires a router the app does not use, and the pages mounted in it never render.
-- **Route files import `createFileRoute` and `Link` from `@tanstack/react-router`**, which this
-  template installs.
-- **The wrappers live in `src/routes/__root.jsx`.** Same rule as `App.jsx` carries on the other
-  template: add around them, never replace them.
-- **Telling the two apart costs nothing** — the app's files are already in your context.
-
-## The nav adapter is already installed
-
-Shipped components import `Link`, `useParams` and friends from `@/lib/nav`, never from a router
-package, so one set of sources runs on either template. `src/lib/nav.js` arrives with the rest of
-the deployed tree, and it is the one place the router is named. Write your own pages against
-`@/lib/nav` too and they stay portable for free.
-
-**On TanStack, check what landed.** The deployed default is the React Router adapter, and
-`deploy.cjs` swaps the TanStack one in when it runs — but a host that copies the tree itself lands
-the default whatever the template. So on a TanStack app, open `src/lib/nav.js` and, if it
-re-exports from `react-router-dom`, copy `_shared/nav/nav.tanstack.js` over it. That file carries
-the two normalisations the imports depend on: `useParams` scoped with `strict: false`, and
-`useNavigate` returning a function you call with a path (`navigate(-1)` included).
-
-## React Router template
-
-One `Layout` holding your chrome renders `<Outlet/>`; every route nests under a single pathless
-route so the chrome wraps all pages. Each vertical's `STEP 3` carries the exact snippet, including
-where the preview banner sits.
-
-## TanStack Start template
-
-Same structure, expressed as files. The chrome that lives in `Layout` goes in `src/routes/__root.jsx`
-(it already renders the document and providers — add your header/footer around its `<Outlet/>`),
-and each route is its own file exporting `createFileRoute`:
-
-```jsx
-// src/routes/shop.jsx      →  /shop
-import { createFileRoute } from "@tanstack/react-router";
-import Shop from "@/pages/Shop";                      // the shipped page, unchanged
-
-export const Route = createFileRoute("/shop")({ component: Shop });
-```
-
-```jsx
-// src/routes/product.$slug.jsx   →  /product/:slug
-import { createFileRoute } from "@tanstack/react-router";
-import ProductDetail from "@/pages/ProductDetail";    // shipped; reads its param via @/lib/nav
-
-export const Route = createFileRoute("/product/$slug")({ component: ProductDetail });
-```
-
-Three things to carry over from the React Router wiring:
-
-- **Shipped pages stay where they are** (`src/pages/…`) and stay unedited. A route file is a
-  two-line mount, not a copy of the page.
-- **Path params use `$name`**, so `/product/:slug` becomes the file `product.$slug.jsx` and the
-  route path `/product/$slug`. `useParams()` from `@/lib/nav` returns them the same way.
-- **Providers** a vertical asks you to wrap the tree in (`CartProvider`, `MemberProvider`, …) go in
-  `__root.jsx` around `<Outlet/>`, once — not per route file.
-
-Per-user routes should also set `ssr: false` so personal data never lands in cacheable HTML:
-
-```jsx
-export const Route = createFileRoute("/my-plans")({ component: MyPlans, ssr: false });
-```