@wix/agent-skills 1.18.1 → 1.19.0

package/skills/wix-vibe-headless/references/bookings/seed/{seed-rentals.js → seed-rentals.cjs}

@@ -1,5 +1,5 @@
 // Rentals seed helpers — run at BUILD TIME via exec_tool (NOT shipped in the app).
-// A DELTA on seed-bookings.js: Wix Rentals has no APIs of its own, so a rental is a Bookings
+// A DELTA on seed-bookings.cjs: Wix Rentals has no APIs of its own, so a rental is a Bookings
 // service carrying rentals-specific field values. Everything about the transport, images and
 // error handling is the same; only the create order and the service payload differ.
 //
@@ -9,7 +9,7 @@
 // Usage (build-time exec_tool) — prefer `setupRentals`, which runs the whole flow in the one order
 // that works and threads the resource ids into each service for you:
 //   const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/bookings/seed/seed-rentals.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/bookings/seed/seed-rentals.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //   await seed.setupRentals(ctx, {
 //     resourceTypeName: "Meeting rooms",
@@ -27,7 +27,7 @@
 //   2. Resources created before the service, and their ids listed in `serviceResources[].resourceIds`.
 //   3. No category — a rental is surfaced by its `appId`, not by a Bookings category.
 //
-// Images are reused from seed-bookings.js — require both.
+// Images are reused from seed-bookings.cjs — require both.
 // Source recipe: wix-headless/references/inline-recipes/setup-rentals.md.
 
 const API = "https://www.wixapis.com";

package/skills/wix-vibe-headless/references/cms/INSTRUCTIONS.md

@@ -148,7 +148,7 @@ Validate the mime type and the size there as well.
 
 ## Fallback — beyond the helpers
 Need something the helpers don't cover? Call it yourself with `wixApiRequest`, but look up the exact
-endpoint/method/body in the official Wix reference first (or use the `wix-docs` skill) — never guess.
+endpoint/method/body in the official Wix reference first (or use the documentation skill available in your environment) — never guess.
 - Data Items API: https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items.md
 - Partial update (Patch): https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/patch-data-item.md
 - Upsert by id (Save): https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/save-data-item.md

package/skills/wix-vibe-headless/references/cms/seed/SEED.md

@@ -141,5 +141,5 @@ permission scope, and the response envelope.
 - Bulk Insert Data Item References: https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items/bulk-insert-data-item-references.md
 - Data Items API: https://dev.wix.com/docs/api-reference/business-solutions/cms/data-items.md
 - Collections: https://dev.wix.com/docs/api-reference/business-solutions/cms/collection-management/data-collections.md
-- Anything not covered → use the `wix-docs` skill (search + read the live reference); never guess.
-- Anything not covered → use the `wix-docs` skill (search + read the live reference); never guess.
+- Anything not covered → use the documentation skill available in your environment (search + read the live reference); never guess.
+- Anything not covered → use the documentation skill available in your environment (search + read the live reference); never guess.

package/skills/wix-vibe-headless/references/events/INSTRUCTIONS.md

@@ -47,16 +47,9 @@ end). (Files missing? the install's `deploy` result lists what it wrote; re-run
 `references/events/app/` → `src/`.)
 
 
-## STEP 2 — Theme (nothing to style on the shipped components)
-The shipped components carry **no palette of their own** — they render from base44's design tokens in
-`src/index.css` (`:root`/`.dark`: `--background`, `--foreground`, `--card`, `--primary`, `--muted`,
-`--border`, `--radius`, `--font-*`) via shadcn Tailwind classes (`bg-card`, `text-foreground`,
-`bg-primary`, `text-muted-foreground`, `border-border`, `rounded-lg`, `font-display`). Those tokens
-are **already set to the brand by the design phase**, so the shipped pages are themed with zero work
-here. To adjust the palette, edit `index.css` (`:root` **and** `.dark`) — the base44 way; **never add
-a parallel theme file (e.g. a `theme.css`) or restyle the shipped JSX.** Build the Home/Header you add
-(STEP 3) from the **same** base44 tokens/classes so it matches automatically. A dark brand is just
-base44's dark palette in `index.css` — no per-component work.
+## STEP 2 — Theme
+Use the existing Base44 theme in `src/index.css` so your pages and the shipped components
+share the same colors and typography.
 
 ## STEP 3 — Wire routes + provider (surgical `find_replace` on `src/App.jsx`, never a rewrite)
 **No file reads needed to wire this.** Every shipped page and `WixManageBanner` is a default export that takes **no props** — wire them exactly as the snippet shows; nothing in those files needs looking up.
