@wix/agent-skills 1.18.0 → 1.18.2

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

@@ -23,7 +23,7 @@ Everything is under `.agents/skills/wix-vibe-headless/references/`.
   **shapes**, fieldsets, and paging.
 - `app/{components,pages,hooks,context}/…` — a **reference UI** (+ hooks/providers) built on that data
   layer; the field shapes and route patterns it uses (e.g. `/product/:slug`) are the data contract.
-- `seed/seed-*.js` — build-time **seeding functions** that create content.
+- `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.
 
@@ -31,15 +31,15 @@ Everything is under `.agents/skills/wix-vibe-headless/references/`.
 
 | vertical | `app/rest/` data layer | seed module |
 |---|---|---|
-| storefront | `wix-store-catalog.js`, `wix-store-cart.js` — products & variants; server cart + checkout redirect | `seed-store.js` |
-| bookings | `wix-bookings-services.js`, `wix-bookings-checkout.js` — services/categories/slots; booking + checkout | `seed-bookings.js` |
-| blog | `wix-blog.js` — posts (list + by-slug), categories, tags | `seed-blog.js` |
-| events | `wix-events-browse.js`, `wix-events-registration.js` — events & categories; RSVP / ticketing + checkout | `seed-events.js` |
-| portfolio | `wix-portfolio.js` — collections, projects, galleries | `seed-portfolio.js` |
-| restaurants | `wix-restaurants-menu.js`, `-ordering.js`, `-reservations.js` — menu; online ordering; table reservations | `seed-restaurants.js` |
+| 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 | `seed-cms.js` |
-| pricing-plans | `wix-pricing-plans.js` — plans list + subscribe/checkout | `seed-pricing-plans.js` |
+| 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
@@ -57,7 +57,7 @@ within each. **One exception — `forms` must be seeded before its UI is built;
 ### 1 · Install the skills
 
 Two skills, into `.agents/skills/`: **`wix-vibe-headless`** (this build guide + the seed modules —
-self-contained) and **`wix-docs`** (fallback to search/read the Wix API reference).
+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
@@ -110,8 +110,9 @@ 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); use `wix-docs`
-for anything they don't cover. Content queries return `REQUIRED_APP_NOT_INSTALLED` until the app is
+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.
 

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

@@ -40,16 +40,9 @@ end). (Files missing? the install's `deploy` result lists what it wrote; re-run
 `references/blog/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 @@ reference page inline.
   included; add them as an authenticated `wixApiRequest` call).
 
 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 `Blog`/`PostDetail`/category/tag pages to add chrome.
 - The Layout's fixed top region owns positioning: `<WixManageBanner/>` above `<Header/>`; your `Header` is plain in-flow markup (not `position:fixed`).
 - Route by `slug` through the shipped helpers — never hand-build a post/category/tag URL. Display categories/tags by `.label` (not `.name`).
@@ -226,7 +218,6 @@ connector) — separate from this client build; 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 the vertical's data route(s)** (not just the home page) — `/blog` and a post detail page (plus a category/tag 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 `Blog`/`PostDetail`/`CategoryPage`/`TagPage` untouched; content clears the fixed chrome; `<TaxonomyProvider>` wraps the tree.
 - [ ] Feed lists live published posts (newest first) and paginates via `nextCursor`; post detail loads by `slug`; a bad slug shows the not-found state (no invented post).

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

@@ -1,11 +1,11 @@
 # Blog — seeding
 
-Seed a Wix Blog (Blog V3) by **calling `seed-blog.js`** — don't hand-write the REST calls. It's
+Seed a Wix Blog (Blog V3) by **calling `seed-blog.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 Blog
 seed operation. `require` it and call the functions with plain data.
 
 > **NOT yet live-verified — transcribed from `setup-blog.md`.** Endpoints/fields mirror the recipe
-> exactly; if a call returns an unexpected shape, use the **`wix-docs`** skill (never guess).
+> exactly; if a call returns an unexpected shape, use the documentation skill available in your environment (never guess).
 
 **DEFAULT — one call.** `setupBlog(ctx, plan)` runs the whole flow (memberId → categories/tags →
 posts → covers), keeping every id in memory. Pass category/tag **names** and it resolves them to
@@ -15,11 +15,7 @@ for you (Blog binds the cover by the Wix Media file id, not a url).
 ```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/blog/seed/seed-blog.js", "utf8"))(m, m.exports, require);
