@wix/agent-skills 1.18.0 → 1.18.2

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

@@ -1,11 +1,23 @@
 # Forms — seeding (Form Schemas v4 REST)
 
-Creating a form is an **admin/build-time** job, in six sequential steps. Each has a section below.
+**Two actions live in this doc — decide which one you're doing before reading on.** Both are
+**admin/build-time** work over an elevated credential, and both run through the same six steps:
+
+| action | when | the steps it uses |
+|---|---|---|
+| **CREATE a form** — `POST` | there's no form yet: the app needs a contact / quote / application form and nothing has been created for it | all six, in order |
+| **REVISE a form** — `PATCH` | the form already exists and a request changes **what it collects**: *"add a dropdown for job industry"*, *"make the phone optional"*, *"add a file upload"*, *"drop the budget question"* | 1 (auth) → 3 (author just the new field) → **4b · Revising a form later** → 5 (re-verify) → 6 (rewrite the config, then wire the control) |
+
+A field the visitor can fill that isn't in the schema is **silent data loss** — no submission, no
+inbox, no contact, and the submit still resolves `true`. So never local component state, and never
+delete-and-recreate a live form: **`PATCH` it**, keeping the `formId` the UI already imports.
+
+The six steps, each with a section below:
 
 1. **Authenticate** — get an elevated credential; the public client ID cannot write.
-2. **Install the Wix Forms app** — idempotent, and nothing works until it's there.
+2. **Install the Wix Forms app** — idempotent, and nothing works until it's there. *(create only.)*
 3. **Author the form body** — adapt the every-field payload to what the request asks for.
-4. **Create the form** — POST each body; a `200` here means almost nothing.
+4. **Create the form** — POST each body; a `200` here means almost nothing. *(revising: **4b**.)*
 5. **Verify it works** — read the form back, and **submit to it once** for real.
 6. **Hand off** — the verified `formId` + field `target`s are written to a file the UI imports.
 
@@ -13,7 +25,7 @@ Creating a form is an **admin/build-time** job, in six sequential steps. Each ha
 
 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 |
@@ -22,7 +34,7 @@ live Wix API reference.
 | 3 | Create Form | https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/create-form.md | the create call, plus 10 complete request examples — the source of the payload below |
 | 3 | Form object | https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/form-object.md | each property individually, incl. form-level settings this doc doesn't cover |
 | 4 | Form Schemas API | https://dev.wix.com/docs/api-reference/crm/forms/form-schemas.md | every schema method (get, list, delete, enable/disable) |
-| 4 | Update Form | https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/update-form.md | revising a form without losing its `formId` |
+| 4b | Update Form | https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/update-form.md | the `PATCH`: revising a form without losing its `formId`, and the whole-array replace semantics |
 | 4 | List Forms Providers Configs | https://dev.wix.com/docs/api-reference/crm/forms/form-schemas/list-forms-providers-configs.md | the Forms **app's** ceiling on fields and forms — **not** the site's plan cap, which this call cannot tell you (see step 4) |
 | 5 | Create Submission | https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/create-submission.md | the submission call used to prove the form accepts data |
 | 5 | About Submission Values | https://dev.wix.com/docs/api-reference/crm/forms/form-submissions/about-submission-values.md | the value shape each `inputType` submits — string, array, address object, … |
@@ -77,8 +89,10 @@ costs nothing.
 ## 3 · Author the form body — every field type
 
 There is **one** create call:
-`POST https://www.wixapis.com/form-schema-service/v4/forms` with `{ "form": { … } }`.
-**You author that body**, starting from the payload below and adapting it to the request.
+`POST https://www.wixapis.com/form-schema-service/v4/forms` with
+`{ "form": { "namespace": "wix.form_app.form", … } }` — that namespace is the Wix Forms app's, and
+the only one the owner's dashboard shows. **You author that body**, starting from the payload below
+and adapting it to the request.
 
 The payload is one form holding **every field type Wix Forms supports**. Each field block is copied
 verbatim from the official Create Form examples, so the `identifier` / `inputType` / `componentType`