@@ -206,10 +199,9 @@ official Wix Events API reference first, never guess:
 - Member login + "my registrations" → the **members** vertical (`references/members/INSTRUCTIONS.md`).
 
 Fallback only — when you hit an error or need something not shown here: read the relevant shipped file
-under `src/`, or look it up via the **`wix-docs`** skill.
+under `src/`, or look it up via the documentation skill available in your environment.
 
 ## Hard rules
-- Style via base44 design tokens (`index.css` / shadcn Tailwind classes), never by rewriting the shipped components or adding a parallel theme file.
 - Header/footer live in a `Layout` around `<Outlet/>` (STEP 3) — never edit the shipped `Events`/`EventDetail` to add chrome.
 - The Layout's fixed top region owns positioning: `<WixManageBanner/>` above `<Header/>`; your `Header` is plain in-flow markup (not `position:fixed`).
 - Paid ticket checkout goes through the shipped reserve → `getTicketCheckoutUrl` redirect (the Wix-hosted ticket form) — never a hand-built registration/ticket/payment URL.
@@ -225,7 +217,6 @@ parallel.
 
 ## Verify (before declaring done)
 - [ ] Client files copied into `src/`; `WIX_CLIENT_ID` set (not the placeholder).
-- [ ] Brand palette lives in `index.css` (`:root`/`.dark`); no parallel theme file; shipped components/pages not restyled or rewritten.
 - [ ] Opened the vertical's data route(s) (not just the home page) and confirmed the shipped components render themed (surface, text, brand) with images.
 - [ ] `Layout` (fixed `<WixManageBanner/>` + `<Header/>` region, then `<Outlet/>` + Footer) wraps all routes; shipped `Events`/`EventDetail` untouched; content clears the fixed chrome.
 - [ ] Event grid renders live events; clicking a card opens the detail page by `slug`; visitor token persists across reload.

package/skills/wix-vibe-headless/references/events/seed/SEED.md

@@ -1,6 +1,6 @@
 # Events — seeding
 
-Seed Wix Events (Events V3) by **calling `seed-events.js`** — don't hand-write the REST calls. It's
+Seed Wix Events (Events V3) by **calling `seed-events.cjs`** — don't hand-write the REST calls. It's
 a build-time module (run via `exec_tool`, not shipped in the app) that abstracts every Wix Events
 seed operation. `require` it and call the functions with plain data.
 
