@wix/agent-skills 1.6.0 → 1.7.0

package/skills/wix-app/references/custom-element-widget/SETTINGS_PANEL.md

@@ -2,344 +2,33 @@
 
 This reference documents components and patterns specific to widget settings panels. For general WDS component documentation (FormField, Input, Dropdown, Checkbox, ToggleSwitch, DatePicker, Box, etc.), use the the `wix-design-system` skill.
 
-## Import
+## Layout
 
-```typescript
-import {
-  SidePanel,
-  FormField,
-  Input,
-  Dropdown,
-  Checkbox,
-  ToggleSwitch,
-  DatePicker,
-  TimeInput,
-  Box,
-  WixDesignSystemProvider,
-} from "@wix/design-system";
-import "@wix/design-system/styles.global.css";
-```
-
-## SidePanel Components
+The scaffolded `<name>.panel.tsx` already wraps everything in `SidePanel > Header > Content > Footer`. Wrap each `FormField` in `SidePanel.Field`. For component-level props (`SidePanel`, `SidePanel.Header`/`Content`/`Field`/`Footer`, `SectionHelper`), use the wix-design-system skill.
 
-### SidePanel
+## Color & Font Picker Fields
 
-Main container for the settings panel. Always wrap panel content in this component.
+Use the Wix Editor's native picker dialogs via `inputs.selectColor()` and `inputs.selectFont()` from `@wix/editor`. Both follow the same callback shape: `inputs.selectX(value, { onChange })`. Do NOT use `<input type="color">`, async/await, or a readOnly text Input — those don't integrate with the Editor picker dialogs.
 
-```typescript
-<SidePanel width="300" height="100vh">
-  <SidePanel.Header title="Widget Settings" />
-  <SidePanel.Content noPadding stretchVertically>
-    {/* Form fields */}
-  </SidePanel.Content>
-</SidePanel>
-```
+| Picker | API | Preview / trigger | Value type |
+|---|---|---|---|
+| Color | `inputs.selectColor(value, { onChange })` | `FillPreview` (WDS) | `string` (CSS color) |
+| Font | `inputs.selectFont(value, { onChange })` | `Button` (WDS) | `{ font: string; textDecoration: string }` |
 
-**Props:**
-
-- `width`: Panel width (default: "300")
-- `height`: Panel height (default: "100vh")
-
-### SidePanel.Header
-
-Header section with title.
+Wrap each picker in the standard `<SidePanel.Field><FormField label={label}>…</FormField></SidePanel.Field>`. The picker handlers themselves:
 
 ```typescript
-<SidePanel.Header title="Widget Settings" />
-```
-
-**Props:**
-
-- `title`: Header title text
-
-### SidePanel.Content
-
-Content area for form fields.
-
-```typescript
-<SidePanel.Content noPadding stretchVertically>
-  {/* Form content */}
-</SidePanel.Content>
-```
-
-**Props:**
-
-- `noPadding`: Remove default padding
-- `stretchVertically`: Stretch to fill available height
-
-### SidePanel.Field
-
-Wrapper for individual form fields. Use this to wrap each `FormField`.
-
-```typescript
-<SidePanel.Field>
-  <FormField label="Title">
-    <Input value={title} onChange={handleChange} />
-  </FormField>
-</SidePanel.Field>
-```
-
-## Widget API Integration Patterns
-
-### TimeInput with widget.setProp
-
-```typescript
-const parseTimeValue = (timeString: string): Date => {
-  const [hours, minutes] = timeString.split(':');
-  const date = new Date();
-  date.setHours(parseInt(hours, 10), parseInt(minutes, 10), 0, 0);
-  return date;
-};
-
-<TimeInput
-  value={parseTimeValue(targetTime)}
-  onChange={({ date }) => {
-    const hours = String(date.getHours()).padStart(2, '0');
-    const minutes = String(date.getMinutes()).padStart(2, '0');
-    const newTime = `${hours}:${minutes}`;
-    setTargetTime(newTime);
-    widget.setProp("target-time", newTime);
-  }}
+// Color
+<FillPreview
+  fill={value}
+  onClick={() => inputs.selectColor(value, { onChange: (val) => { if (val) onChange(val); } })}
 />
-```
-
-## Custom Components
-
-### ColorPickerField
-
-Custom component for color selection using `inputs.selectColor()` from `@wix/editor`. This opens the Wix color picker dialog with theme colors, gradients, and more — **NOT** a basic HTML `<input type="color">`.
-
-```typescript
-import React, { type FC } from 'react';
-import { inputs } from '@wix/editor';
-import { FormField, Box, FillPreview, SidePanel } from '@wix/design-system';
-
-interface ColorPickerFieldProps {
-  label: string;
-  value: string;
-  onChange: (value: string) => void;
-}
 
-export const ColorPickerField: FC<ColorPickerFieldProps> = ({
-  label,
-  value,
-  onChange,
-}) => (
-  <SidePanel.Field>
-    <FormField label={label}>
-      <Box width="30px" height="30px">
-        <FillPreview
-          fill={value}
-          onClick={() => inputs.selectColor(value, { onChange: (val) => { if (val) onChange(val); } })}
-        />
-      </Box>
-    </FormField>
-  </SidePanel.Field>
-);
+// Font
+<Button onClick={() => inputs.selectFont(value, {
+  onChange: (val) => onChange({ font: val.font, textDecoration: val.textDecoration || '' }),
+})}>
+  Change Font
+</Button>
 ```
 
