@wix/agent-skills 1.5.0 → 1.7.0

package/skills/wix-headless/references/shared/MCP_PREFIX.md

@@ -1,105 +0,0 @@
-# Wix MCP Tool Prefix — Discovery & Propagation
-
-Wix MCP tools are exposed under one of two prefixes depending on how the user installed the integration:
-
-| Install mode | Prefix |
-|---|---|
-| **Plugin** (typical for end users) | `mcp__plugin_<plugin-name>_wix-mcp-remote__` (e.g. `mcp__plugin_wix-headless_wix-mcp-remote__WixREADME`) |
-| **Direct MCP server** | `mcp__wix-mcp-remote__` (e.g. `mcp__wix-mcp-remote__WixREADME`) |
-
-Tool **suffixes** are identical in both modes: `WixREADME`, `CallWixSiteAPI`, `ListWixSites`, `ManageWixSite`, `SearchWixHeadlessDocumentation`, `SearchWixSDKDocumentation`, `SearchWixRESTDocumentation`, `BrowseWixRESTDocsMenu`, `ReadFullDocsArticle`, `ReadFullDocsMethodSchema`. Only the prefix differs.
-
-Documentation in this plugin uses the canonical short form (`mcp__wix-mcp-remote__<suffix>`) for readability — substitute the discovered prefix at runtime.
-
----
-
-## Discovery — entry-point skills only, once per session
-
-The entry-point skill (`wix-headless`) MUST run this before any other MCP call:
-
-1. Use whatever tool-discovery primitive your runtime provides to look up `WixREADME`.
-2. From the returned tool name, strip the trailing `WixREADME` — what remains (ending in `wix-mcp-remote__`) is the **MCP prefix**. Examples:
-   - Returned name `mcp__plugin_wix_wix-mcp-remote__WixREADME` → prefix `mcp__plugin_wix_wix-mcp-remote__`
-   - Returned name `mcp__wix-mcp-remote__WixREADME` → prefix `mcp__wix-mcp-remote__`
-3. Call `<prefix>WixREADME` once to verify connectivity.
-4. **If discovery returns no match, or the verify call fails:** stop and tell the user:
-   > *"Wix MCP tools are not available in this session. Please ensure the Wix MCP server is connected (or that the Wix plugin is enabled), then restart your client."*
-5. Hold the discovered prefix in working memory for the rest of the session — use it for every MCP call AND pass it into every subagent prompt.
-
----
-
-## Propagation to subagents
-
-Subagents (every Phase 1 / Phase 2 / Phase 3 / Phase 4 implementer) are isolated workers — they see only the prompt their parent gave them, not the parent's session state. Every subagent prompt MUST include this line verbatim near the top:
-
-```
-MCP tool prefix: <discovered prefix>
-Use this prefix for every Wix MCP call. Example: <prefix>CallWixSiteAPI, <prefix>WixREADME.
-```
-
-Without this line the subagent will try the canonical short form and fail in plugin mode.
-
----
-
-## `CallWixSiteAPI` call conventions — read before the first call
-
-`CallWixSiteAPI` is the most error-prone tool in this plugin. Two failure modes recur; avoid both:
-
-**1. Missing required wrapper params.** The tool requires — in addition to `method`, `url`, `body` — these wrapper fields:
-
-- `siteId` — from `wix.config.json` (or the parent prompt)
-- `reason` — one-sentence human reason, e.g. `"Install Wix Stores app for <brand>"`
-- `sourceDocUrl` — the Wix docs URL the recipe is from, e.g. `"https://dev.wix.com/docs/picasso/wix-ai-docs/recipes-v2/manage/platform/recipe-install-wix-apps"`
-
-**2. `body` passed as a stringified JSON.** `body` is typed `anyOf: [object, array]` — pass it as a real structured value. `body: "{\"tenant\":…}"` will be rejected with `Expected object, received string`.
-
-**The safe pattern — follow on the first `CallWixSiteAPI` of each session:**
-
-1. **Load the schema** via your runtime's tool-discovery primitive (the orchestrator's Step 0 already did this for the whole session per `<SKILL_ROOT>/references/commands/mcp-bootstrap.md` — only re-load if you hit a tool-not-found error).
-2. Call with the full shape:
-   ```
-   <prefix>CallWixSiteAPI(
-     siteId: "<siteId from wix.config.json>",
-     reason: "<one-sentence reason>",
-     sourceDocUrl: "<URL of the Wix docs recipe you're following>",
-     method: "POST",
-     url: "https://www.wixapis.com/<service>/<path>",
-     body: { …as a real object, not a string }
-   )
-   ```
-
-**When you see reference snippets written in prose-HTTP form** (e.g. `CallWixSiteAPI: POST /blog/v3/posts` followed by `body: { … }`), translate them into the full tool-call shape above — the prose form omits the wrapper fields for readability, not because they're optional.
-
-## Defensive fallback — required in every implementer agent
-
-If a Wix MCP call returns "tool not found" or the tool name appears unavailable for any reason:
-
-1. Re-discover the tool via your runtime's tool-discovery primitive, looking up the suffix (e.g. `CallWixSiteAPI`).
-2. Use the discovered tool name and retry the call.
-3. **Do NOT bail.** Only escalate to the user if discovery itself returns no match.
-
-This guards against parents that forgot to pass the prefix and against future prefix-scheme changes.
-
----
-
-## Prefer bundled reference docs over external doc reads
-
-Your agent directory includes `.md` reference files with API recipes, call templates, and error handling tailored to your scope. These are your primary source — they document the exact call patterns, body shapes, and edge cases for your use case.
-
-The Wix MCP also exposes documentation tools (`SearchWixRESTDocumentation`, `ReadFullDocsArticle`, `SearchWixSDKDocumentation`, etc.). These are useful when you hit an error or edge case not covered by your reference files. But **prefer your bundled `.md` files first** — each external doc read costs a tool call and 15-30s, and the bundled recipes are already validated for this plugin's flows.
-
-**Rule of thumb:** read your reference files → try the documented recipe → only if you get an unexpected error or need an endpoint not covered, fall back to the MCP doc tools.
-
----
-
-## Absolute paths — never trust CWD-relative instruction locations
-
-Subagents launched by the orchestrator run with the project directory as CWD (e.g. `/Users/.../headless-projects/chairloom/`), not the skill root. Your instruction file and its sibling references live **inside the skill**, not in your CWD — e.g. the stores instructions live at `<skill-root>/references/stores/INSTRUCTIONS.md`.
-
-**Rule:** every implementer prompt MUST include an `Instruction file (absolute path)` line pointing at the right `INSTRUCTIONS.md`. Read that file and only that path. Then use the absolute paths it lists for sibling references. Never:
-
-- Resolve `references/stores/INSTRUCTIONS.md` against your CWD — it doesn't exist there.
-- `Glob **/INSTRUCTIONS.md` or `**/agents/**` to "find" your instructions — that walks the project tree and finds nothing relevant; it's the most expensive failure mode in current runs.
-- Walk up from the project directory looking for the skill root — guess wrong and you'll burn minutes globbing.
-
-If your prompt is missing the absolute `Instruction file` line, ask the parent (don't guess). The `wix-headless` skill is responsible for computing and passing this absolute path in every agent-launch prompt (see `references/ORCHESTRATION.md` § "Agent prompt template").

package/skills/wix-headless/scripts/copy-utility-templates.mjs

@@ -1,153 +0,0 @@
-#!/usr/bin/env node
-// Copy templated utility files into the project for the named phase.
-// Invoked by the wix-headless skill orchestrator before Phase 3 Components or
-// Phase 4 Pages dispatches, so that mechanical SDK-wrapper utilities
-// (back-in-stock.ts, discounts.ts, categories.ts) are on disk by the time
-// agents start.
-//
-// These files are pure templates — same shape regardless of brand. Letting an
-// LLM regenerate them costs tokens and risks drift. Pre-copying is structurally
-// better.
-//
-// Usage (both modes work):
-//   node <SKILL_ROOT>/scripts/copy-utility-templates.mjs <project-dir> <phase>
-//   curl -s https://dev.wix.com/skills/wix-headless/scripts/copy-utility-templates.mjs \
-//     | node --input-type=module - <project-dir> <phase>
-//
-//   <phase> ∈ { "components", "pages" }
-//
-// Note: `node <(curl ...)` does NOT work for .mjs files — Node sees /dev/fd/N
-// with no extension and rejects ESM syntax. Use the stdin form above.
-//
-// Template files auto-detect whether they can be read on disk (tgz install)
-// and fall back to HTTP fetch when streamed via stdin.
-//
-// Reads `.wix/site.json` to discover which packs are loaded, then copies the
-// matching templates for the given phase. Never overwrites an existing file
-// (so user customisations and earlier orchestrator state are preserved).
-
-import { readFileSync, writeFileSync, existsSync, mkdirSync, copyFileSync } from "node:fs";
-import { join, dirname, resolve } from "node:path";
-import { fileURLToPath } from "node:url";
-
-const SKILL_URL = "https://dev.wix.com/skills/wix-headless";
-
-// Mode detection — see check-manifest.mjs for the same pattern.
-let SKILL_ROOT_DISK = null;
-try {
-  const scriptDir = dirname(fileURLToPath(import.meta.url));
-  const candidate = resolve(scriptDir, "..");
-  if (existsSync(join(candidate, "templates"))) {
-    SKILL_ROOT_DISK = candidate;
-  }
-} catch {
-  // fileURLToPath may fail on non-file URLs; fall through to URL mode.
-}
-
-// Copy a template file (path relative to <SKILL_ROOT>/templates/) into the
-// project at destPath. Returns { ok: true } on success, or { ok: false,
-// reason: "..." } on failure (source missing, HTTP error, IO error).
-async function copyTemplate(sourceRel, destPath) {
-  if (SKILL_ROOT_DISK) {
-    const src = join(SKILL_ROOT_DISK, "templates", sourceRel);
-    if (!existsSync(src)) return { ok: false, reason: `missing on disk: ${src}` };
-    try {
-      mkdirSync(dirname(destPath), { recursive: true });
-      copyFileSync(src, destPath);
-      return { ok: true };
-    } catch (e) {
-      return { ok: false, reason: e.message };
-    }
-  }
-  const url = `${SKILL_URL}/templates/${sourceRel}`;
-  try {
-    const r = await fetch(url);
-    if (r.status === 404) return { ok: false, reason: `missing at ${url}` };
-    if (!r.ok) return { ok: false, reason: `fetch ${url}: HTTP ${r.status}` };
-    const text = await r.text();
-    mkdirSync(dirname(destPath), { recursive: true });
-    writeFileSync(destPath, text);
-    return { ok: true };
-  } catch (e) {
-    return { ok: false, reason: e.message };
-  }
-}
-
-// Hardcoded mapping: { pack, phase, source (relative to templates dir), dest (relative to project) }.
-// To add a new templated utility: ship the file under templates/<pack>/, then add
-// an entry here. Keep this list small — only files that are pure SDK wrappers
-// with no brand-specific content belong here.
-const TEMPLATES = [
-  { pack: "stores", phase: "components", source: "stores/back-in-stock.ts", dest: "src/utils/back-in-stock.ts" },
-  { pack: "ecom", phase: "components", source: "ecom/discounts.ts", dest: "src/utils/discounts.ts" },
-  { pack: "stores", phase: "pages", source: "stores/categories.ts", dest: "src/utils/categories.ts" },
-];
-
-const projectDir = process.argv[2];
-const phase = process.argv[3];
-
-if (!projectDir || !phase) {
-  console.error("usage: copy-utility-templates.mjs <project-dir> <phase>");
-  console.error("  <phase> ∈ { components, pages }");
-  process.exit(2);
-}
-
-if (phase !== "components" && phase !== "pages") {
-  console.error(`copy-utility-templates: invalid phase "${phase}" — must be "components" or "pages"`);
-  process.exit(2);
-}
-
-const sitePath = join(projectDir, ".wix/site.json");
-let loadedPacks;
-try {
-  const site = JSON.parse(readFileSync(sitePath, "utf8"));
-  loadedPacks = new Set(site.verticals ?? []);
-  if (loadedPacks.size === 0) {
-    console.error(`copy-utility-templates: site.json.verticals is empty — has Setup completed?`);
-    process.exit(1);
-  }
-} catch (e) {
-  console.error(`copy-utility-templates: cannot read ${sitePath} (${e.message}). Has Setup completed?`);
-  process.exit(1);
-}
-
-const candidates = TEMPLATES.filter((t) => t.phase === phase && loadedPacks.has(t.pack));
-
-if (candidates.length === 0) {
-  console.log(`copy-utility-templates: no templates for phase "${phase}" with loaded packs ${[...loadedPacks].join(", ")} — nothing to do`);
-  process.exit(0);
-}
-
-const copied = [];
-const skipped = [];
-const errors = [];
-
-for (const { pack, source, dest } of candidates) {
-  const destPath = join(projectDir, dest);
-
-  if (existsSync(destPath)) {
-    skipped.push(dest);
-    continue;
-  }
-
-  const result = await copyTemplate(source, destPath);
-  if (result.ok) {
-    copied.push(dest);
-  } else {
-    errors.push(`failed to copy ${source} → ${dest} (pack "${pack}"): ${result.reason}`);
-  }
-}
-
-const summary = {
-  phase,
-  packs: [...loadedPacks],
-  copied,
-  skipped,
-  errors,
-};
-
-console.log(JSON.stringify(summary, null, 2));
-
-if (errors.length > 0) {
-  process.exit(1);
-}

package/skills/wix-headless/templates/ecom/components-ecom.css

@@ -1,215 +0,0 @@
-/* src/styles/components-ecom.css
- *
- * Ecom-pack component CSS. Owned by the ecom Phase 3 components agent.
- *
- * This file is the SINGLE source of truth for ecom-component classes.
- * The designer's global.css does NOT publish .cart-summary, .cart-total,
- * .cart-empty, or .checkout-btn — those all live here. See
- * references/shared/STYLING.md § "Component-specific CSS is owned by the
- * component, not the designer".
- *
- * Class groups in this file:
- * - .cart-summary / .cart-total / .cart-empty / .checkout-btn → /cart page summary panel and empty state
- * - .cart-item / .cart-item-* / .qty-* → CartView.tsx line items
- * - .cart-discount / .cart-applied-discounts → CartView.tsx discount rows
- * - .cart-badge / .cart-badge-* → CartBadge.tsx (mounted in Navigation)
- *
- * Tailwind v4 requires @reference in non-entrypoint CSS files that use @apply
- * — without these, utilities like `size-6` fail at build with "Cannot apply
- * unknown utility class". Do not remove.
- */
-@reference "tailwindcss";
-@reference "./global.css";
-
-/* =========================================================================
-   Cart summary panel + total + checkout button + empty state.
-   Owned here, NOT in global.css. The .checkout-btn extends .btn-primary
-   (which IS designer-owned) and adds full-width + :disabled treatment.
-   ========================================================================= */
-.cart-summary {
-  background: var(--color-paper-warm, var(--color-cream));
-  border: 1px solid var(--color-rule);
-  padding: var(--spacing-xl);
-  border-radius: var(--radius-md);
-  display: flex;
-  flex-direction: column;
-  gap: var(--spacing-sm);
-}
-@media (min-width: 768px) {
-  .cart-summary {
-    position: sticky;
-    top: var(--spacing-xl);
-  }
-}
-
-.cart-empty {
-  text-align: center;
-  padding-block: var(--spacing-3xl);
-  color: var(--color-mute);
-}
-.cart-empty .checkout-btn {
-  display: inline-flex;
-  width: auto;
-  max-width: 18rem;
-}
-
-/* .checkout-btn composes the designer's `btn` @utility primitive plus the brand's
-   primary fill. Do NOT use `@apply btn-primary` here — Tailwind v4 only @applies
-   utilities declared with `@utility` (which `btn` is in global.css), not plain
-   custom classes like `.btn-primary` (which is just a regular CSS rule). The build
-   fails with "Cannot apply unknown utility class `btn-primary`" if you try.
-   The Phase 3 agent's brand-token swap (bark → navy/charcoal/coral/etc.) adapts
-   the var names without changing the composition shape. an earlier run on 2026-04-30 hit
-   this; the recovery cost ~1 min and a rebuild. */
-.checkout-btn {
-  @apply btn;
-  background: var(--color-bark);
-  color: var(--color-cream);
-  box-shadow: var(--shadow-sm);
-  width: 100%;
-  margin-top: var(--spacing-md);
-}
-.checkout-btn:hover:not(:disabled) {
-  background: var(--color-tobacco);
-  box-shadow: var(--shadow-md);
-}
-.checkout-btn:disabled {
-  opacity: 0.5;
-  cursor: not-allowed;
-}
-
-/* --- Cart badge icon safety net --- */
-/* CartBadge.tsx renders an inline SVG bag icon + optional count span. The designer
-   owns .cart-badge in global.css; these rules guarantee an icon-button layout
-   (relative positioning anchor, centered icon, count pill overlap) even if the
-   designer's rule is purely aesthetic. */
-.cart-badge {
-  @apply relative inline-flex items-center justify-center;
-}
-.cart-badge-icon {
-  @apply size-6 shrink-0;
-}
-.cart-badge-count {
-  @apply absolute -top-1 -right-2 min-w-5 h-5 px-1 inline-flex items-center justify-center rounded-full bg-bark text-cream text-xs font-body tabular-nums leading-none;
-}
-
-/* --- Cart layout safety net --- */
-/* .cart-item is a global contract class styled by the designer in global.css.
-   These rules ensure the row layout works even if the designer omits flex. */
-.cart-item {
-  @apply flex flex-row gap-md;
-}
-.cart-item-image {
-  @apply shrink-0;
-}
-/* Clickable image + name link back to /products/<slug>.
-   At-rest underline + pointer cursor so the link is discoverable without
-   hovering (critical on touch). Muted rule-color underline keeps visual
-   weight in line with the body text; hover/focus escalates to tobacco. */
-.cart-item-image-link {
-  @apply block shrink-0 cursor-pointer;
-}
-.cart-item-image-link:hover .cart-item-image,
-.cart-item-image-link:focus-visible .cart-item-image {
-  @apply border-ink;
-}
-.cart-item-name-link {
-  @apply text-inherit cursor-pointer no-underline;
-  /* border-bottom is more predictable than text-decoration-line for inline
-     <a> inside <h3> (no text-decoration inheritance quirks). Muted ink at
-     rest, tobacco on hover. */
-  border-bottom: 1px solid var(--color-muted);
-  padding-bottom: 1px;
-  transition: color 150ms ease, border-color 150ms ease;
-}
-.cart-item-name-link:hover,
-.cart-item-name-link:focus-visible {
-  @apply text-tobacco outline-none;
-  border-bottom-color: var(--color-tobacco);
-}
-.cart-item-info {
-  @apply flex-1 min-w-0;
-}
-
-/* --- Description lines & modifiers --- */
-.cart-item-option {
-  @apply text-sm text-bark/70 font-body my-0.5;
-}
-.cart-item-modifiers {
-  @apply mt-1;
-}
-
-/* --- Quantity stepper --- */
-.cart-item-qty {
-  @apply inline-flex items-center gap-sm mt-sm w-fit;
-}
-.qty-btn {
-  @apply size-7 inline-flex items-center justify-center border border-bark rounded bg-transparent text-bark cursor-pointer font-body text-base leading-none;
-}
-.qty-btn:disabled {
-  @apply opacity-30 cursor-not-allowed;
-}
-.qty-value {
-  @apply font-body text-sm min-w-6 text-center tabular-nums;
-}
-
-/* --- Unavailable state --- */
-.cart-item-unavailable {
-  @apply text-sm text-red-600 font-medium font-body;
-}
-
-/* --- Price + remove --- */
-.cart-item-actions {
-  @apply flex flex-col items-end gap-1 shrink-0;
-}
-.cart-item-prices {
-  @apply flex items-center gap-sm;
-}
-.cart-item-full-price {
-  @apply text-sm text-bark/70 line-through font-body;
-}
-.cart-item-unit-price {
-  @apply font-body font-semibold whitespace-nowrap;
-}
-.cart-item-line-total {
-  @apply font-body text-xs text-bark/70 m-0;
-}
-.cart-item-remove {
-  @apply text-sm bg-transparent border-none text-bark/60 font-body cursor-pointer underline;
-}
-
-/* --- Cart summary: discount + total rows ---
-   Subtotal uses the designer's .cart-subtotal contract class in global.css.
-   These rows appear only when priceSummary exposes a discount or a total
-   that differs from subtotal (see CartView.tsx extractSummary). */
-.cart-discount {
-  @apply flex items-baseline justify-between gap-sm font-body text-sm mt-sm;
-}
-.cart-discount-name {
-  @apply text-xs text-bark/60;
-}
-.cart-discount-amount {
-  @apply whitespace-nowrap;
-}
-.cart-total {
-  border-top: 1px solid var(--color-rule);
-  padding-top: var(--spacing-md);
-  margin-top: var(--spacing-sm);
-  font-family: var(--font-display);
-  font-size: 1.25rem;
-  font-weight: 500;
-  display: flex;
-  justify-content: space-between;
-  align-items: baseline;
-}
-
-/* Applied-discounts row — name-only (no amount) for cases where the API
-   reports a promo NAME via appliedDiscounts[].discountName but no cart-level
-   amount in priceSummary.discount (common for line-item automatic discounts
-   — the savings already show inline via fullPrice/price strikethrough). */
-.cart-applied-discounts {
-  @apply flex items-baseline justify-between gap-sm font-body text-sm mt-sm;
-}
-.cart-applied-discounts-name {
-  @apply text-right text-bark/80 italic;
-}

package/skills/wix-manage/references/events/list-events.md

@@ -1,203 +0,0 @@
----
-name: "List Events"
-description: Queries events from Wix Events using Events API. Covers field sets (DETAILS, URLS, REGISTRATION), filtering by status/date, and pagination.
----
-# List Events with Wix Events API
-
-This recipe demonstrates how to query and list events from Wix Events using the REST API.
-
-## Prerequisites
-
-- Wix Events app installed on the site
-- API access with events permissions
-
-## Required APIs
-
-- **Events API**: [REST](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/query-events)
-- **Filter and Sort Guidelines**: [Documentation](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/filter-and-sort)
-
----
-
-## Step 1: Verify Events App is Installed
-
-Before querying events, ensure Wix Events is installed on the site. If not, use the [Install Wix Apps](../app-installation/install-wix-apps.md) recipe to install it.
-
----
-
-## Step 2: Query Events
-
-**Endpoint**: `POST https://www.wixapis.com/events/v3/events/query`
-
-**Request Body**:
-```json
-{
-  "query": {
-    "paging": {
-      "limit": 10
-    }
-  },
-  "fields": ["DETAILS", "URLS"]
-}
-```
-
-**Request**:
-```bash
-curl -X POST \
-  'https://www.wixapis.com/events/v3/events/query' \
-  -H 'Authorization: <AUTH>' \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "query": {
-      "paging": {
-        "limit": 10
-      }
-    },
-    "fields": ["DETAILS", "URLS"]
-  }'
-```
-
-### Available Field Sets
-
-The `fields` parameter determines which data is returned. You MUST specify at least `"DETAILS"`.
-
-| Field Set | Description |
-|-----------|-------------|
-| `DETAILS` | Core event information (required) |
-| `URLS` | Event page URLs |
-| `CATEGORIES` | Event categories |
-| `AGENDA` | Event schedule/agenda |
-| `SEO_SETTINGS` | SEO metadata |
-| `REGISTRATION` | Registration settings |
-| `TEXTS` | Custom text content |
-| `FORM` | Registration form configuration |
-| `DASHBOARD` | Dashboard settings |
-| `FEED` | Social feed settings |
-| `ONLINE_CONFERENCING_SESSION` | Virtual event settings |
-
-### IMPORTANT NOTES:
-- I MUST specify at least `"DETAILS"` in the `fields` array
-- I MUST NEVER use `"FULL"` as a field value
-- If the user wants event links, I MUST include `"URLS"` in the fields
-- Follow the [Filter and Sort Guidelines](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/filter-and-sort) for query filtering
-
----
-
-## Step 3: Filter Events (Optional)
-
-Apply filters to narrow down results:
-
-**Filter by Status**:
-```json
-{
-  "query": {
-    "filter": {
-      "status": "UPCOMING"
-    },
-    "paging": {
-      "limit": 10
-    }
-  },
-  "fields": ["DETAILS"]
-}
-```
-
-> **Note:** Valid status values are: `UPCOMING`, `STARTED`, `ENDED`, `CANCELED`, `DRAFT`.
-
-**Filter by Date Range**:
-```json
-{
-  "query": {
-    "filter": {
-      "dateAndTimeSettings.startDate": {
-        "$gte": "2024-01-01T00:00:00Z",
-        "$lte": "2024-12-31T23:59:59Z"
-      }
-    },
-    "paging": {
-      "limit": 10
-    }
-  },
-  "fields": ["DETAILS"]
-}
-```
-
----
-
-## Response Structure
-
-```json
-{
-  "events": [
-    {
-      "id": "event-id-123",
-      "title": "Event Title",
-      "shortDescription": "Event description",
-      "status": "UPCOMING",
-      "dateAndTimeSettings": {
-        "startDate": "2024-06-15T10:00:00Z",
-        "endDate": "2024-06-15T18:00:00Z",
-        "timeZoneId": "America/New_York",
-        "dateAndTimeTbd": false,
-        "recurrenceStatus": "ONE_TIME"
-      },
-      "location": {
-        "type": "VENUE",
-        "address": {}
-      },
-      "slug": "event-slug"
-    }
-  ],
-  "pagingMetadata": {
-    "count": 10,
-    "hasNext": true
-  }
-}
-```
-
----
-
-## Common Use Cases
-
-### List Upcoming Events
-```json
-{
-  "query": {
-    "filter": {
-      "status": "UPCOMING",
-      "dateAndTimeSettings.startDate": {
-        "$gte": "2024-01-01T00:00:00Z"
-      }
-    },
-    "sort": [
-      {
-        "fieldName": "dateAndTimeSettings.startDate",
-        "order": "ASC"
-      }
-    ],
-    "paging": {
-      "limit": 20
-    }
-  },
-  "fields": ["DETAILS", "URLS"]
-}
-```
-
-### List Events with Registration Info
-```json
-{
-  "query": {
-    "paging": {
-      "limit": 10
-    }
-  },
-  "fields": ["DETAILS", "REGISTRATION", "FORM"]
-}
-```
-
----
-
-## Next Steps
-
-- Create events using the [Create Event API](https://dev.wix.com/docs/api-reference/business-solutions/events/event-management/events-v3/create-event)
-- Manage RSVPs and registrations
-- Configure event tickets and pricing