@@ -155,10 +169,18 @@ owner's dashboard, or on the first real submission.
 - **`required` lives at `inputOptions.required`**, never inside a validation block.
 - **`validation` is always present**, even as `{}`, and nests under the **`inputType`** options
   object — not the `componentType` one.
+- **A choice field's `identifier` IS its kind** — `DROPDOWN`, `RADIO_GROUP`, `CHECKBOX_GROUP`,
+  `TAGS` — matching the `componentType`, never `TEXT_INPUT`: the identifier routes the field to its
+  renderer, so `TEXT_INPUT` + `componentType: DROPDOWN` is accepted and stored as a text input. (A
+  long answer is `TEXT_AREA` for the same reason.)
 - **A choice field declares its options twice** — the component's `options[]` and the validation
   `enum` (`STRING`) or `items.stringOptions.enum` + `itemType` (`ARRAY`) — and the two must agree.
   Get it wrong and the create still returns `200`: the field is created as a **plain text box**,
   losing its choices. Only the 5a component check catches it.
+- **A choice field that came back as a text box: read which options block came home.**
+  `textInputOptions` where you sent `dropdownOptions` is that fallback — and with a well-formed block
+  and `enum`, the cause is the `identifier`. Re-sending it, or delete-and-re-add with the same
+  identifier, reproduces it.
 - **`target` is the immutable submission key**: starts with an ASCII letter, letters/digits/`_`
   only, no `__`, unique within the form. Use field's label converted to snake_case with _ and 6 random alphanumeric  
   characters as the field target, e.g. "First name" -> `first_name_a689be`.
@@ -1578,7 +1600,7 @@ always on the public host, never `/_api/`:
 
 ```
 POST https://www.wixapis.com/form-schema-service/v4/forms
-{ "form": { … the body from step 3 … } }
+{ "form": { "namespace": "wix.form_app.form", … the rest of the body from step 3 … } }
 ```
 
 Read **`form.id`** from the response — that's the `formId` the rest of the run carries. **Record it
@@ -1625,16 +1647,64 @@ proves the form works. Two failures worth recognizing before you retry:
   than discovering the limit after a full authoring pass, and count every entry in `formFields`, the
   `SUBMIT_BUTTON` included.
 
-**Revising a form later** — add a field, relabel one, tighten a rule:
+## 4b · Revising a form later
+
+Add a field, relabel one, tighten a rule, retire one — a `PATCH`, never a second create. Everything
+above still applies; this is the delta.
+
+**Read the form back first — you need its `revision`.** The `formId` comes from
+`src/rest/wix-forms.config.js` (`WIX_FORMS.<key>.formId`), never typed by hand:
 
 ```
+GET https://www.wixapis.com/form-schema-service/v4/forms?namespace=wix.form_app.form&formIds=<formId>
 PATCH https://www.wixapis.com/form-schema-service/v4/forms/<formId>
-{ "form": { …, "revision": "<the form's current revision>" } }
+{ "form": { …the whole object you just read, with your change…, "revision": "<its current revision>" } }
 ```
 