-**Important:** Always use `inputs.selectColor()` from `@wix/editor` with the `FillPreview` WDS component. Do NOT use `<Input type="color">` — it produces a basic browser color picker that doesn't match the Wix Editor UX.
-
-### FontPickerField
-
-Custom component for font selection using `inputs.selectFont()` from `@wix/editor`. This opens the Wix font picker dialog with font family, size, bold, italic, and other typography features.
-
-```typescript
-import React, { type FC } from 'react';
-import { inputs } from '@wix/editor';
-import { FormField, Button, Text, SidePanel } from '@wix/design-system';
-
-interface FontValue {
-  font: string;
-  textDecoration: string;
-}
-
-interface FontPickerFieldProps {
-  label: string;
-  value: FontValue;
-  onChange: (value: FontValue) => void;
-}
-
-export const FontPickerField: FC<FontPickerFieldProps> = ({
-  label,
-  value,
-  onChange,
-}) => (
-  <SidePanel.Field>
-    <FormField label={label}>
-      <Button
-        size="small"
-        priority="secondary"
-        onClick={() => inputs.selectFont(value, { onChange: (val) => onChange({ font: val.font, textDecoration: val.textDecoration || "" }) })}
-        fullWidth
-      >
-        <Text size="small" ellipsis>Change Font</Text>
-      </Button>
-    </FormField>
-  </SidePanel.Field>
-);
-```
-
-**Important:** Always use `inputs.selectFont()` from `@wix/editor` with the callback pattern `inputs.selectFont(value, { onChange })`. Do NOT use an async/await pattern or a readOnly text Input — the callback pattern integrates directly with the Wix Editor font picker dialog.
-
-## Complete Example
-
-```typescript
-import React, { type FC, useState, useEffect, useCallback } from "react";
-import { widget } from "@wix/editor";
-import {
-  SidePanel,
-  WixDesignSystemProvider,
-  Input,
-  FormField,
-  TimeInput,
-  Box,
-} from "@wix/design-system";
-import "@wix/design-system/styles.global.css";
-import { ColorPickerField } from "./components/ColorPickerField";
-import { FontPickerField } from "./components/FontPickerField";
-import { parseTimeValue } from "./utils";
-
-const DEFAULT_BG_COLOR = "#0a0e27";
-const DEFAULT_TEXT_COLOR = "#00ff88";
-const DEFAULT_TEXT_FONT = "";
-const DEFAULT_TEXT_DECORATION = "";
-
-const Panel: FC = () => {
-  const [title, setTitle] = useState<string>("Countdown");
-  const [targetDate, setTargetDate] = useState<string>("");
-  const [targetTime, setTargetTime] = useState<string>("00:00");
-  const [bgColor, setBgColor] = useState<string>(DEFAULT_BG_COLOR);
-  const [textColor, setTextColor] = useState<string>(DEFAULT_TEXT_COLOR);
-  const [font, setFont] = useState({ font: DEFAULT_TEXT_FONT, textDecoration: DEFAULT_TEXT_DECORATION });
-
-  useEffect(() => {
-    Promise.all([
-      widget.getProp("title"),
-      widget.getProp("target-date"),
-      widget.getProp("target-time"),
-      widget.getProp("bg-color"),
-      widget.getProp("text-color"),
-      widget.getProp("font"),
-    ])
-      .then(([titleVal, dateVal, timeVal, bgColorVal, textColorVal, fontString]) => {
-        setTitle(titleVal || "Countdown");
-        setTargetDate(dateVal || "");
-        setTargetTime(timeVal || "00:00");
-        setBgColor(bgColorVal || DEFAULT_BG_COLOR);
-        setTextColor(textColorVal || DEFAULT_TEXT_COLOR);
-        setFont(JSON.parse(fontString || "{}"));
-      })
-      .catch((error) => console.error("Failed to fetch widget properties:", error));
-  }, []);
-
-  const handleTitleChange = useCallback((event: React.ChangeEvent<HTMLInputElement>) => {
-    const newTitle = event.target.value;
-    setTitle(newTitle);
-    widget.setProp("title", newTitle);
-  }, []);
-
-  const handleDateChange = useCallback((event: React.ChangeEvent<HTMLInputElement>) => {
-    const newDate = event.target.value;
-    setTargetDate(newDate);
-    widget.setProp("target-date", newDate);
-  }, []);
-
-  const handleTimeChange = useCallback(({ date }: { date: Date }) => {
-    if (date) {
-      const hours = String(date.getHours()).padStart(2, '0');
-      const minutes = String(date.getMinutes()).padStart(2, '0');
-      const newTime = `${hours}:${minutes}`;
-      setTargetTime(newTime);
-      widget.setProp("target-time", newTime);
-    }
-  }, []);
-
-  const handleBgColorChange = (value: string) => {
-    setBgColor(value);
-    widget.setProp("bg-color", value);
-  };
-
-  const handleTextColorChange = (value: string) => {
-    setTextColor(value);
-    widget.setProp("text-color", value);
-  };
-
-  const handleFontChange = (value: { font: string; textDecoration: string }) => {
-    setFont(value);
-    widget.setProp("font", JSON.stringify(value));
-  };
-
-  return (
-    <WixDesignSystemProvider>
-      <SidePanel width="300" height="100vh">
-        <SidePanel.Header title="Countdown Settings" />
-        <SidePanel.Content noPadding stretchVertically>
-          <Box direction="vertical" gap="24px">
-            <SidePanel.Field>
-              <FormField label="Title" required>
-                <Input
-                  type="text"
-                  value={title}
-                  onChange={handleTitleChange}
-                  placeholder="Enter countdown title"
-                />
-              </FormField>
-            </SidePanel.Field>
-
-            <SidePanel.Field>
-              <FormField label="Target Date" required>
-                <Input
-                  type="date"
-                  value={targetDate}
-                  onChange={handleDateChange}
-                />
-              </FormField>
-            </SidePanel.Field>
-
-            <SidePanel.Field>
-              <FormField label="Target Time" required>
-                <TimeInput
-                  value={parseTimeValue(targetTime)}
-                  onChange={handleTimeChange}
-                />
-              </FormField>
-            </SidePanel.Field>
-
-            <ColorPickerField
-              label="Background Color"
-              value={bgColor}
-              onChange={handleBgColorChange}
-            />
-
-            <ColorPickerField
-              label="Text Color"
-              value={textColor}
-              onChange={handleTextColorChange}
-            />
-
-            <FontPickerField
-              label="Text Font"
-              value={font}
-              onChange={handleFontChange}
-            />
-          </Box>
-        </SidePanel.Content>
-      </SidePanel>
-    </WixDesignSystemProvider>
-  );
-};
-
-export default Panel;
-```
-
-## Notes
-
-- Always import `@wix/design-system/styles.global.css` for proper styling
-- Use `SidePanel.Field` to wrap each `FormField`
-- Update both local state AND `widget.setProp()` in onChange handlers
-- Prop names in `widget.getProp()` and `widget.setProp()` use kebab-case
-- For color selection, use `inputs.selectColor()` from `@wix/editor` with `FillPreview` — do NOT use `<Input type="color">`
-- For font selection, use `inputs.selectFont()` from `@wix/editor` with a `Button` — do NOT use a text Input
-- Both `inputs.selectColor()` and `inputs.selectFont()` use the callback pattern: `inputs.selectColor(value, { onChange })` and `inputs.selectFont(value, { onChange })`
-- Font values are stored as JSON strings via `widget.setProp("font", JSON.stringify(value))` and parsed back with `JSON.parse()`

