@wix/agent-skills 1.32.0 → 1.33.1

package/README.md

@@ -39,6 +39,16 @@ Install using [Gemini CLI](https://geminicli.com):
 gemini extensions install https://github.com/wix/skills
 ```
 
+### Antigravity Plugin
+
+In [Antigravity](https://antigravity.google), open **Customizations → Plugins**, click **+ Install from URL**, and enter `https://github.com/wix/skills/tree/main/antigravity/wix`. Or, from a terminal:
+
+```bash
+agy plugin install https://github.com/wix/skills/tree/main/antigravity/wix
+```
+
+The Wix MCP server signs you in to your Wix account the first time a Wix tool is used.
+
 ### Skills CLI
 
 Install using [skills CLI](https://github.com/vercel-labs/skills):
@@ -93,6 +103,17 @@ When a major bump is required (a breaking change in the underlying `wix-cli`), t
 
 Besides the npm package, skills are served as raw markdown / `.tgz` at `https://www.wix.com/skills/<name>` (also `dev.wix.com/skills`), directly from the `main` branch of `wix/skills` with no build step. Responses are cached, so a change reflects there within a few minutes of reaching that branch.
 
+## Privacy and telemetry
+
+Only `wix-replatform` collects telemetry. The other skills send nothing of their own; calls they make to Wix APIs and the Wix MCP are covered by the [Wix Privacy Policy](https://www.wix.com/about/privacy).
+
+During a migration run, `wix-replatform`:
+
+- **Sends run telemetry to Wix** (`https://frog.wix.com/migration-data-validator`): stage timings and outcomes, migrated record counts, errors and gaps by type (never record contents), the source platform and site URL, the destination site ID and the operator's Wix user ID. Turn it off with `RP_TELEMETRY_BI_DISABLED=1`.
+- **Reads the agent's Claude Code session transcripts** (`~/.claude/projects/`) at the end of the run, copies them compressed into the migration project's `telemetry/transcripts/` folder on your machine, and adds a summary (token cost, turn counts, tool failures, retry loops) to the run telemetry. The transcripts themselves stay local. Turn it off with `RP_TELEMETRY_TRANSCRIPT_DISABLED=1`.
+
+Set the variables in the environment the agent runs in. See [wix-replatform/README.md](wix-replatform/README.md).
+
 ## Contributing
 
 To report a problem with a skill or suggest a change, [open an issue](https://github.com/wix/skills/issues/new). Pull requests are not merged in this repository; accepted changes are made by the maintainers. See [CONTRIBUTING.md](CONTRIBUTING.md) for what makes a useful report.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/agent-skills",
-  "version": "1.32.0",
+  "version": "1.33.1",
   "description": "Wix Skills for AI coding agents — versioned npm distribution of the wix/skills content.",
   "license": "MIT",
   "repository": {
@@ -12,7 +12,7 @@
     "url": "https://github.com/wix/skills/issues"
   },
   "scripts": {
-    "version": "node .github/scripts/sync-plugin-versions.mjs && git add .claude-plugin/plugin.json .codex-plugin/plugin.json .cursor-plugin/plugin.json plugin.json gemini-extension.json skills/wix-headless-kit/install/pins.json"
+    "version": "node .github/scripts/sync-plugin-versions.mjs && git add .claude-plugin/plugin.json .codex-plugin/plugin.json .cursor-plugin/plugin.json plugin.json gemini-extension.json antigravity/wix/plugin.json skills/wix-headless-kit/install/pins.json"
   },
   "files": [
     "skills/**",

package/skills/wix-app/references/DASHBOARD_PAGE.md

@@ -33,7 +33,7 @@ The CLI generates the folder, the page's component file (`<page>.tsx`, the build
 
 **After scaffolding, check `routePath`:** use `support-tickets`, not `/support-tickets`; a leading slash fails registration even if the build passes. Internal router paths stay `/`, `/:id`, `/new`, never prefixed with `<route>` — see `<pkgRoot>/dist/docs/Collection to Entity Flow.md`.
 
-**Before writing that UI:** copy in the installed `@wix/patterns` page template that matches, per [DRAFT_TEMPLATE.md](dashboard-page/DRAFT_TEMPLATE.md) — don't compose the shell from scratch.
+**Before writing UI:** copy the [template](dashboard-page/DRAFT_TEMPLATE.md). Make sure `WixPatternsProvider` remains at the extension root, inside `BusinessManagerTheme` and above all components calling Patterns hooks.
 
 **Then, for whatever the template doesn't cover:** list every patterns name you'll add, and resolve them all in one `node <pkgRoot>/bin/patterns-lookup.cjs <name…>` call ([WIX_PATTERNS_DOCS.md § 1](WIX_PATTERNS_DOCS.md#1--the-index)). Its import, examples and props file decide whether you open anything else. Each Bash call is a fresh shell — re-set the path variable every time.
 

package/skills/wix-app/references/EDITOR_REACT_COMPONENT.md

@@ -19,6 +19,24 @@ Keep the Wix CLI scaffold and file roles:
 
 Supplementary files are allowed; keep scaffold roles intact.
 
+## Required Reading (blocking)
+
+Before writing code, open and read in full every reference in the matching
+row. An unopened one is a failed run. Open paths directly; never skim or
+grep instead.
+
+| Scope | Required references |
+| --- | --- |
+| Creating a component | [`REACT-GUIDELINES.md`](editor-react-component/REACT-GUIDELINES.md), [`COMPONENT-CONTRACT.md`](editor-react-component/COMPONENT-CONTRACT.md), [`PARTS.md`](editor-react-component/PARTS.md), [`PROPS-VS-CSS.md`](editor-react-component/PROPS-VS-CSS.md), [`CSS-GUIDELINES.md`](editor-react-component/CSS-GUIDELINES.md), [`DIRECTIONALITY.md`](editor-react-component/DIRECTIONALITY.md), [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md), [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md), [`EDITOR-EXTENSION-CONFIGURATION.md`](editor-react-component/EDITOR-EXTENSION-CONFIGURATION.md), [`OVERFLOW.md`](editor-react-component/OVERFLOW.md) |
+| Editing React or JSX | [`REACT-GUIDELINES.md`](editor-react-component/REACT-GUIDELINES.md), [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md) |
+| Changing public contract, semantic root, or named parts | [`COMPONENT-CONTRACT.md`](editor-react-component/COMPONENT-CONTRACT.md), [`PARTS.md`](editor-react-component/PARTS.md), [`PROPS-VS-CSS.md`](editor-react-component/PROPS-VS-CSS.md) |
+| Changing public data props or elected root global class | [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md) |
+| Item array where only one body is visible | [`COMPONENT-CONTRACT.md`](editor-react-component/COMPONENT-CONTRACT.md), [`PROPS-VS-CSS.md`](editor-react-component/PROPS-VS-CSS.md), [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md), [`DESIGN-STATES.md`](editor-react-component/DESIGN-STATES.md) |
+| Creating or changing CSS | [`CSS-GUIDELINES.md`](editor-react-component/CSS-GUIDELINES.md) |
+| Creating or changing layout/content | [`OVERFLOW.md`](editor-react-component/OVERFLOW.md) |
+| Root direction contract, direction-sensitive behavior, or `ReactNode` slot | [`DIRECTIONALITY.md`](editor-react-component/DIRECTIONALITY.md) |
+| Sizing, installation, or manifest overrides | [`EDITOR-EXTENSION-CONFIGURATION.md`](editor-react-component/EDITOR-EXTENSION-CONFIGURATION.md) |
+
 ## Workflow
 
 1. **Scaffold only when creating.** Run in the Wix app (`wix.config.json`).
@@ -31,9 +49,9 @@ Supplementary files are allowed; keep scaffold roles intact.
    Never rerun the scaffold for an existing component.
    Write a meaningful `description` in 1-2 plain sentences (max 300 chars): what
    the user sees, when to use it, and capabilities that affect that choice.
-   Don't repeat the component name or add implementation details.
+   Don't repeat the name or add implementation details.
 
-2. **Run the dependency preflight.** Check required packages:
+2. **Run the dependency preflight.**
 
    ```bash
    deps=(@wix/react-component-schema @wix/react-component-utils @wix/editor-react-types)
@@ -56,16 +74,15 @@ Supplementary files are allowed; keep scaffold roles intact.
    }
    ```
 
-3. **Plan.** Identify props, root, parts, and states; read routed references.
-   Use the scaffold and references before inspecting package declarations.
-   Inspect only needed declarations resolved by the app for undocumented APIs
-   or fields, or typecheck failures. They govern API shapes; retain editor rules.
+3. **Plan.** Identify props, root, parts, and states; open all required references first.
+   Use them and the scaffold before inspecting package declarations; inspect
+   only for undocumented APIs or fields, or typecheck failures. Declarations
+   govern API shapes; retain editor rules.
 
 4. **Implement.** Keep props, logic, and styles in their scaffolded editable
-   files. Format edited source files with the app's configured formatter before
-   checking formatting. Never edit or format `*.generated.ts`.
+   files. Format edited source files with the app's formatter. Never edit or format `*.generated.ts`.
 
-5. **Run the accessibility review.** Once the JSX is complete, run from the
+5. **Run the accessibility review (mandatory).** Once the JSX is complete, run from the
    same folder (`<SKILL_ROOT>` is the directory containing the active `SKILL.md`):
 
    ```bash
@@ -89,43 +106,30 @@ Supplementary files are allowed; keep scaffold roles intact.
    ```
 
    Run `npx tsc --noEmit`, relevant tests/lint, and the accessibility review.
-   If later edits affect a check, rerun that
-   check. Inspect the manifest when generated; never hand-repair it. Diagnose
-   failures with
+   If later edits affect a check, rerun that check. Inspect the manifest when generated; never hand-repair it.
+   Diagnose failures with
    [`editor-react-component/MANIFEST-ERRORS.md`](editor-react-component/MANIFEST-ERRORS.md).
 
    For creation/layout changes, complete the routed overflow resize review.
 
-8. **Report.** Summarize files, checks, blockers, and checks that could not run.
+8. **Report.** Summarize files, checks, blockers, unrun checks.
+   List required references as read/unread; read any unread one and fix first.
 
 ## Reference Policy
 
-Read only matched references. Preserve unrelated behavior. `SKILL.md` routes;
-references are leaves.
-
-### Required References
-
-| Scope | Required references |
-| --- | --- |
-| Creating a component | [`REACT-GUIDELINES.md`](editor-react-component/REACT-GUIDELINES.md), [`COMPONENT-CONTRACT.md`](editor-react-component/COMPONENT-CONTRACT.md), [`PARTS.md`](editor-react-component/PARTS.md), [`PROPS-VS-CSS.md`](editor-react-component/PROPS-VS-CSS.md), [`CSS-GUIDELINES.md`](editor-react-component/CSS-GUIDELINES.md), [`DIRECTIONALITY.md`](editor-react-component/DIRECTIONALITY.md), [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md), [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md), [`EDITOR-EXTENSION-CONFIGURATION.md`](editor-react-component/EDITOR-EXTENSION-CONFIGURATION.md) |
-| Editing React or JSX | [`REACT-GUIDELINES.md`](editor-react-component/REACT-GUIDELINES.md), [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md) |
-| Changing public contract, semantic root, or named parts | [`COMPONENT-CONTRACT.md`](editor-react-component/COMPONENT-CONTRACT.md), [`PARTS.md`](editor-react-component/PARTS.md), [`PROPS-VS-CSS.md`](editor-react-component/PROPS-VS-CSS.md) |
-| Changing public data props or elected root global class | [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md) |
-| Item array where only one body is visible | [`COMPONENT-CONTRACT.md`](editor-react-component/COMPONENT-CONTRACT.md), [`PROPS-VS-CSS.md`](editor-react-component/PROPS-VS-CSS.md), [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md), [`DESIGN-STATES.md`](editor-react-component/DESIGN-STATES.md) |
-| Creating or changing CSS | [`CSS-GUIDELINES.md`](editor-react-component/CSS-GUIDELINES.md) |
-| Creating or changing layout/content | [`OVERFLOW.md`](editor-react-component/OVERFLOW.md) |
-| Root direction contract, direction-sensitive behavior, or `ReactNode` slot | [`DIRECTIONALITY.md`](editor-react-component/DIRECTIONALITY.md) |
-| Sizing, installation, or manifest overrides | [`EDITOR-EXTENSION-CONFIGURATION.md`](editor-react-component/EDITOR-EXTENSION-CONFIGURATION.md) |
+Read every required reference for the matched scope, optional ones only on
+trigger. Preserve unrelated behavior. References are leaves.
 
 ### Optional References
 
 | Trigger | Read |
 | --- | --- |
 | Interactive/selectable part, custom state, or open/reveal toggle | [`DESIGN-STATES.md`](editor-react-component/DESIGN-STATES.md) |
+| Disabled or invalid state | [`DISABLED-INVALID.md`](editor-react-component/DISABLED-INVALID.md) |
 | Creating interactive components or changing interactions/callbacks | [`FUNCTION-HANDLERS.md`](editor-react-component/FUNCTION-HANDLERS.md) |
 | Browser APIs, effects, or time-dependent output | [`SSR.md`](editor-react-component/SSR.md) |
 | Non-established CSS feature or DOM API, or user asks for one by name | [`BROWSER-SUPPORT.md`](editor-react-component/BROWSER-SUPPORT.md) |
-| `npx wix build` or manifest generation exits with an error | [`MANIFEST-ERRORS.md`](editor-react-component/MANIFEST-ERRORS.md) |
+| `npx wix build` or manifest generation errors or warns | [`MANIFEST-ERRORS.md`](editor-react-component/MANIFEST-ERRORS.md) |
 | Animation, video, carousel, or other playable/looped/autoplaying content | [`ANIMATED-COMPONENTS.md`](editor-react-component/ANIMATED-COMPONENTS.md), [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md) |
 | Site/runtime/editor context hooks needed | [`SITE-CONTEXT-HOOKS.md`](editor-react-component/SITE-CONTEXT-HOOKS.md) (+ [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md) when design-mode behavior differs) |
 | Branded, themed, or brand-aware component requested | [`BRANDED-COMPONENTS.md`](editor-react-component/BRANDED-COMPONENTS.md) |
@@ -137,9 +141,7 @@ references are leaves.
 - Elected root: `dir={direction}`, fallback-direction class, logical CSS for
   direction-sensitive layout.
 - Deterministic render; no browser globals during render.
-- Explicit foreground colors need a known contrasting background; transparent
-  roots inherit from the host.
-- Baseline Widely Available CSS/DOM only, or supported fallbacks.
+- Baseline Widely Available CSS/DOM only, or fallbacks.
 - Accessibility per part, per [`ACCESSIBILITY.md`](editor-react-component/ACCESSIBILITY.md):
   read only `a11y.ariaLabel`, and only for a control without a visible name;
   never spread the `a11y` object or add one-off ARIA props.
@@ -149,17 +151,14 @@ references are leaves.
 - Native design states: interactive elements only, never a non-interactive root
   or part; pair selectors with injected modifiers; toggle custom state classes
   from data, each with a matching `:global()` rule.
-- Open/close/reveal (click/hover/focus): props-only root
+- Open/close/reveal: props-only root
   `isOpen: ElementState<boolean>` synced to state; module classes, no `--open` class.
 - Single-visible-body arrays: `name` per item, `ActiveItemIndex<'prop'>`, render
   all bodies, hide inactive accessibly.
 - No arrays inside array items; keep group fields flat (no object props).
 - Autoplay/loop: play/pause control, honor reduced motion, suppress autoplay in
   editor design mode.
-- Resizable layout: keep required content usable at 320px. Reflow visible
-  groups inside their page and cap track minima with
-  `minmax(min(100%, <minimum>), 1fr)`. Follow [`OVERFLOW.md`](editor-react-component/OVERFLOW.md).
-- Preview composition, inline or through variables:
-  `withDefaults(withFallbackPlaceholder(PreviewOrComponent, options), defaultProps)`.
-  Keep `withDefaults` outermost; use one crucial data field and match the root
-  class.
+- Resizable layout: keep required content usable at 320px, per
+  [`OVERFLOW.md`](editor-react-component/OVERFLOW.md).
+- Preview: `withDefaults` outermost, one crucial data field, matching root
+  class, per [`COMPONENT-PREVIEW.md`](editor-react-component/COMPONENT-PREVIEW.md).

package/skills/wix-app/references/editor-react-component/ANIMATED-COMPONENTS.md

@@ -64,19 +64,24 @@ export interface MyAnimationProps {
   direction?: Direction;
   a11y?: A11y;
 
-  /** Start playing on load. Default `true`. */
+  /** Start playing on load. */
   autoPlay?: boolean;
 
-  /** Repeat when finished. Default `true`. */
+  /** Repeat when finished. */
   loop?: boolean;
 
-  /** Show play/pause button. Default `'showOnHover'`. */
   pauseButtonVisibility?: 'showAlways' | 'showOnHover';
 
   elementProps?: {
     myAnimationPlayButton?: { className?: string };
   };
 }
+
+export const defaultProps = {
+  autoPlay: true,
+  loop: true,
+  pauseButtonVisibility: 'showAlways',
+} as const;
 ```
 
 Omit `loop` when repeat is unsupported.
@@ -183,7 +188,7 @@ Set the visibility data attribute on the existing elected root, preserving its
 full root contract:
 
 ```tsx
-data-pause-button-visibility={pauseButtonVisibility ?? 'showOnHover'}
+data-pause-button-visibility={pauseButtonVisibility}
 ```
 
 Wire the named part completely:
@@ -210,7 +215,7 @@ Wire the named part completely:
 /* Narrow behavior-only exception documented in CSS-GUIDELINES.md. Keep editable
    appearance on .playButton and use this relationship only for visibility. */
 
-/* showOnHover (default) */
+/* showOnHover */
 .root[data-pause-button-visibility="showOnHover"] .playButton {
   opacity: 0;
   pointer-events: none;
@@ -222,7 +227,7 @@ Wire the named part completely:
   pointer-events: auto;
 }
 
-/* showAlways — no extra CSS needed; button is visible by default */
+/* showAlways (default) — no extra CSS needed; button is visible by default */
 ```
 
 ## 4. Suppress Autoplay in `component.preview.tsx`

package/skills/wix-app/references/editor-react-component/DESIGN-STATES.md

@@ -23,7 +23,8 @@ in the component's `.tsx` and `.module.css`.
 | Interactive — `button`/`a`/`input`/`select`/`textarea`/`summary`, an interactive `role`, or an interactive handler (`onClick`/`onMouseEnter`/`onFocus`/…) | `hover` |
 | Input field — `select`/`textarea`; `input` except `hidden`/`button`/`submit`/`reset`/`image`; or an input-widget `role` (`checkbox`/`radio`/`switch`/`slider`/`spinbutton`/`textbox`/`searchbox`/`combobox`/`listbox`) | `focus` |
 | Other interactive element whose editable focus appearance the user explicitly requests | `focus` |
-| Disableable — `button`/`input`/`select`/`textarea`/`fieldset` or a disableable role | `disabled` (+ `invalid` for `input`/`select`/`textarea`) |
+| `button`/`input`/`select`/`textarea`/`fieldset` when asked or its action can be unavailable | `disabled` |
+| `input`/`select`/`textarea` with a constraint or `setCustomValidity`; a `form`/`fieldset` with one | `invalid` |
 | Has a selectable/variant value in its data — `selected`/`active`/`current`/`checked`/`featured` | that custom state |
 | Whole component opens/collapses or reveals content (expandable panel, disclosure, dropdown, drawer, popup, tooltip) on click, hover or focus | root `isOpen` state, no part `open` state (§6) |
 | None of the above, incl. a non-interactive root or part | no states, and no `:hover`/`:active`/`:focus` rules, even decorative; resting style only |
@@ -110,8 +111,6 @@ The local static accessibility scan cannot measure rendered color contrast.
   spread alone suffices (it merges `className` itself). The key is the global
   class in camelCase (`COMPONENT-CONTRACT.md`).
 
-Wire native and custom states as follows:
-
 ```tsx
 <button
   type="button"

package/skills/wix-app/references/editor-react-component/DISABLED-INVALID.md

@@ -0,0 +1,31 @@
+# Disabled and Invalid Wiring
+
+Use after DESIGN-STATES.md §1 decides a part exposes `disabled` or `invalid`. A
+native element's `:disabled` or `:invalid`, paired with the `:global` modifier in
+the §3 rule, is what generates the state.
+
+## Disabled
+
+Author it when asked, or when the control stays visible but its action can be
+unavailable (unmet precondition, request in progress, sold out). Otherwise author
+no `disabled` binding and no `--disabled` rule.
+
+## Invalid
+
+Author it only for a native field with a constraint (`required`, `pattern`,
+`type="email"`, …) or a `setCustomValidity` message. An unconstrained field is
+never invalid.
+
+For validity from outside the field (a server check, a password confirmation),
+call `setCustomValidity` in the component file, on the field itself: through a
+ref bound with `ref={confirmRef}`, a callback ref, or `event.currentTarget` in an
+`on*` handler (inline, or a function of the component passed by name). The field may be in a component of the same file
+that renders it. Not from a custom hook, a function outside the component, or
+another file, and not through a ref given to a custom component. A field in a loop
+or rendered conditionally is detected when every field with that `ref` or handler
+prop calls it. If only some do, the ones that do may not be detected: give them a
+constraint prop instead, otherwise leave `invalid` off them.
+
+A `form` or `fieldset` is invalid when a field inside it is
+(`.form:global(.signup-form--invalid), .form:invalid`), with no constraint of its
+own; with no constrained field it is never invalid.

package/skills/wix-app/references/editor-react-component/MANIFEST-ERRORS.md

@@ -1,7 +1,7 @@
 # Manifest Build Errors
 
 Use this reference only when `npx wix build` or `npx wix generate manifest`
-exits with an error. Read the error name from the first token before the colon
+exits with an error or prints a warning. For an error, read the error name from the first token before the colon
 (`IoError:`, `ParseError:`, or `NotFoundError:`), then apply the matching fix.
 
 | Error | Fix |
@@ -20,6 +20,19 @@ exits with an error. Read the error name from the first token before the colon
 
 After each fix, re-run `npx wix build && npx wix generate manifest` to confirm.
 
+## Warnings
+
+The build can also print non-fatal warnings such as
+`[css] … styles selectors that matched no element in the extraction render`.
+Read every warning and fix it; this is mandatory, with one exception below.
+
+- **A part's own class** (`.errorMessage`, `.item`) means the part is not
+  mounted in the extraction render. Keep it mounted per `PARTS.md`, then
+  re-run build and manifest generation.
+- **A class applied only by state** (`.contentOpen` from `open && styles.contentOpen`)
+  is expected: the part is mounted and only the state look is absent. Leave the
+  markup and CSS unchanged; do not force the state on or remove the styling.
+
 ## Checklist
 
 - [ ] The fix matches the reported error name and message.

package/skills/wix-app/references/editor-react-component/PARTS.md

@@ -46,9 +46,38 @@ Apply this filter to every candidate:
   share the same semantic editor surface. Distinguish position with data or a
   module-only helper class, not separate part names.
 
-The manifest generator can silently omit a named part behind conditional JSX.
-Keep an editor-controlled part mounted in the render it inspects. Hide it with
-CSS driven by a data attribute, or disable it when it should remain visible.
+## Keep Every Part Mounted
+
+The manifest is generated from a single server-side render of the component
+with mock props. Effects do not run and `useState` keeps its initial value, so
+markup that is not mounted in that render, and the CSS that styles it, never
+reaches the manifest. The source is not changed afterwards: write it so every
+part is mounted regardless of state.
+
+- Mount every phase (loading, error, empty, question, result) and hide the
+  inactive ones with the `hidden` attribute. Never write
+  `phase === 'x' && <Part />`. Give a `hidden` element no author `display`
+  rule: it would override `hidden`.
+- While data is missing, render one static placeholder item inside a hidden
+  wrapper so the item parts exist. It is never visible.
+- Mutually exclusive messages (loading, error, empty) are one part whose text
+  switches by phase, not several parts with the same name.
+- A modifier toggled by state (`correct`, `incorrect`) is a design state; see
+  `DESIGN-STATES.md`.
+
+```tsx
+const item = current ?? placeholderItem; // placeholder shows only while hidden
+
+<div hidden={phase !== 'question'}>
+  <h3
+    {...elementProps?.quizQuestion}
+    className={classNames('quiz-question', styles.question, elementProps?.quizQuestion?.className)}
+  >
+    {item.question}
+  </h3>
+</div>
+```
+
 After generating the manifest, confirm that its `elements` include every
 intended named part and that each `elementProps.<key>` read in code equals the
 camelCase of that part's global class.

package/skills/wix-app/references/editor-react-component/SSR.md

@@ -29,9 +29,11 @@ const items = buildItems(props.items);
 return <ul>{items.map(renderItem)}</ul>;
 ```
 
-This does not require every data branch to render simultaneously. Empty,
-loading, and error states may be conditional when their initial value is stable
-and the same on server and client.
+This does not require every data branch to render simultaneously: loading,
+empty, and error states may be conditional when their initial value is stable
+and the same on server and client. A branch that contains a named part must
+still be mounted in the first render, or the manifest omits that part (see
+`PARTS.md`).
 
 ## Deterministic Output
 
@@ -47,4 +49,5 @@ format, or a client-only enhancement that does not replace the initial markup.
 
 - [ ] No browser globals are accessed at module scope or during render.
 - [ ] Initial server/client markup is complete and identical.
+- [ ] Every named part is mounted in the first render.
 - [ ] Render output does not depend on random, clock, locale, or timezone state.

package/skills/wix-headless-kit/install/pins.json

@@ -3,6 +3,6 @@
   "@wix/create-new": "0.0.124",
   "typescript": "5.8.3",
   "templates": {
-    "ref": "v1.32.0"
+    "ref": "v1.33.1"
   }
 }

package/skills/wix-manage/SKILL.md

@@ -36,8 +36,8 @@ Lists all apps installed on a site using Apps Installer API. Useful for verifyin
 
 ## Custom Apps
 
-### [Use App Skills and App Tools](references/custom-apps/use-app-skills-and-app-tools.md)
-"Discovers and runs what the apps installed on a Wix site add for AI agents: app skills, which are an app's instructions for a task (for example pricing a product for customers in another country, or checking a property listing before it is published), and app tools, which are actions and lookups an app exposes. Use every time a site has custom apps installed, before acting on the user's request: knowing which apps are installed doesn't tell what they can do, so only this skill's discovery calls show whether one of them handles the request. Also use when the user asks for something an installed app provides rather than a built-in Wix feature, asks what their apps can do, or names an app, skill or tool. Covers reading a chosen skill's instructions and running the app tools it allows, or running a single app tool directly."
+### [Use App Tools](references/custom-apps/use-app-tools.md)
+"Discovers and runs app tools, the actions and lookups that apps installed on a Wix site expose to AI agents, for example converting a price with a pricing app or tracking a package with a shipping app. Covers listing the site's app tools, choosing one by its description, and running it with a payload built from its input schema. Use when the user asks for something an installed app provides rather than a built-in Wix feature, asks what their apps can do, or names an app or app tool."
 
 ---
 
@@ -237,10 +237,16 @@ Routes discounts, coupons, sales and bundles to promotion recipes, and visual pr
 ## Events
 
 ### [Create an Event with the Wix Events API](references/events/create-wix-event.md)
-"Creates an event with the Wix Events V3 API — the required request body, ISO-8601 date and time settings, venue/online/TBD location, RSVP vs ticketed registration, guest capacity, short vs rich-text descriptions, ticket tiers and pricing, and recurring series. Covers the exact field shapes and the API's misleading validation messages. Use when the user wants to create an event, set its date, location, description, guest limit or ticket prices, or set up a repeating event."
+"Creates an event with the Wix Events V3 API — one-off or recurring, RSVP, ticketed, registration-free or with external registration — including date and time, venue or online location, guest limit, description and ticket tiers. Covers the exact field shapes and the API's misleading validation messages. Use when the user wants to create or set up an event, an information-only event, or a repeating event — including a weekly workshop, class or meetup series held on set dates at a venue or online; a Bookings class or course is booked per session instead."
 
 ### [Manage Wix Events — Publishing, Cancelling, Cloning and Counting](references/events/manage-wix-events.md)
-"Operates on events that already exist with the Wix Events V3 API — finding an event by title, publishing a draft, cancelling, deleting (one or by filter), cloning, updating an event's date or details, and counting events. Use when the user wants to find, publish or cancel an event, duplicate one, move an event's date, delete events in bulk, or count their events. Creating an event, its tickets or a recurring series is a separate recipe."
+"Operates on Wix events that already exist with the Wix Events V3 API — finding, updating (date, venue, details, page settings), controlling registration (close, reopen, registration-free, external, members-only, limits), switching between RSVP and ticketed (a new event — ask before creating it), publishing, cancelling, deleting, cloning and counting, including single occurrences of a recurring event. Use to close registration, move or cancel an event, or change how guests register."
+
+### [Manage Event Tickets](references/events/manage-event-tickets.md)
+"Manages the ticket types of a ticketed Wix event with the Ticket Definitions V3 API — adding, editing, repricing, hiding, reordering and deleting tickets, scheduling or ending ticket sales, and changing the ticket currency. Use when the user wants to add early-bird, VIP, child or donation tickets to an existing event, change a ticket's price or quantity, or set when tickets stop selling."
+
+### [Manage Event Guests](references/events/manage-event-guests.md)
+"Manages the people registered for a Wix event — RSVPs on RSVP events, and orders, tickets and ticket holders on ticketed events: listing and counting guests, adding or removing a guest, changing an RSVP, checking guests in, and marking orders paid. Use when the user asks who is coming or how many registered, or wants to add, remove or check in a guest. Notes what the API can't do, such as refunds and resending emails."
 
 ---
 
@@ -455,7 +461,7 @@ Query and list products from a Wix Store using the Catalog V1 Query Products end
 Manages pre-order settings for product variants using V3 Inventory API. Covers enabling/disabling pre-orders, setting messages, configuring limits, and handling trackQuantity requirements.
 
 ### [Update Product with Options (Catalog V3)](references/stores/update-product-with-options.md)
-Start here for existing Catalog V3 product updates, including digital products that fail at add-to-cart with ITEM_NOT_FOUND_IN_CATALOG. Includes name lookup, Get Product, and PATCH in one flow, plus importing a supplied PDF and attaching it to the existing variant. Covers options, variant prices and SKUs, product visibility (hide/unhide through `visible`, never delete), description edits that preserve Rich Content, and revision-based updates. Read another recipe only for a field or operation this flow does not cover.
+Start here for existing Catalog V3 product updates, including digital products that fail at add-to-cart with ITEM_NOT_FOUND_IN_CATALOG. Includes name lookup, Get Product, and PATCH in one flow, plus importing a supplied PDF and attaching it to the existing variant. Covers options, variant prices and SKUs, variant shipping weight in the site's weight unit, product visibility (hide/unhide through `visible`, never delete), description edits that preserve Rich Content, and revision-based updates. Read another recipe only for a field or operation this flow does not cover.
 
 ### [Stores Dashboard Navigation](references/stores/stores-dashboard-navigation.md)
 "Builds direct links to Wix Stores and eCommerce dashboard pages on manage.wix.com — products list, edit a specific product, categories, inventory, orders list, a specific order, abandoned checkouts, gift cards, shipping and tax settings. Pairs each main Stores/eCommerce entity with its read API so you can fetch an entity and hand back a 'view it in your dashboard' link. Use when the user asks where something is in the Wix dashboard, wants a direct link to a dashboard page, or you need a dashboard URL to include with the result of an API operation."
@@ -464,7 +470,7 @@ Start here for existing Catalog V3 product updates, including digital products t
 ## Automations
 
 ### [Build and Manage Wix Automations](references/automations/build-and-manage-automations.md)
-Inspect Wix automations and their on/off status, create linear automations from the site’s installed triggers and actions, and turn automations on or off on request.
+Create, update, activate or deactivate Wix Automations with app actions, trigger filters, conditions, delays, variables, branches and schedules, and check their current status, using the public Wix Automations APIs.
 
 <details>
 <summary>Internal skills (loaded on demand by Build and Manage Wix Automations — do NOT use directly)</summary>
@@ -484,8 +490,20 @@ Inspect Wix automations and their on/off status, create linear automations from
 - [Automations Mapping Expressions](references/automations/bracket-expressions.md)
   Write builder-compatible automation mapping expressions, literals and data references.
 
+- [Automations Conditions](references/automations/conditions.md)
+  Configure visual and code conditions while preserving boolean intent, comparison boundaries and builder editability.
+
+- [Automations Delays Variables and Branches](references/automations/special-actions.md)
+  Configure delay, rate-limit, variable and parallel-branch steps, preserving supported existing step metadata.
+
+- [Automations Schemas and Scheduling](references/automations/schemas-and-scheduling.md)
+  Configure dynamic schemas and scheduled automation triggers with correct timezone and calendar behavior.
+
+- [Automations Validation and Persistence](references/automations/validation-and-verification.md)
+  Validate automation configuration, check builder compatibility, persist changes and verify the saved result.
+
 - [Automations Activation Status](references/automations/activation-status.md)
-  Read an automation’s current ACTIVE or INACTIVE status, and activate or deactivate it when the user asks.
+  Inspect or change active status with lock checks, revision handling and read-back, without requiring unrelated repairs before deactivation.
 
 </details>
 

package/skills/wix-manage/references/automations/actions.md

@@ -3,7 +3,7 @@ name: "Automations Action Configuration"
 description: "Configure app-defined automation actions from their input schemas and preserve supported existing action mappings."
 ---
 
-> **Stage scope:** this stage covers only what [Build and Manage Wix Automations](https://dev.wix.com/docs/api-reference/business-management/automations/skills/build-and-manage-wix-automations) lists; do not perform anything marked "Later stages only" or any workflow that needs a guide marked "not yet published". "Stage", "Later stages only" and "not yet published" describe how this skill is being rolled out; never mention them to the user. Explain a limit in product terms: what can't be done through the API here and where the user can do it instead (for example, in the automations builder).
+> **Stage scope:** this stage covers only what [Build and Manage Wix Automations](https://dev.wix.com/docs/api-reference/business-management/automations/skills/build-and-manage-wix-automations) lists; do not perform anything marked "Later stages only", and follow the instruction attached to each guide marked "not yet published". "Stage", "Later stages only" and "not yet published" describe how this skill is being rolled out; never mention them to the user. Explain a limit in product terms: what can't be done through the API here and where the user can do it instead (for example, in the automations builder).
 
 # App-Defined Actions — Discovery, Schemas, Input Mapping
 
@@ -11,9 +11,9 @@ description: "Configure app-defined automation actions from their input schemas
 
 - An action is `appId` + `actionKey`. Find real ones with **Resolve Actions** (site catalog), then read the version active on the site with **Get Runtime Action**. Never invent keys.
 - The configuration is `appDefinedInfo.inputMapping`: an object keyed ONLY by input-schema property names, with values of the schema's type — literals, or `{{…}}` formulas in fields the UI schema marks as dynamic.
-- Fields marked `updateSchemaOnChange: true` reveal more inputs once set → **Get Action Dynamic Input Schema**. Output that depends on configuration → **Get Action Dynamic Output Schema** after the mapping is final.
-- **Later stages only — email is outside stage 2:** **Send an email** (`triggered-emails`): initialize each NEW step with **Generate Action Input Mapping**, persist the returned mapping unchanged, then configure content with Get / Set Email Content (Automations Email Actions (not yet published)). Existing content-only edits do not initialize another email.
-- Entity-selector fields take **ids**, never display names (Automations Entity and Provider Configuration (not yet published)).
+- Fields marked `updateSchemaOnChange: true` reveal more inputs once set → **Get Action Dynamic Input Schema**. Output that depends on configuration → **Get Action Dynamic Output Schema** after the mapping is final, except user-defined LLM result fields: declare their override schema directly (§4).
+- **Later stages only — email is outside stage 3:** **Send an email** (`triggered-emails`): initialize each NEW step with **Generate Action Input Mapping**, persist the returned mapping unchanged, then configure content with Get / Set Email Content (Automations Email Actions (not yet published; email configuration is outside stage 3)). Existing content-only edits do not initialize another email.
+- Entity-selector fields take **ids**, never display names (Automations Entity and Provider Configuration (topic guide not yet published; consult the [Automations API reference](https://dev.wix.com/docs/api-reference/business-management/automations))).
 - Before accepting any action, prove its side effect and its recipient (§6).
 
 ---
@@ -29,7 +29,7 @@ Site-scoped (`wix-site-id` header), SDK module `actionCatalog`: Resolve Actions
 3. Get Runtime Action for the 1–3 best candidates; build against that version's `inputSchema`, `outputSchema`, `interfaceConfiguration`.
 4. An action missing from Resolve Actions is not usable on this site. The builder shows such a step as "action not found" and blocks it.
 
-**Do not use** unsupported or deprecated actions — `send-mail` (→ `triggered-emails`), `send-coupon-action` (→ `wixcoupons-retrieve_coupon` + a delivery step that uses its code), `wix_automations-velo_action`, `wix_automations-data_manipulation_code` (code variable; public Create refuses it — §4 of Automations Delays Variables and Branches (not yet published)), `whatsapp-send-message` (WhatsApp), `forward-to-zapier` (Zapier), and site actions `wix_automations-wix_api_integration` (non-public). Match these by `actionKey` (+ `appId`), not by app or display name — other actions of the same app are fine. Reasons and replacements: §2 of Automations Feasibility and Planning (not yet published) (site actions: §1).
+**Do not use** unsupported or deprecated actions — `send-mail` (→ `triggered-emails`), `send-coupon-action` (→ `wixcoupons-retrieve_coupon` + a delivery step that uses its code), `wix_automations-velo_action`, `wix_automations-data_manipulation_code` (code variable; public Create refuses it — [Automations Delays Variables and Branches](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-delays-variables-and-branches) §4), `whatsapp-send-message` (WhatsApp), `forward-to-zapier` (Zapier), and site actions `wix_automations-wix_api_integration` (non-public). Match these by `actionKey` (+ `appId`), not by app or display name — other actions of the same app are fine. Reasons and replacements: §2 of Automations Feasibility and Planning (topic guide not yet published; consult the [Automations API reference](https://dev.wix.com/docs/api-reference/business-management/automations)) (site actions: §1).
 
 ### Selection rules
 
@@ -55,7 +55,7 @@ Conditional fields (`if`/`then`/`dependencies`, e.g. a due date shown only when
 UI-schema keys that change what you may write:
 
 - `dynamicValuesOptions.enabled: true` → the field accepts `{{…}}` formulas. `strict: true` → the formula must return the field's exact type/format. **A field without it is static: literal only.**
-- `"ui:widget": "EntitySelector"` + `entitySelectorOptions` (`selectorId`/`tag`, `filters`, `dynamicFiltersMapping`) → entity picker; value = id or array of ids (§1 of Automations Entity and Provider Configuration (not yet published)). Same for input properties carrying `itemsSelectionConfiguration`.
+- `"ui:widget": "EntitySelector"` + `entitySelectorOptions` (`selectorId`/`tag`, `filters`, `dynamicFiltersMapping`) → entity picker; value = id or array of ids (§1 of Automations Entity and Provider Configuration (topic guide not yet published; consult the [Automations API reference](https://dev.wix.com/docs/api-reference/business-management/automations))). Same for input properties carrying `itemsSelectionConfiguration`.
 - `"ui:field": "AudienceSelector"` → an audience object owned by the app's picker; don't hand-author it — the user sets it in the builder.
 - `"ui:field": "TextSectionField"` → display-only text; never map it.
 - `"ui:widget": "hidden"`, `ui:readonly` → keep the schema `default`. Other `ui:*` keys are presentation only.
@@ -63,13 +63,13 @@ UI-schema keys that change what you may write:
 ## 4. Dynamic input and output schemas
 
 - **Input**: a property with `updateSchemaOnChange: true` (e.g. a template or form id) changes which inputs exist. Set it, then call Get Action Dynamic Input Schema with `{appId, actionKey, inputMapping}` (the mapping so far). The builder shows the static schema **merged** with the returned one (properties and `required` united), so keys from either are kept. Repeat if another controlling field is revealed. Never invent a field you expected but didn't get — it appears only after its controlling selection. The builder re-fetches this schema from your saved mapping every time the step is opened, so a dynamic key whose controlling value isn't in the mapping is dropped on the first edit.
-- **Output**: after the mapping is final, call Get Action Dynamic Output Schema (or the bulk variant) and use the returned `outputSchema` for downstream `var()` paths. A dynamic output is a _real_ schema — never replace it with an override (allowlist: §3 of Automations Schemas and Scheduling (not yet published)).
+- **Output**: for `wix_automations-llm_call` result fields you define in its output configuration, declare `overrideOutputSchema` directly ([Automations Schemas and Scheduling](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-schemas-and-scheduling) §3); do not probe the dynamic-output SPI to discover your own declared fields or execute the AI during setup. For catalog-driven dynamic outputs, after the mapping is final, call Get Action Dynamic Output Schema (or the bulk variant) and use the returned `outputSchema` for downstream `var()` paths. A dynamic output is a _real_ schema — never replace it with an override (allowlist: [Automations Schemas and Scheduling](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-schemas-and-scheduling) §3).
 
 ## 5. Building the input mapping
 
 ### 5.1 Provider-owned mappings — email and opaque widgets
 
-> **Later stages only:** email and other opaque-widget configuration is not available in stage 2; this section is published in stage 4.
+> **Later stages only:** email and other opaque-widget configuration is not available in stage 3; this section is published in stage 4.
 
 **In this stage:** never invent an opaque widget's mapping or its app-owned keys; tell the user which action to add in the builder and how it should be configured.
 
@@ -83,7 +83,7 @@ MUST (builder renderability — the `GENERIC` form drops, rewrites or flags anyt
 - An action with no input properties (or only hidden ones): send `"inputMapping": {}` — the builder writes `{}` itself on open otherwise.
 - Map fields the form would auto-fill, or opening the step silently changes the automation: fields with a schema `default` (write the default or your value), every `identityType` input (the form auto-maps it when exactly one matching payload path exists), required `date`/`date-time`/`time` strings (else filled with "now").
 - Enum fields (`oneOf` / `enum`): one of the listed constants.
-- Entity-selector fields: real ids of the right kind and shape (§1 of Automations Entity and Provider Configuration (not yet published)).
+- Entity-selector fields: real ids of the right kind and shape (§1 of Automations Entity and Provider Configuration (topic guide not yet published; consult the [Automations API reference](https://dev.wix.com/docs/api-reference/business-management/automations))).
 - `{{…}}` only in fields with `dynamicValuesOptions.enabled` (or an `identityType` field), per [Automations Mapping Expressions](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-mapping-expressions) §4: number/boolean hold exactly one expression of that type; date-time a single date-time expression or ISO literal; strings may mix text and expressions. An **array-typed** `var()` in a string field is flagged as a format mismatch.
 - Don't copy volatile values: dates → `now()`/payload dates; ids → resolved at build time, never from examples.
 - Keep what the user describes for one field in that field. A subject described as "Order received, then the customer's first name" is one `subject` string mixing text and expressions (`"Order received {{var(…)}}"`); don't split its values into other fields, such as a message's `fields` rows.
@@ -113,7 +113,7 @@ Process: (1) fetch the effective schema (§4) before you write a mapping or any
 
 ### 5.3 Validation errors on actions
 
-Error shape, error type → fix, and how the builder shows each: [Build and Manage Wix Automations — included validation procedure](https://dev.wix.com/docs/api-reference/business-management/automations/skills/build-and-manage-wix-automations) §2. Must-know here: fix the field named by `configurationError.fieldKey` — never delete a field to silence it; `CRITICAL` blocks (status `INVALID`), `WARNING` doesn't but must be reported; a `var()` path that doesn't exist may NOT be reported — verify paths yourself.
+Error shape, error type → fix, and how the builder shows each: [Automations Validation and Persistence](https://dev.wix.com/docs/api-reference/business-management/automations/skills/automations-validation-and-persistence) §2. Must-know here: fix the field named by `configurationError.fieldKey` — never delete a field to silence it; `CRITICAL` blocks (status `INVALID`), `WARNING` doesn't but must be reported; a `var()` path that doesn't exist may NOT be reported — verify paths yourself.
 
 ## 6. Side-effect and recipient review
 
@@ -123,7 +123,7 @@ This section owns the semantic review (you, not code) required for every action
 - **Entity**: the affected entity has a matching input (e.g. a label picker for "add label").
 - **Identity input**: the id it acts on, with the right `identityType`.
 - **Recipient lineage** (email, chat, SMS, push): write down `{requestedAudience, resolvedAudienceKind (contact|visitor|owner|contributor|label|phone|device), resolvedIdentityPath}`. The trigger contact and a contact created upstream are different people even if both are `contactId`. Wording never proves the recipient.
-  - **Later stages only — email is outside stage 2:** Email: the audience fields decide — read `selectedAudience` / `contactId` exactly as in §3 of Automations Email Actions (not yet published) ("Recipient encoding"). A root `contactId` or `triggerContactExcluded` alone doesn't prove who receives it.
+  - **Later stages only — email is outside stage 3:** Email: the audience fields decide — read `selectedAudience` / `contactId` exactly as in §3 of Automations Email Actions (not yet published; email configuration is outside stage 3) ("Recipient encoding"). A root `contactId` or `triggerContactExcluded` alone doesn't prove who receives it.
   - Chat (`send-message`): only a schema-supported contact-id or visitor-id route; owner/team chat needs a different, proven component or a clarification.
   - SMS / push: prove the schema-supported contact, audience, phone or device route.