-Never delete-and-recreate: a `PATCH` keeps the `formId` the UI already holds and spends no extra slot
-against the site's form cap. Re-run step 5 afterwards — an update regresses a layout exactly as a
-create can.
+- **`namespace` is a required query parameter on the read**, hence the `?namespace=` above. Without it
+  the read `400`s with `namespace has size 0, expected 10 or more` — a violation naming a *field*, so
+  it reads like a body problem. Fix the call, not the payload.
+- **The read-back is the `PATCH` body.** Apply the change to what the `GET` returned and send that.
+  `namespace` is immutable and travels along; **there is no `fieldMask`**, and no `revision` outside
+  `form`. Inventing either is a silent partial write.
+- **`formFields` replaces wholesale.** Wix: *"Any field that's missing from the array you send is
+  moved to `deletedFormFields`, so resend every field you want to keep."* `steps` behaves the same
+  way. Drops are recoverable from `deletedFormFields` — if you notice, which is step 5's job.
+- **A stale `revision` is rejected** — re-`GET` and re-apply; never guess or increment it.
+- **A new field needs three things generated**: a fresh UUID `id`, a `target` unique in the form
+  (`job_industry_7f2b`), and — for a choice field — an options block whose `enum` and `options[]`
+  agree. Step 3 is the shape, and its warnings still hold.
+
+**Add the layout item too** — append to `steps[<n>].layout.large.items`, mirroring into `medium` /
+`small` if the form has them:
+
+```json
+{ "fieldId": "<the new field's id>", "row": <next row>, "column": 0, "width": 12, "height": 1 }
+```
+
+A field missing from the layout isn't dropped, but it sorts last and has no defined position in the
+owner's builder. To place it mid-form, insert at that `row` and bump every item at or after it — `row`
+restarts at 0 per step.
+
+**Changing a field's component type in place** — a text input that should have been a dropdown — means
+the choice `identifier` and **only** the new options block; don't leave `textInputOptions` beside
+`dropdownOptions`. A read-back still showing `textInputOptions` is the identifier, not the block.
+
+**The other revisions:**
+
+- **label, placeholder, options, validation, order** — patch and stop. The client reads all of those
+  live from the schema, so no config rewrite and no code change follows.
+- **retiring a field the form has submissions for** — set `hidden: true` ("hidden from submitters":
+  the field stops being rendered, and the submissions already collected under it keep their meaning)
+  rather than dropping it from the array. Drop only a field added by mistake in this same run.
+- **never rename a `target`** — it's the storage key, so a rename orphans every submission already
+  collected under the old one. Change the *label* instead.
+
+**Then re-run step 5 in full** — a `PATCH` regresses a form exactly as a create does, and §5a is where
+a dropdown that silently became a text input gets caught. Then step 6, revising: add the read-back
+`target` to `src/rest/wix-forms.config.js` (the one sanctioned edit to that file outside a seed run,
+and only *after* step 5 passes) and wire the control per `INSTRUCTIONS.md`. The field is live for new
+submissions; past ones don't carry it. Step 4's plan gates apply to an added field too.
 
 ## 5 · Verify it works
 
@@ -1671,6 +1741,9 @@ against the returned `form.formFields`:
 GET https://www.wixapis.com/form-schema-service/v4/forms/<formId>/summary
 ```
 
+*(The summary and the single-form `GET` take the id in the path, so neither needs the `namespace`
+query parameter — every **listing** read does.)*
+
 Assert `formSummary.fields` is **non-empty**, with one entry per input field you sent (everything in
 `formFields` except the `SUBMIT_BUTTON`). The summary is exactly what the Wix dashboard renders, so a
 short or empty count means the form is blank — or partly blank — **for the owner**, even while the
@@ -1735,8 +1808,8 @@ DELETE https://www.wixapis.com/form-submission-service/v4/submissions/<id>
 The id comes from the 5c response as **`submission.id`**: REST returns `id`, not the `_id` the
 reference schema shows (that's the SDK's shape). Do this every time — the owner's inbox is a real
 business inbox, and a probe left in it looks like a real enquiry. If a probe ever escapes, find it
-with `POST /form-submission-service/v4/submissions/namespace/query` filtered by `formId` +
-`namespace`.
+with `POST /form-submission-service/v4/submissions/namespace/query`, filtered by `formId` and
+`"namespace": "wix.form_app.form"`.
 
 ## 6 · Hand off
 
@@ -1745,8 +1818,9 @@ form, keyed by the form's name lowercased with each run of non-alphanumerics col
 `_` (`"Quote request"` → `quote_request`):
 
 ```js
-// Written by the seed run once step 5 passed. Do not hand-edit, and do not create it early:
-// its existence is what proves the form schemas were created AND verified.
+// Written by the seed run once step 5 passed. Do not create it early: its existence is what proves
+// the form schemas were created AND verified. Its only later edit is a verified schema change —
+// see step 4b; never a hand-typed field.
 export const WIX_FORMS = {
   contact: { formId: "…", name: "Contact", targets: { email: true, message: true } },
 };

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) ─────────────────