package/skills/wix-app/references/dashboard-menu-plugin/bookings-slots.md

@@ -44,15 +44,3 @@
 - **Use case:** Add custom payment options to the collect payment button menu.
 
 > **Note:** This slot also appears on the Wix eCommerce Order Page.
-
-### Booking List Page
-
-**Booking More Actions Menu — Slot ID:** `38fbe11f-6bc6-4df7-a742-e3e169a16cef`
-
-- **Dashboard path:** Booking Calendar > Booking List
-- **Use case:** Add actions for individual bookings.
-
-**Booking List Bulk Actions More Actions Menu — Slot ID:** `f1ab2ce9-a790-4e3e-a0f7-fae4da37a668`
-
-- **Dashboard path:** Booking Calendar > Booking List (when items are selected)
-- **Use case:** Add bulk actions for multiple selected bookings.

package/skills/wix-app/references/dashboard-menu-plugin/ecommerce-slots.md

@@ -15,3 +15,10 @@
 
 - **Dashboard path:** Sales > Orders
 - **Use case:** Add actions for individual orders in the orders list.
+
+### Edit Draft Order Page
+
+**Draft Order Fee — Slot ID:** `057f1726-f0b3-40ef-8903-1bd104e18369`
+
+- **Dashboard path:** Sales > Orders > Order > More Actions > Edit Order
+- **Use case:** Add a menu item to the edit-order screen — typically used to open a modal that adds or adjusts custom order fees.

