@wix/ditto-codegen-public 1.0.263 → 1.0.265

package/dist/out.js

@@ -48556,25 +48556,28 @@ var require_codegen_prompt = __commonJS({
 - Handle all edge cases and error scenarios appropriately
 
 IMPORTANT INSTRUCTIONS:
-1. NEVER run preview, dev, release, or promote commands. Preview/deployment is handled separately.
-2. You MUST run \`npm install\` when you are adding new dependencies to package.json.
-3. You SHOULD run \`npx tsc --noEmit\` to check for TypeScript errors after generating code.
-4. You SHOULD run \`npm run build\` or \`wix build\` to verify the build succeeds.
-5. CRITICAL: After creating any new extension (dashboard page, widget, embedded script, etc.), you MUST update \`src/extensions.ts\` to register it. Every extension needs to be exported from this file or it won't work.
-6. UUID GENERATION: To generate UUIDs, use Node.js: \`node -e "console.log(require('crypto').randomUUID())"\`. Do NOT use \`uuidgen\` as it may not be installed.
+- NEVER run preview, dev, release, or promote commands. Preview/deployment is handled separately.
+- You MUST run \`npm install\` when you are adding new dependencies to package.json.
+- You SHOULD run \`npx tsc --noEmit\` to check for TypeScript errors after generating code.
+- You SHOULD run \`npm run build\` or \`wix build\` to verify the build succeeds.
+- CRITICAL: After creating any new extension (dashboard page, widget, embedded script, etc.), you MUST update \`src/extensions.ts\` to register it. Every extension needs to be exported from this file or it won't work.
+- UUID GENERATION: To generate UUIDs, use Node.js: \`node -e "console.log(require('crypto').randomUUID())"\`. Do NOT use \`uuidgen\` as it may not be installed.
+
+TYPESCRIPT ENVIRONMENT:
+- The project extends \`astro/tsconfigs/base\` which enables \`verbatimModuleSyntax\`. Type-only imports MUST use the \`type\` keyword (e.g. \`import type { MyType } from './types';\`).
+
+EFFICIENCY - AVOID UNNECESSARY FIX CYCLES:
+- Once validation (tsc + build) passes, do NOT refactor or "clean up" code. Move on immediately.
+- When fixing multiple occurrences of the same pattern, use a single edit that covers all instances instead of separate edits for each occurrence.
 
 FILE CREATION - CRITICAL RULES:
-8. NEVER rewrite the same file twice. Once a file is written successfully, move on to the next file immediately.
-9. Create files SEQUENTIALLY, one at a time. Do NOT batch multiple write tool calls in a single response - this causes protocol errors.
-10. When creating an extension with multiple files, create them one at a time in sequence. Always update src/extensions.ts last to register the new extension.
-11. After EACH successful file write, immediately proceed to write the NEXT file. Do not stop until all files are created.
-12. COMPLETION CHECK: Before running validation (tsc, build), verify ALL required files for the extension have been created and src/extensions.ts has been updated.
+- NEVER rewrite the same file twice. Once a file is written successfully, move on to the next file immediately.
 
 OUTPUT SIZE LIMITS - CRITICAL:
-14. Keep each file under 200 lines. If a component would be larger, split it into multiple files (e.g., separate types.ts, utils.ts, styles).
-15. Do NOT output excessive comments or documentation in code.
-16. When writing a file, write it IMMEDIATELY after deciding to create it. Do not repeat "Now let me create..." multiple times - just create it.
-17. If you find yourself repeating the same text without making progress, STOP and write the file with whatever content you have ready.
+- Keep each file under 200 lines. If a component would be larger, split it into multiple files (e.g., separate types.ts, utils.ts, styles).
+- Do NOT output excessive comments or documentation in code.
+- When writing a file, write it IMMEDIATELY after deciding to create it. Do not repeat "Now let me create..." multiple times - just create it.
+- If you find yourself repeating the same text without making progress, STOP and write the file with whatever content you have ready.
 
 PERMISSIONS REQUIREMENT:
 At the end of your response, output the required Wix app permissions as a JSON block.
@@ -48774,6 +48777,8 @@ var require_config = __commonJS({
           webfetch: "allow",
           skill: "allow",
           task: "deny",
+          todowrite: "deny",
+          todoread: "deny",
           external_directory: {
             "/root/.agents/**": "allow",
             "/root/.claude/**": "allow",
@@ -74170,6 +74175,7 @@ var require_SPIAgent = __commonJS({
 - "ecom.taxCalculationProvider.calculateTax" - For custom tax calculations
 - "ecom.recommendationsProvider.getRecommendations" - For product recommendations
 - "ecom.catalog.getCatalogItems" - For external catalog integration
+- "bookings.staffSortingProvider.sortStaffMembers" - For custom staff sorting/assignment in bookings
 
 **SPI Selection Guidelines:**
 - For shipping-related requests \u2192 use "ecom.shippingRates.getShippingRates"
@@ -74181,6 +74187,7 @@ var require_SPIAgent = __commonJS({
 - For tax calculations \u2192 use "ecom.taxCalculationProvider.calculateTax"
 - For product recommendations \u2192 use "ecom.recommendationsProvider.getRecommendations"
 - For external catalog \u2192 use "ecom.catalog.getCatalogItems"
+- For staff sorting/assignment in bookings \u2192 use "bookings.staffSortingProvider.sortStaffMembers"
 </service_plugin>`;
     };
     exports2.getSPIAgentDocumentation = getSPIAgentDocumentation;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.263",
+  "version": "1.0.265",
   "description": "AI-powered Wix CLI app generator - standalone executable",
   "scripts": {
     "build": "node build.mjs",
@@ -28,5 +28,5 @@
     "@wix/ditto-codegen": "1.0.0",
     "esbuild": "^0.27.2"
   },
-  "falconPackageHash": "dba48cab03e25adf44f9e435dce1352d6354d45aa693b174a99500b2"
+  "falconPackageHash": "2e9eb478e1ada3951ce4c064b65a00360873cc2c6e31dfae89772452"
 }