@wix/ditto-codegen-public 1.0.353 → 1.0.355

package/dist/out.js

@@ -12110,11 +12110,14 @@ var require_site_data_layer_rules = __commonJS({
 
 The agent operates on a live Wix site (METASITE_ID is in your prompt context).
 
-For any persistent-data need \u2014 CMS collections, content tables, schemas, data models, or databases that store items \u2014 use the \`wix-site-data-collection\` skill.
+## Mandatory for data persistence
 
-The \`wix-app\` skill remains the right tool for surrounding extensions (dashboard pages, modals, widgets); only the data layer is overridden. A Wix CLI data collection extension will NOT work here \u2014 it only provisions on app install, but this is a live site that already exists. Use the \`wix-site-data-collection\` skill to discover the existing collections on the site and wire your code against them.
+For any persistent-data need (CMS collections, tables, schemas, data models):
 
-DO NOT write any code relating to Wix CLI data extensions \u2014 for example, do not generate \`src/extensions/data/extensions.ts\`.`;
+1. **You MUST invoke the \`wix-site-data-collection\` skill first** \u2014 before scaffolding or writing collection code.
+2. **Do NOT** run \`wix generate\` with \`extensionType: DATA_COLLECTION\`, and do not create data-collection CLI extension files manually (e.g. \`src/extensions/backend/data-collections/*\`).
+
+\`wix-app\` is still correct for dashboard pages, modals, widgets, and UI \u2014 only the data layer is overridden here.`;
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.353",
+  "version": "1.0.355",
   "description": "AI-powered Wix CLI app generator - standalone executable",
   "scripts": {
     "build": "node build.mjs",
@@ -29,5 +29,5 @@
     "esbuild": "^0.27.2",
     "vitest": "^4.0.16"
   },
-  "falconPackageHash": "943d5f8ec00f0137ee6eb09d99039fcb25d9b2e45502f9ca49f7ba53"
+  "falconPackageHash": "dd6728e78e15bfd74a1b9833c183856688581fdb5c38a7c055f003e6"
 }