package/skills/wix-app/references/dashboard-menu-plugin/restaurants-slots.md

@@ -7,21 +7,9 @@
 - **Dashboard path:** Table Reservations
 - **Use case:** Add global actions to the table reservations page's more actions menu.
 
-**Reservation Item More Actions Menu — Slot ID:** `f51f609d-950f-448a-a5e7-f01d31a7978d`
-
-- **Dashboard path:** Table Reservations
-- **Use case:** Add actions for individual reservations.
-
 ### Online Orders Page
 
 **Order Card More Actions Menu — Slot ID:** `d6b9230e-7388-4b5a-bb50-86afe3e344b2`
 
 - **Dashboard path:** Online Orders
 - **Use case:** Add actions for individual online orders.
-
-### Restaurant Menus Page
-
-**Menus Main More Actions Menu — Slot ID:** `e2a7ffb0-5e9c-4eda-bc0c-14724ff3e407`
-
-- **Dashboard path:** Restaurant Menus
-- **Use case:** Add global actions to the restaurant menus page's more actions menu.

package/skills/wix-app/references/dashboard-plugin/SLOTS.md

@@ -1,6 +1,8 @@
 # Dashboard Plugin Slots Reference
 
-Slots are UI placeholders on dashboard pages of Wix first-party business apps. Each slot has a unique ID used in the `extends` field of a dashboard plugin.
+Slots are UI placeholders on dashboard pages of Wix first-party business apps. Each slot has a unique ID passed as the `extendsSlotId` scaffold param (written as `extends` in the generated `.extension.ts` file).
+
+> **Authoritative slot list**: run `wix schema generate --type DASHBOARD_PLUGIN` for the live, complete `extendsSlotId` enum (each `anyOf` entry has the slot's human-readable title). This file documents per-slot parameters, dashboard paths, and use cases — content the schema does not carry.
 
 **Key behaviors:**
 - Some slots with the same ID appear on different pages. A plugin targeting such a slot is displayed on all pages containing it.
@@ -161,20 +163,6 @@ Slots are UI placeholders on dashboard pages of Wix first-party business apps. E
 
 > **Note:** This slot also appears on the Wix Bookings Calendar Page.
 
-### Edit Order Page — Additional Fees
-
-**Slot ID:** `057f1726-f0b3-40ef-8903-1bd104e18369`
-
-- **Dashboard path:** Sales > Orders > Order > More Actions > Edit Order
-- **Location:** Right side of page, in the "Order summary" card
-- **Parameters:**
-  | Name | Type | Description |
-  |------|------|-------------|
-  | `draftOrderId` | String | ID of the order being edited |
-  | `onDraftOrderUpdate()` | `() => Promise<void>` | Callback that notifies the host page about a draft order update, prompting a UI refresh |
-- **Multi-plugin:** Vertical, newest at bottom
-- **Use case:** Manage custom fees for orders — add or remove order fees according to custom business logic.
-
 ---
 
 ## Wix Events

package/skills/wix-app/references/service-plugin/ADDITIONAL-FEES.md

@@ -2,27 +2,11 @@
 
 ## Overview
 
-The Additional Fees SPI allows you to add custom fees to orders during checkout, such as handling fees, rush delivery charges, or global order fees.
-
-## Import
-
-```typescript
-import { additionalFees } from '@wix/ecom/service-plugins';
-```
-
-## Handler
-
-| Handler | Description |
-| --- | --- |
-| `calculateAdditionalFees` | Calculate and return additional fees to apply to the order |
+The Additional Fees SPI lets you add custom fees to orders during checkout (handling fees, rush delivery charges, global order fees, etc.). Implement the `calculateAdditionalFees` handler — it calculates and returns the fees to apply.
 
 ## Request and Response Schema
 
-Before implementing, call `ReadFullDocsMethodSchema` with the docs URL below to get the full request/response types.
-
-**MCP Tools to use:**
-- `ReadFullDocsMethodSchema` - Full request/response schema with field names, types, and descriptions
-- `ReadFullDocsArticle` - Full documentation with code examples (use if schema needs more context)
+Before implementing, call `ReadFullDocsMethodSchema` on the docs URL to get the full request/response types.
 
 | Handler | Docs URL |
 | --- | --- |

package/skills/wix-app/references/service-plugin/BOOKINGS-STAFF-SORTING.md

@@ -2,29 +2,13 @@
 
 ## Overview
 
-The Staff Sorting Provider SPI allows you to implement custom staff assignment algorithms for Wix Bookings. When a booking slot has multiple available staff members, Wix calls your plugin to determine the priority order for staff assignment.
+The Staff Sorting Provider SPI lets you implement custom staff assignment algorithms for Wix Bookings. When a booking slot has multiple available staff members, Wix calls your plugin to determine the priority order. Implement the `sortStaffMembers` handler — it returns the available staff members reordered by priority.
 
 **FQDN**: `wix.interfaces.resources.sorting.v1.staff_sorting_provider`
 
-## Import
-
-```typescript
-import { staffSorting } from "@wix/bookings/service-plugins";
-```
-
-## Handler
-
-| Handler | Description |
-| --- | --- |
-| `sortStaffMembers` | Sort available staff members by priority for a given booking slot |
-
 ## Request and Response Schema
 
-Before implementing, call `ReadFullDocsMethodSchema` with the docs URL below to get the full request/response types.
-
-**MCP Tools to use:**
-- `ReadFullDocsMethodSchema` - Full request/response schema with field names, types, and descriptions
-- `ReadFullDocsArticle` - Full documentation with code examples (use if schema needs more context)
+Before implementing, call `ReadFullDocsMethodSchema` on the docs URL to get the full request/response types.
 
 | Handler | Docs URL |
 | --- | --- |
@@ -85,30 +69,6 @@ staffSorting.provideHandlers({
 });
 ```
 
-## Extension Registration
-
-Register the staff sorting provider using the `bookingsStaffSortingProvider()` builder. This builder requires additional fields beyond the standard ones:
-
-```typescript
-import { extensions } from "@wix/astro/builders";
-
-export const staffSorting = extensions.bookingsStaffSortingProvider({
-  id: "{{GENERATE_UUID}}",
-  name: "Workload Balanced Staff Assignment",
-  source: "./backend/service-plugins/bookings-staff-sorting/workload-balancer/plugin.ts",
-  methodName: "Workload Balancer",
-  methodDescription: "Balances workload by prioritizing staff with fewer recent bookings",
-});
-```
-
-### Additional Builder Fields
-
-| Field | Type | Required | Max Length | Description |
-| --- | --- | --- | --- | --- |
-| `methodName` | string | Yes | - | Display name for the sorting method |
-| `methodDescription` | string | Yes | 100 chars | Description of the sorting algorithm (max 100 characters) |
-| `dashboardPluginId` | string | No | - | Optional dashboard plugin ID for configuration UI |
-
 ## Key Implementation Notes
 
 1. **Return all IDs** - You must return every ID from `availableResourceIds`, just reordered

package/skills/wix-app/references/service-plugin/DISCOUNT-TRIGGERS.md

@@ -4,12 +4,6 @@
 
 The Custom Triggers SPI allows you to define custom conditions that can trigger discounts in the Wix eCommerce system. You can create time-based triggers, product-based triggers, or any custom logic.
 
-## Import
-
-```typescript
-import { customTriggers } from "@wix/ecom/service-plugins";
-```
-
 ## Handlers
 
 | Handler | Description |
@@ -19,11 +13,7 @@ import { customTriggers } from "@wix/ecom/service-plugins";
 
 ## Request and Response Schema
 
-Before implementing, call `ReadFullDocsMethodSchema` with the docs URLs below to get the full request/response types.
-
-**MCP Tools to use:**
-- `ReadFullDocsMethodSchema` - Full request/response schema with field names, types, and descriptions
-- `ReadFullDocsArticle` - Full documentation with code examples (use if schema needs more context)
+Before implementing, call `ReadFullDocsMethodSchema` on each docs URL to get the full request/response types.
 
 | Handler | Docs URL |
 | --- | --- |

package/skills/wix-app/references/service-plugin/GIFT-CARDS.md

@@ -4,12 +4,6 @@
 
 The Gift Vouchers Provider SPI allows you to integrate external gift card or voucher systems with Wix eCommerce. This enables customers to redeem gift cards, check balances, and void transactions.
 
-## Import
-
-```typescript
-import { giftVouchersProvider } from '@wix/ecom/service-plugins';
-```
-
 ## Handlers
 
 | Handler | Description |
@@ -20,11 +14,7 @@ import { giftVouchersProvider } from '@wix/ecom/service-plugins';
 
 ## Request and Response Schema
 
-Before implementing, call `ReadFullDocsMethodSchema` with the docs URLs below to get the full request/response types.
-
-**MCP Tools to use:**
-- `ReadFullDocsMethodSchema` - Full request/response schema with field names, types, and descriptions
-- `ReadFullDocsArticle` - Full documentation with code examples (use if schema needs more context)
+Before implementing, call `ReadFullDocsMethodSchema` on each docs URL to get the full request/response types.
 
 | Handler | Docs URL |
 | --- | --- |

package/skills/wix-app/references/service-plugin/PAYMENT-SETTINGS.md

@@ -2,29 +2,11 @@
 
 ## Overview
 
-The Payment Settings SPI allows you to integrate custom payment settings with the Wix eCommerce payment process. This is called during payment processing (e.g., when a customer enters credit card details) and returns payment settings that Wix passes to the payment provider.
-
-A common use case is to enforce 3D Secure (3DS) payments for certain transactions based on custom business logic.
-
-## Import
-
-```typescript
-import { paymentSettings } from '@wix/ecom/service-plugins';
-```
-
-## Handler
-
-| Handler | Description |
-| --- | --- |
-| `getPaymentSettings` | Return payment settings to apply during the payment process |
+The Payment Settings SPI lets you integrate custom payment settings with the Wix eCommerce payment process. It's called during payment processing (e.g., when a customer enters credit card details) and returns settings that Wix passes to the payment provider. A common use case is enforcing 3D Secure (3DS) for certain transactions. Implement the `getPaymentSettings` handler.
 
 ## Request and Response Schema
 
-Before implementing, call `ReadFullDocsMethodSchema` with the docs URL below to get the full request/response types.
-
-**MCP Tools to use:**
-- `ReadFullDocsMethodSchema` - Full request/response schema with field names, types, and descriptions
-- `ReadFullDocsArticle` - Full documentation with code examples (use if schema needs more context)
+Before implementing, call `ReadFullDocsMethodSchema` on the docs URL to get the full request/response types.
 
 | Handler | Docs URL |
 | --- | --- |
@@ -113,23 +95,3 @@ paymentSettings.provideHandlers({
 5. **Fallback configuration** - Use the `fallbackValueForRequires3dSecure` builder field to set a default value if the SPI call fails (defaults to `false`)
 6. **Handle errors gracefully** - Return sensible defaults on error rather than throwing
 
-## Extension Registration
-
-Register the payment settings provider using the `ecomPaymentSettings()` builder. This builder accepts a special `fallbackValueForRequires3dSecure` field:
-
-```typescript
-import { extensions } from "@wix/astro/builders";
-
-export const paymentSettings = extensions.ecomPaymentSettings({
-  id: "{{GENERATE_UUID}}",
-  name: "Custom Payment Settings",
-  source: "./backend/service-plugins/ecom-payment-settings/my-payment-settings/plugin.ts",
-  fallbackValueForRequires3dSecure: false, // Default if SPI call fails
-});
-```
-
-### Additional Builder Fields
-
-| Field | Type | Required | Description |
-| --- | --- | --- | --- |
-| `fallbackValueForRequires3dSecure` | boolean | No | Default value for `requires3dSecure` if the SPI call fails (defaults to `false`) |

package/skills/wix-app/references/service-plugin/SHIPPING-RATES.md

@@ -2,28 +2,11 @@
 
 ## Overview
 
-The Shipping Rates SPI allows you to provide custom shipping options and calculate shipping costs based on order details, destination, weight, or any custom logic.
-
-## Import
-
-```typescript
-import { shippingRates } from "@wix/ecom/service-plugins";
-import { ChargeType } from "@wix/auto_sdk_ecom_shipping-rates";
-```
-
-## Handler
-
-| Handler | Description |
-| --- | --- |
-| `getShippingRates` | Calculate and return available shipping options with costs |
+The Shipping Rates SPI lets you provide custom shipping options and calculate shipping costs based on order details, destination, weight, or any custom logic. Implement the `getShippingRates` handler — it returns the available shipping options with their costs.
 
 ## Request and Response Schema
 
-Before implementing, call `ReadFullDocsMethodSchema` with the docs URL below to get the full request/response types.
-
-**MCP Tools to use:**
-- `ReadFullDocsMethodSchema` - Full request/response schema with field names, types, and descriptions
-- `ReadFullDocsArticle` - Full documentation with code examples (use if schema needs more context)
+Before implementing, call `ReadFullDocsMethodSchema` on the docs URL to get the full request/response types.
 
 | Handler | Docs URL |
 | --- | --- |