-  return m.exports; })();
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/blog/seed/seed-blog.cjs"));
 const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 
 const result = await seed.setupBlog(ctx, {
@@ -88,7 +84,7 @@ first** (`installBlogApp`, idempotent), so seeding works even if the site doesn'
 
 ## 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 Blog API reference — never guess. The
+use the documentation skill available in your environment to search + read the live Wix Blog API reference — never guess. The
 authoritative source recipe is `wix-headless/references/inline-recipes/setup-blog.md`.
 
 Read a method's page before writing its call: it carries the exact body shape, the required

package/skills/wix-vibe-headless/references/blog/seed/{seed-blog.js → seed-blog.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/blog/seed/seed-blog.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/blog/seed/seed-blog.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //   const memberId = await seed.getAuthorMemberId(ctx);                    // STEP 1 — required for every post
 //   const cats = await seed.createCategories(ctx, ["Recipes", "Brewing"]); // STEP 3 — only if the brief groups posts
@@ -22,8 +22,7 @@
 //   await seed.attachPostCovers(ctx, posts.map((p, i) => ({ postId: p.id, fileId: files[i].id })));
 //
 // Live-verified end-to-end (members author, categories, posts single+bulk, tags, covers, idempotent
-// re-runs). If any call ever fails with a shape the caller didn't expect, fall back to the wix-docs
-// skill (search + read the live Wix Blog API reference) — never guess. Source recipe:
+// re-runs). If any call ever fails with a shape the caller didn't expect, fall back to the documentation skill available in your environment (search + read the live Wix Blog API reference) — never guess. Source recipe:
 // wix-headless/references/inline-recipes/setup-blog.md.
 
 const API = "https://www.wixapis.com";

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

@@ -51,16 +51,9 @@ the end). (Files missing? the install's `deploy` result lists what it wrote; re-
 `references/bookings/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.
@@ -207,7 +200,7 @@ window.location.href = checkoutUrl;   // hosted checkout; on return the booking
 ## Extending the client
 The shipped flow covers **APPOINTMENT and CLASS** services (`listSlotsForService` routes by
 `service.type`). For anything beyond that, add a helper on `wixApiRequest`, looking the endpoint up
-in the **`wix-docs`** skill first (never guess):
+using the documentation skill available in your environment first (never guess):
 - **COURSE** enrollment — a course is enrolled as a *whole*, not per session; `listEventTimeSlots`
   returns no slots for it, so the slot-picker flow doesn't apply (course-specific flow).
 - **Service variants / participants** (duration- or person-based pricing), **add-ons**, and
@@ -217,7 +210,7 @@ in the **`wix-docs`** skill first (never guess):
   them see their own appointments.
 
 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. Each helper in
+file under `src/`, or look it up via the documentation skill available in your environment. Each helper in
 `wix-bookings-services.js` / `wix-bookings-checkout.js` links its own reference page inline; these are
 the areas they sit in:
 - Bookings (services, categories, bookings): https://dev.wix.com/docs/api-reference/business-solutions/bookings.md
@@ -269,7 +262,6 @@ identical.
 - **One unit type per service.** A room rented by the hour *and* by the day is two services.
 
 ## 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
   `Services`/`ServiceDetail` to add chrome.
 - The Layout's fixed top region owns positioning: `<WixManageBanner/>` above `<Header/>`; your
@@ -297,7 +289,6 @@ build; 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 `/services` and a service detail page** (not just the home page) and confirmed the shipped cards render themed (surface, text, brand color) with images.
 - [ ] `Layout` (fixed `<WixManageBanner/>` + `<Header/>` region, then `<Outlet/>` + Footer) wraps all
       routes; shipped `Services`/`ServiceDetail` untouched; content clears the fixed chrome.

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

@@ -1,6 +1,6 @@
 # Bookings — seeding
 
-Seed a Wix Bookings catalog by **calling `seed-bookings.js`** — don't hand-write the REST calls.
+Seed a Wix Bookings catalog by **calling `seed-bookings.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
 Bookings seed operation. Load it and call **`setupBookings` — the one-call path** — with plain data.
 
@@ -9,11 +9,7 @@ Bookings seed operation. Load it and call **`setupBookings` — the one-call pat
 ```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/bookings/seed/seed-bookings.js", "utf8"))(m, m.exports, require);
-  return m.exports; })();
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/bookings/seed/seed-bookings.cjs"));
 const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 
 // ONE call: install → resolve staff → categories → services → CLASS sessions → images, all in the
@@ -103,12 +99,12 @@ same body; don't loop and don't re-create the ones that already succeeded.
 
 ## Rentals
 
-`seed-rentals.js` is the rentals half — the same transport, a different create order and payload.
+`seed-rentals.cjs` is the rentals half — the same transport, a different create order and payload.
 Wix Rentals has no APIs of its own, so a rental is a Bookings service with rentals-specific
 field values.
 
 ```js
-const seed = require("…/references/bookings/seed/seed-rentals.js");
+const seed = require(require("path").resolve(".agents/skills/wix-vibe-headless/references/bookings/seed/seed-rentals.cjs"));
 await seed.setupRentals(ctx, {
   resourceTypeName: "Meeting rooms",
   resources: ["Room A", "Room B"],              // parallel capacity = MORE RESOURCES
@@ -144,7 +140,7 @@ than a multi-service group. Pass `workingHours` only when the brief names openin
 
 ## 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-bookings.md`.
 
 Read a method's page before writing its call: it carries the exact body shape, the required

package/skills/wix-vibe-headless/references/bookings/seed/{seed-bookings.js → seed-bookings.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/bookings/seed/seed-bookings.js");
+//   const seed = require("/app/.agents/skills/wix-vibe-headless/references/bookings/seed/seed-bookings.cjs");
 //   const ctx = { token: accessToken, siteId: WIX_METASITE_ID };
 //
 //   await seed.installBookingsApp(ctx);                          // if the site doesn't have Wix Bookings yet
@@ -32,7 +32,7 @@
 //   // await seed.attachServiceImage(ctx, { serviceId: s.id, revision: s.revision, image: { id: file.id, url: file.url, width: 1024, height: 1024 } });
 //
 // If any call fails with a shape the caller didn't expect, or you need an operation this module
-// doesn't cover, fall back to the wix-docs skill (search + read the live Wix API reference) —
+// doesn't cover, 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-bookings.md.
 
 const API = "https://www.wixapis.com";

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

@@ -15,6 +15,12 @@ field — the shipped utils supply the schema behind it, the state, the validati
 > Use **`cms`** only when the app must **read the entries back** (a gallery, a listing, "my
 > submissions") — a visitor cannot read Forms submissions. Submit-only → forms.
 
+> **⚠️ "Add a field" is a SCHEMA change.** *"Add a dropdown for job industry"*, *"make the phone
+> optional"*, *"drop the budget question"* — all reads like UI work and all are a `PATCH` to the live
+> schema (`seed/SEED.md`, REVISE): patch it, verify, rewrite `wix-forms.config.js`, **then** wire the
+> control. A field the visitor can fill that isn't in the schema is **silent data loss** — the value
+> reaches no submission, inbox or contact, and the submit still resolves `true`.
+
 ## What ships (utils only)
 
 | file | what it is |
@@ -24,7 +30,7 @@ field — the shipped utils supply the schema behind it, the state, the validati
 | `rest/wix-forms-submissions.js` | Write transport: `toSubmissionValues`, `createSubmission`, `SUBMITTED_OK`, the file flow (`getMediaUploadUrl`, `uploadSubmissionFile`, `uploadFormFiles`), `submissionViolations`. |
 | `hooks/useWixForm.js` | The form's non-visual half: `useWixForm(formId)` → `{ form, values, setValues, bind, submit, validate, errors, loading, read }`. Also exports `validateField`, `mapSubmissionErrors`, `FORM_ERROR`. Not on React? Those plus `lib/` are the load-bearing part; port the state around them. |
 | `wix-config.js` *(shared)* | the two ids, written by the install step. |
-| `wix-forms.config.js` *(generated)* | **the gate** — `WIX_FORMS`: each form's `formId` + read-back `targets`, written by the seed after verification. |
+| `wix-forms.config.js` *(generated)* | **the gate** — `WIX_FORMS`: each form's `formId` + read-back `targets`, written by the seed after verification. Its one later edit is a verified schema change (REVISE), never a hand-typed field. |
 | `WixManageBanner` *(shared)* | Dev-only manage banner — mount it in your Layout. |
 
 ## Prerequisites — a HARD GATE
@@ -384,6 +390,9 @@ Don't reach for `role="form"`, an `aria-label` on an input that already has a `<
 ## Hard rules
 
 - A visitor-fillable form is this vertical, not `cms`.
+- **Never hold a form field in local component state** — a value outside the hook's `values` submits
+  nothing. Adding a field is a schema change: `seed/SEED.md`, REVISE.
+- **Never answer a field request with a dashboard link** — that link is for the owner's own edits.
 - Read and write only through the shipped helpers — never hand-build a Wix Forms URL.
 - Never invent a `target`, label, option or constraint — every one comes from the schema (authored
   markup included). Never detect a control by its `target` name either.
@@ -412,8 +421,9 @@ 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. Calling an endpoint the helpers don't wrap is fine via `wixApiRequest` — look up the exact
-method and body first (or use the `wix-docs` skill), never guess.
+authored, and REVISE for changing one. Calling an endpoint the helpers don't wrap is fine via
+`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
@@ -438,21 +448,28 @@ checks the dashboard summary, sends and deletes one real submission), then write
 `src/rest/wix-forms.config.js`. Needs an elevated credential, and **does not run in parallel with the
 client** — see Prerequisites.
 
+**Changing a form that already exists** — a new field, a relabel, a tightened rule — is that doc's
+**REVISE** action: `PATCH` on the current `revision`, re-verify, rewrite the config, wire the
+control. Never a second create.
+
 ## Point the user to their dashboard
 
 Substitute the site's `metaSiteId`:
 
 - **Forms list** — `https://manage.wix.com/dashboard/{metaSiteId}/wix-forms`
-- **Form builder** — `https://manage.wix.com/dashboard/{metaSiteId}/wix-forms/form/{formId}` → add,
-  relabel, reorder or require fields; every change reflects on the site with no code change.
-- **Submissions** — `https://manage.wix.com/dashboard/{metaSiteId}/wix-forms-and-payments/submissions`
-- **Forms settings** (incl. notifications) — `https://manage.wix.com/dashboard/{metaSiteId}/wix-forms-and-payments/settings`
+- **Form builder** — `https://manage.wix.com/dashboard/{metaSiteId}/wix-forms/form/{formId}` → where
+  the **owner** edits fields; a relabel or new option reaches a looped form with no code change, a new
+  field still needs a control. **Asked to change the form yourself? REVISE, not this link.**
+- **Submissions** — `https://manage.wix.com/dashboard/{metaSiteId}/wix-forms/form/{formId}/submissions`
+  → per form, off its builder path; there's no site-wide submissions page to link
 - **Contacts** — `https://manage.wix.com/dashboard/{metaSiteId}/contacts` → contact-mapped fields
   create or update a contact automatically.
 
 ## Verify
 
 - [ ] `wix-forms.config.js` exists; every `formId` comes from `WIX_FORMS`, none typed by hand.
+- [ ] Every control's `name` inside the `<form>` is a target in `WIX_FORMS.<key>.targets`, and its
+      value lives in the hook's `values` — **no field is backed by local state**.
 - [ ] `WIX_CLIENT_ID` set (not the placeholder).
 - [ ] Looped form: relabel a field in the dashboard, reload, the new label appears with no code
       change. Authored form: every `target` in the JSX matches `WIX_FORMS.<key>.targets` exactly.