@@ -14,11 +14,7 @@ after create, and **publishing is one-way**. So per event: create DRAFT → (tic
 ```js
 // build-time exec_tool
 const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-const fs = require("fs");
-// exec_tool's require can return EMPTY exports for these build-time modules — load the file itself:
-const seed = (() => { const m = { exports: {} };
-  new Function("module", "exports", "require", fs.readFileSync("/app/.agents/skills/wix-vibe-headless/references/events/seed/seed-events.js", "utf8"))(m, m.exports, require);
-  return m.exports; })();
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/events/seed/seed-events.cjs"));
 const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 
 // DEFAULT — one call runs the whole flow per event (create DRAFT → tiers → publish), then resolves
@@ -94,7 +90,7 @@ Free/RSVP events need neither.
 
 ## Reference
 If a call returns a shape you didn't expect, or you need an operation this module doesn't cover,
-use the **`wix-docs`** skill to search + read the live Wix API reference — never guess. The
+use the documentation skill available in your environment to search + read the live Wix API reference — never guess. The
 authoritative source recipe is `wix-headless/references/inline-recipes/setup-events.md`.
 
 Read a method's page before writing its call: it carries the exact body shape, the required

package/skills/wix-vibe-headless/references/events/seed/{seed-events.js → seed-events.cjs}

@@ -8,7 +8,7 @@
 //
 // Usage (build-time exec_tool):
 //   const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");  // Base44 (generic: use $TOKEN)
-//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/events/seed/seed-events.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/events/seed/seed-events.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //
 //   // setupEvents installs the Wix Events app first (installEventsApp) — base44 sites may not have it.
@@ -31,7 +31,7 @@
 //   const file = await seed.importImage(ctx, imageUrl);   // → { id, url } (Wix Media file id + wixstatic url)
 //   await seed.setEventMainImage(ctx, { eventId: ev.id, id: file.id, url: file.url, height: 1024, width: 1024, altText: ev.slug });
 //
-// If any call fails with a shape the caller didn't expect, fall back to the wix-docs skill
+// If any call fails with a shape the caller didn't expect, fall back to the documentation skill available in your environment
 // (search + read the live Wix API reference) — never guess. Source recipe (authoritative):
 // wix-headless/references/inline-recipes/setup-events.md.
 

package/skills/wix-vibe-headless/references/forms/INSTRUCTIONS.md

@@ -422,7 +422,8 @@ Don't reach for `role="form"`, an `aria-label` on an input that already has a `<
 Three sources answer what this file doesn't: the **JSDoc** in `hooks/useWixForm.js` and
 `lib/wix-form-schema-utils.js`; the **Wix reference** below; and `seed/SEED.md` for how a field was
 authored, and REVISE for changing one. Calling an endpoint the helpers don't wrap is fine via
-`wixApiRequest` — look up the exact method and body first (or the `wix-docs` skill), never guess.
+`wixApiRequest` — first look up the exact method and body in official Wix API documentation using
+the documentation skill available in your environment; never guess.
 
 - Form object (the shape `form` and its fields arrive in): https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/form-object.md
 - Form Schemas API: https://dev.wix.com/docs/api-reference/crm/forms/form-schemas.md

package/skills/wix-vibe-headless/references/forms/seed/SEED.md

@@ -25,7 +25,7 @@ The six steps, each with a section below:
 
 Wix Forms is a **CRM** API, not Business Solutions. Read the page before writing a call you don't
 find here — never guess a shape. For anything these pages don't settle — a response shape you didn't
-expect, or an operation this doc doesn't cover — use the **`wix-docs`** skill to search + read the
+expect, or an operation this doc doesn't cover — use the documentation skill available in your environment to search + read the
 live Wix API reference.
 
 | step | title | page | what it settles |

package/skills/wix-vibe-headless/references/members/INSTRUCTIONS.md

@@ -72,16 +72,9 @@ fallback — a runtime error, or a field the snippets don't cover (see "Fallback
 > the top of the file — read that, not the whole body, if you need the contract.
 
 
-## STEP 2 — Theme (nothing to style on the shipped components)
-The shipped components carry **no palette of their own** — they render from base44's design tokens
-in `src/index.css` (`:root`/`.dark`: `--background`, `--foreground`, `--card`, `--primary`, `--muted`,
-`--border`, `--radius`, `--font-*`) via shadcn Tailwind classes (`bg-card`, `text-foreground`,
-`bg-primary`, `text-muted-foreground`, `border-border`, `rounded-lg`, `font-display`). Those tokens
-are **already set to the brand by the design phase**, so the shipped auth surfaces are themed with
-zero work here. To adjust the palette, edit `index.css` (`:root` **and** `.dark`) — the base44 way;
-**never add a parallel theme file (e.g. a `theme.css`) or restyle the shipped JSX.** Build the
-Home/Header you add (STEP 3) from the **same** base44 tokens/classes so it matches automatically. A
-dark brand is just base44's dark palette in `index.css` — no per-component work.
+## STEP 2 — Theme
+Use the existing Base44 theme in `src/index.css` so your pages and the shipped components
+share the same colors and typography.
 
 ## STEP 3 — Wire routes + provider (surgical `find_replace` on `src/App.jsx`, never a rewrite)
 **No file reads needed to wire this.** Every shipped page and `WixManageBanner` is a default export that takes **no props** — wire them exactly as the snippet shows; nothing in those files needs looking up.
@@ -254,10 +247,9 @@ Members Area app:
 
 Fallback only — when you hit an error or need something not shown here (password reset, custom SSO
 connection ids, a profile field these snippets don't have): read the relevant shipped file under
-`src/rest/`, or look it up via the **`wix-docs`** skill.
+`src/rest/`, or look it up via the documentation skill available in your environment.
 
 ## Hard rules
-- Style via base44 design tokens (`index.css` / shadcn Tailwind classes), never by rewriting the shipped components or adding a parallel theme file.
 - **Custom login only** — the member logs in on **your** UI; never redirect them to a Wix-hosted login page.
 - **One shared client** — login swaps the token set on `wix-client.js`; reuse it for everything so the
   member identity carries across the app. Never mint a second client or re-mint anonymously after login.
@@ -283,7 +275,6 @@ site's `metaSiteId` from the handoff / `ListWixSites`):
 
 ## Verify (before declaring done)
 - [ ] Client files copied into `src/`; `WIX_CLIENT_ID` set (not the placeholder).
-- [ ] Brand palette lives in `index.css` (`:root`/`.dark`); no parallel theme file; shipped components/pages not restyled or rewritten.
 - [ ] Opened the vertical's data route(s) (not just the home page) — `/login` and `/account` — and confirmed the shipped components render themed (surface, text, brand) with images.
 - [ ] `Layout` (fixed `<WixManageBanner/>` + `<Header/>` region, then `<Outlet/>` + Footer) wraps all routes; shipped `Login`/`Account`/`Callback` untouched; content clears the fixed chrome; `<MemberProvider>` wraps the tree; `<MemberMenu/>` in the header.
 - [ ] Sign-up: `register()` reaches `SUCCESS` (or `REQUIRE_EMAIL_VERIFICATION` handled via the code entry).

package/skills/wix-vibe-headless/references/members/seed/SEED.md

@@ -2,15 +2,14 @@
 
 **Nothing to seed.** Members login is the identity layer: members **self-register** through the
 Wix login page, so there is no member to create at build time and nothing lands in a `seeded`
-map. There is intentionally no `seed-*.js` here.
+map. There is intentionally no `seed-*.cjs` here.
 
 The members work is entirely **frontend wiring** (custom login, account area, gated content) —
 see this vertical's `INSTRUCTIONS.md` and the reference components.
 
 _Optional, off by default:_ only if a run's prompt explicitly asks to exercise the pricing-plans
 purchase path end-to-end, one test member may be created — keep this off so headless runs stay
-deterministic and don't stall on an interactive login. If you need that, use the **`wix-docs`**
-skill for the current member-create shape (source: `wix-headless/references/SEED.md` § members).
+deterministic and don't stall on an interactive login. If you need that, use the documentation skill available in your environment for the current member-create shape (source: `wix-headless/references/SEED.md` § members).
 
 ## Reference
 Members self-register, so this vertical seeds nothing. These are the methods to read if you do reach

package/skills/wix-vibe-headless/references/portfolio/INSTRUCTIONS.md

@@ -48,16 +48,9 @@ end). (Files missing? the install's `deploy` result lists what it wrote; re-run
 `references/portfolio/app/` → `src/`.)
 
 
-## STEP 2 — Theme (nothing to style on the shipped components)
-The shipped components carry **no palette of their own** — they render from base44's design tokens in
-`src/index.css` (`:root`/`.dark`: `--background`, `--foreground`, `--card`, `--primary`, `--muted`,
-`--border`, `--radius`, `--font-*`) via shadcn Tailwind classes (`bg-card`, `text-foreground`,
-`bg-primary`, `text-muted-foreground`, `border-border`, `rounded-lg`, `font-display`). Those tokens
-are **already set to the brand by the design phase**, so the shipped pages are themed with zero work
-here. To adjust the palette, edit `index.css` (`:root` **and** `.dark`) — the base44 way; **never add
-a parallel theme file (e.g. a `theme.css`) or restyle the shipped JSX.** Build the Home/Header you add
-(STEP 3) from the **same** base44 tokens/classes so it matches automatically. A dark brand is just
-base44's dark palette in `index.css` — no per-component work.
+## STEP 2 — Theme
+Use the existing Base44 theme in `src/index.css` so your pages and the shipped components
+share the same colors and typography.
 
 ## STEP 3 — Wire routes (surgical `find_replace` on `src/App.jsx`, never a rewrite)
 **No file reads needed to wire this.** Every shipped page and `WixManageBanner` is a default export that takes **no props** — wire them exactly as the snippet shows; nothing in those files needs looking up.
@@ -196,12 +189,11 @@ Cover images live at `collection.coverImage.imageInfo.url` and `project.coverIma
 
 Fallback only — when you hit an error or need something not shown here (collection SEO, portfolio
 settings, a field these snippets don't have): read the relevant shipped file under `src/`, or look
-it up via the **`wix-docs`** skill / the Portfolio API reference. Each helper in `wix-portfolio.js`
+it up via the documentation skill available in your environment / the Portfolio API reference. Each helper in `wix-portfolio.js`
 links its own reference page inline; the whole area is here:
 - Portfolio (collections, projects, project items): https://dev.wix.com/docs/api-reference/business-solutions/portfolio.md
 
 ## Hard rules
-- Style via base44 design tokens (`index.css` / shadcn Tailwind classes), never by rewriting the shipped components or adding a parallel theme file.
 - Header/footer live in a `Layout` around `<Outlet/>` (STEP 3) — never edit the shipped
   `Portfolio`/`CollectionPage`/`ProjectDetail` to add chrome.
 - The Layout's fixed top region owns positioning: `<WixManageBanner/>` above `<Header/>`; your
@@ -222,7 +214,6 @@ Seed collections and projects per `seed/SEED.md` — separate from this client b
 
 ## Verify (before declaring done)
 - [ ] Client files copied into `src/`; `WIX_CLIENT_ID` set (not the placeholder).
-- [ ] Brand palette lives in `index.css` (`:root`/`.dark`); no parallel theme file; shipped components/pages not restyled or rewritten.
 - [ ] Opened the vertical's data route(s) (`/portfolio`, a collection, a project) — not just the home page — and confirmed the shipped components render themed (surface, text, brand) with images.
 - [ ] `Layout` (fixed `<WixManageBanner/>` + `<Header/>` region, then `<Outlet/>` + Footer) wraps all
       routes; shipped `Portfolio`/`CollectionPage`/`ProjectDetail` untouched; content clears the fixed chrome.

package/skills/wix-vibe-headless/references/portfolio/app/components/ProjectMedia.jsx

@@ -16,7 +16,7 @@ export default function ProjectMedia({ item }) {
   }
   if (item.type === "VIDEO") {
     // resolutions[].url is the confirmed field; posters[0] is the poster (sub-shape not in the
-    // helper JSDoc — posters[0].url used here; confirm in wix-docs if a brand needs more).
+    // helper JSDoc — posters[0].url used here; confirm in documentation skill available in your environment if a brand needs more).
     const vi = item.video?.videoInfo;
     const src = https(vi?.resolutions?.[0]?.url);
     const poster = https(vi?.posters?.[0]?.url);

package/skills/wix-vibe-headless/references/portfolio/seed/SEED.md

@@ -1,6 +1,6 @@
 # Portfolio — seeding
 
-Seed a Wix Portfolio by **calling `seed-portfolio.js`** — don't hand-write the REST calls. It's
+Seed a Wix Portfolio by **calling `seed-portfolio.cjs`** — don't hand-write the REST calls. It's
 a build-time module (run via `exec_tool`, not shipped in the app) that abstracts every Wix
 Portfolio seed operation. `require` it and call the functions with plain data.
 
@@ -17,11 +17,7 @@ first, then thread their real ids into each project.
 ```js
 // build-time exec_tool
 const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-const fs = require("fs");
-// exec_tool's require can return EMPTY exports for these build-time modules — load the file itself:
-const seed = (() => { const m = { exports: {} };
-  new Function("module", "exports", "require", fs.readFileSync("/app/.agents/skills/wix-vibe-headless/references/portfolio/seed/seed-portfolio.js", "utf8"))(m, m.exports, require);
-  return m.exports; })();
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/portfolio/seed/seed-portfolio.cjs"));
 const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 
 const summary = await seed.setupPortfolio(ctx, {
@@ -79,7 +75,7 @@ hide. `setupPortfolio` **installs the Wix Portfolio app first** (`installPortfol
 
 ## Reference
 If a call returns a shape you didn't expect, or you need an operation this module doesn't cover,
-use the **`wix-docs`** skill to search + read the live Wix API reference — never guess. The
+use the documentation skill available in your environment to search + read the live Wix API reference — never guess. The
 authoritative source recipe is `wix-headless/references/inline-recipes/setup-portfolio.md`.
 
 **Transcribed from the recipe — NOT yet live-verified.** The endpoints/fields mirror

package/skills/wix-vibe-headless/references/portfolio/seed/{seed-portfolio.js → seed-portfolio.cjs}

@@ -6,7 +6,7 @@
 //
 // Usage (build-time exec_tool):
 //   const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");  // Base44
-//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/portfolio/seed/seed-portfolio.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/portfolio/seed/seed-portfolio.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //
 //   const collections = await seed.createCollections(ctx, [{ title, description }]);        // STEP 1
@@ -19,7 +19,7 @@
 //   await seed.createProjectItems(ctx, [{ projectId: projects[0].id, sortOrder: 1, title, imageId: files[0].id, height:1024, width:1024 }]);
 //
 // **NOT yet live-verified — transcribed from setup-portfolio.md.** If any call fails with a
-// shape the caller didn't expect, fall back to the wix-docs skill (search + read the live Wix
+// shape the caller didn't expect, fall back to the documentation skill available in your environment (search + read the live Wix
 // API reference) — never guess. Source recipe (authoritative):
 // wix-headless/references/inline-recipes/setup-portfolio.md.
 

package/skills/wix-vibe-headless/references/pricing-plans/INSTRUCTIONS.md

@@ -51,16 +51,9 @@ end). (Files missing? the install's `deploy` result lists what it wrote; re-run
 `references/pricing-plans/app/` → `src/`.)
 
 
-## STEP 2 — Theme (nothing to style on the shipped components)
-The shipped components carry **no palette of their own** — they render from base44's design tokens
-in `src/index.css` (`:root`/`.dark`: `--background`, `--foreground`, `--card`, `--primary`,
-`--muted`, `--border`, `--radius`, `--font-*`) via shadcn Tailwind classes (`bg-card`,
-`text-foreground`, `bg-primary`, `text-muted-foreground`, `border-border`, `rounded-lg`,
-`font-display`). Those tokens are **already set to the brand by the design phase**, so the shipped
-pages are themed with zero work here. To adjust the palette, edit `index.css` (`:root` **and**
-`.dark`) — the base44 way; **never add a parallel theme file (e.g. a `theme.css`) or restyle the
-shipped JSX.** Build the Home/Header you add (STEP 3) from the **same** base44 tokens/classes so it
-matches automatically. A dark brand is just base44's dark palette in `index.css` — no per-component work.
+## STEP 2 — Theme
+Use the existing Base44 theme in `src/index.css` so your pages and the shipped components
+share the same colors and typography.
 
 ## STEP 3 — Wire routes + provider (surgical `find_replace` on `src/App.jsx`, never a rewrite)
 **No file reads needed to wire this.** Every shipped page and `WixManageBanner` is a default export that takes **no props** — wire them exactly as the snippet shows; nothing in those files needs looking up.
@@ -192,7 +185,7 @@ window.location.href = await checkout(plan.id, { thankYouPageUrl: `${window.loca
 const orders = await getMyPlanOrders({ orderStatuses: ["ACTIVE"] });   // omit orderStatuses for all
 
 // Plan image: plan.image is a WixMedia object { id, width, height, altText } with NO .url. The shipped
-// cards render text only to avoid this. To show it, resolve the WixMedia `id` to a URL (wix-docs),
+// cards render text only to avoid this. To show it, resolve the WixMedia `id` to a URL (documentation skill available in your environment),
 // or omit — never <img src={plan.image}> / <img src={plan.image.url}> (undefined / [object Object]).
 ```
 
@@ -208,10 +201,9 @@ method, and body first (never guess):
 - Headless redirect session: https://dev.wix.com/docs/api-reference/business-management/headless/redirects/create-redirect-session.md
 
 Fallback only — when you hit an error or need something not shown here: read the relevant shipped
-file under `src/`, or look it up via the **`wix-docs`** skill.
+file under `src/`, or look it up via the documentation skill available in your environment.
 
 ## Hard rules
-- Style via base44 design tokens (`index.css` / shadcn Tailwind classes), never by rewriting the shipped components or adding a parallel theme file.
 - Header/footer live in a `Layout` around `<Outlet/>` (STEP 3) — never edit the shipped
   `Plans`/`PlanDetail`/`MyPlans` to add chrome.
 - The Layout's fixed top region owns positioning: `<WixManageBanner/>` above `<Header/>`; your
@@ -233,7 +225,6 @@ in parallel.
 
 ## Verify (before declaring done)
 - [ ] Client files copied into `src/`; `WIX_CLIENT_ID` set (not the placeholder).
-- [ ] Brand palette lives in `index.css` (`:root`/`.dark`); no parallel theme file; shipped components/pages not restyled or rewritten.
 - [ ] Opened the vertical's data route(s) (not just the home page) and confirmed the shipped
       components render themed (surface, text, brand) with images.
 - [ ] `Layout` (fixed `<WixManageBanner/>` + `<Header/>` region, then `<Outlet/>` + Footer) wraps

package/skills/wix-vibe-headless/references/pricing-plans/app/components/OrderCard.jsx

@@ -1,6 +1,6 @@
 // Member plan-order row — pure UI for the "My plans" screen. Renders only fields the Order object
 // actually returns (planName, status, start/end dates); for anything else (amount paid, next-billing)
-// look it up in the Orders API reference (wix-docs) — never invent it. Styled with base44 design
+// look it up in the Orders API reference (documentation skill available in your environment) — never invent it. Styled with base44 design
 // tokens (shadcn Tailwind classes).
 
 // Each status carries its OWN text colour: a shared `text-primary-foreground` over a varying

package/skills/wix-vibe-headless/references/pricing-plans/seed/SEED.md

@@ -1,6 +1,6 @@
 # Pricing Plans — seeding
 
-Seed Wix Pricing Plans (Plans V3) by **calling `seed-pricing-plans.js`** — don't hand-write the
+Seed Wix Pricing Plans (Plans V3) by **calling `seed-pricing-plans.cjs`** — don't hand-write the
 REST calls. It's a build-time module (run via `exec_tool`, not shipped in the app) that abstracts
 every Pricing Plans + Benefit Programs seed operation. `require` it and call the functions with
 plain data.
@@ -10,11 +10,7 @@ plain data.
 ```js
 // build-time exec_tool
 const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-const fs = require("fs");
-// exec_tool's require can return EMPTY exports for these build-time modules — load the file itself:
-const seed = (() => { const m = { exports: {} };
-  new Function("module", "exports", "require", fs.readFileSync("/app/.agents/skills/wix-vibe-headless/references/pricing-plans/seed/seed-pricing-plans.js", "utf8"))(m, m.exports, require);
-  return m.exports; })();
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/pricing-plans/seed/seed-pricing-plans.cjs"));
 const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 
 // setupPricingPlans installs the Wix Pricing Plans app first (idempotent) — base44 sites may not have it.
@@ -74,7 +70,7 @@ is NOT a plan field or a perk). Those ids come from the **bookings seed**
 
 ## Reference
 If a call returns a shape you didn't expect, or you need an operation this module doesn't cover,
-use the **`wix-docs`** skill to search + read the live Wix API reference — never guess. The
+use the documentation skill available in your environment to search + read the live Wix API reference — never guess. The
 authoritative source recipe is `wix-headless/references/inline-recipes/setup-pricing-plans.md`.
 
 Read a method's page before writing its call: it carries the exact body shape, the required

package/skills/wix-vibe-headless/references/pricing-plans/seed/{seed-pricing-plans.js → seed-pricing-plans.cjs}

@@ -7,7 +7,7 @@
 //
 // Usage (build-time exec_tool):
 //   const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");  // Base44
-//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/pricing-plans/seed/seed-pricing-plans.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/pricing-plans/seed/seed-pricing-plans.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //
 //   // Bookings is seeded FIRST — its service ids feed a plan's coverage (see SEED.md).
@@ -20,7 +20,7 @@
 //   // Then, per plan that covers bookings services (STEP 2; skip entirely with no bookings):
 //   await seed.attachBookingsCoverage(ctx, plans[0].id, plans[0].coveredServiceIds);
 //
-// If any call fails with a shape the caller didn't expect, fall back to the wix-docs skill
+// If any call fails with a shape the caller didn't expect, fall back to the documentation skill available in your environment
 // (search + read the live Wix API reference) — never guess. Source recipe (authoritative):
 // wix-headless/references/inline-recipes/setup-pricing-plans.md.
 

package/skills/wix-vibe-headless/references/restaurants/INSTRUCTIONS.md

@@ -51,17 +51,9 @@ end). (Files missing? the install's `deploy` result lists what it wrote; re-run
 `references/restaurants/app/` → `src/`.)
 
 
-## STEP 2 — Theme (nothing to style on the shipped components)
-The shipped components (menu, item dialog, order cart, reservations) carry **no palette of their
-own** — they render from base44's design tokens in `src/index.css` (`:root`/`.dark`: `--background`,
-`--foreground`, `--card`, `--primary`, `--muted`, `--border`, `--radius`, `--font-*`) via shadcn
-Tailwind classes (`bg-card`, `text-foreground`, `bg-primary`, `text-muted-foreground`,
-`border-border`, `rounded-lg`, `font-display`). Those tokens are **already set to the brand by the
-design phase**, so the shipped pages are themed with zero work here. To adjust the palette, edit
-`index.css` (`:root` **and** `.dark`) — the base44 way; **never add a parallel theme file (e.g. a
-`theme.css`) or restyle the shipped JSX.** Build the Home/Header you add (STEP 3) from the **same**
-base44 tokens/classes so it matches automatically. A dark brand is just base44's dark palette in
-`index.css` — no per-component work.
+## STEP 2 — Theme
+Use the existing Base44 theme in `src/index.css` so your pages and the shipped components
+share the same colors and typography.
 
 ## STEP 3 — Wire routes + provider (surgical `find_replace` on `src/App.jsx`, never a rewrite)
 **No file reads needed to wire this.** Every shipped page and `WixManageBanner` is a default export that takes **no props** — wire them exactly as the snippet shows; nothing in those files needs looking up.
@@ -217,7 +209,7 @@ Building something beyond the shipped pages, or need a path these snippets don't
 Modifier up-charges / price-variant selection / special requests on the **cart line** are **not**
 wired into `addItemToCart` — the restaurants `catalogReference.options` shape for these isn't
 documented for client add-to-cart, so `ItemDialog` displays modifier groups for the diner but sends
-only quantity. To wire them, confirm the shape via the **`wix-docs`** skill / the reference first,
+only quantity. To wire them, confirm the shape via the documentation skill available in your environment / the reference first,
 never guess:
 - Restaurants API reference: https://dev.wix.com/docs/api-reference/business-solutions/restaurants.md
 - Sample flows (cart options): https://dev.wix.com/docs/api-reference/business-solutions/restaurants/online-orders/sample-flows.md
@@ -226,10 +218,9 @@ never guess:
   in lets them see their own order/reservation history.
 
 Fallback only — when you hit an error or need something not shown here: read the relevant shipped
-file under `src/`, or look it up via the **`wix-docs`** skill.
+file under `src/`, or look it up via the documentation skill available in your environment.
 
 ## Hard rules
-- Style via base44 design tokens (`index.css` / shadcn Tailwind classes), never by rewriting the shipped components or adding a parallel theme file.
 - Header/footer live in a `Layout` around `<Outlet/>` (STEP 3) — never edit the shipped `Menu`/`Reservations` to add chrome.
 - The Layout's fixed top region owns positioning: `<WixManageBanner/>` above `<Header/>`; your `Header` is plain in-flow markup (not `position:fixed`).
 - Order through the shipped cart: `addItem()` → `checkout()` (redirect-session) — never a hand-built `/checkout`, ordering, or reservation URL.
@@ -252,7 +243,6 @@ run in parallel.
 
 ## Verify (before declaring done)
 - [ ] Client files copied into `src/`; `WIX_CLIENT_ID` set (not the placeholder).
-- [ ] Brand palette lives in `index.css` (`:root`/`.dark`); no parallel theme file; shipped components/pages not restyled or rewritten.
 - [ ] Opened `/menu` and `/reservations` (not just the home page) and confirmed the shipped components render themed (surface, text, brand) with images.
 - [ ] `Layout` (fixed `<WixManageBanner/>` + `<Header/>` region, then `<Outlet/>` + Footer) wraps all routes; shipped `Menu`/`Reservations` untouched; content clears the fixed chrome; `<OrderCartProvider>` wraps the tree; `<OrderCartDrawer/>` mounted; `<OrderCartButton/>` in the header.
 - [ ] `getFullMenu()` renders real sections/items with prices, variants, modifiers, and labels; empty catalog shows the shipped empty state (no mock items).

package/skills/wix-vibe-headless/references/restaurants/seed/SEED.md

@@ -1,6 +1,6 @@
 # Restaurants — seeding
 
-Seed a Wix Restaurants site by **calling `seed-restaurants.js`** — don't hand-write the REST calls.
+Seed a Wix Restaurants site by **calling `seed-restaurants.cjs`** — don't hand-write the REST calls.
 It's a build-time module (run via `exec_tool`, not shipped in the app) that abstracts every seed
 operation across the vertical's four recipes: the **menu** (always) plus three on-demand add-ons —
 **online ordering**, **table reservations**, and **experiences**. `require` it and call the functions
@@ -18,11 +18,7 @@ across exec calls. Online ordering and table reservations run only when the plan
 ```js
 // build-time exec_tool
 const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");
-const fs = require("fs");
-// exec_tool's require can return EMPTY exports for these build-time modules — load the file itself:
-const seed = (() => { const m = { exports: {} };
-  new Function("module", "exports", "require", fs.readFileSync("/app/.agents/skills/wix-vibe-headless/references/restaurants/seed/seed-restaurants.js", "utf8"))(m, m.exports, require);
-  return m.exports; })();
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/restaurants/seed/seed-restaurants.cjs"));
 const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 
 const result = await seed.setupRestaurants(ctx, {
@@ -155,7 +151,7 @@ await seed.createExperiences(ctx, loc.id, [{ configuration: { /* per Create-Expe
 
 ## Reference
 If a call returns a shape you didn't expect, or you need an operation this module doesn't cover, use the
-**`wix-docs`** skill to search + read the live Wix API reference — never guess. The **Experiences** create
+documentation skill available in your environment to search + read the live Wix API reference — never guess. The **Experiences** create
 payload especially lives in the docs (fields evolve). The authoritative source recipes are
 `wix-headless/references/inline-recipes/setup-restaurants.md`, `setup-restaurant-orders.md`,
 `setup-restaurant-reservations.md`, and `setup-restaurant-experiences.md`.

package/skills/wix-vibe-headless/references/restaurants/seed/{seed-restaurants.js → seed-restaurants.cjs}

@@ -6,7 +6,7 @@
 //
 // Usage (build-time exec_tool):
 //   const { accessToken } = await base44.asServiceRole.connectors.getConnection("wix");  // Base44 (generic: use $TOKEN)
-//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/restaurants/seed/seed-restaurants.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/restaurants/seed/seed-restaurants.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //
 //   // --- MENU (always; the seedable core) ---
@@ -38,7 +38,7 @@
 //
 // **NOT yet live-verified — transcribed from setup-restaurants.md / setup-restaurant-orders.md /
 // setup-restaurant-reservations.md / setup-restaurant-experiences.md.** If any call fails with a
-// shape the caller didn't expect, fall back to the wix-docs skill (search + read the live Wix API
+// shape the caller didn't expect, fall back to the documentation skill available in your environment (search + read the live Wix API
 // reference) — never guess.
 //
 // ── PRECONDITIONS the recipes flag (record in the handoff, do NOT fail the seed) ─────────────────