@wix/ditto-codegen-public 1.0.166 → 1.0.167

package/dist/out.js

@@ -114534,12 +114534,27 @@ Given the full chat history, current user request, and all project files:
   * You want to check their configuration
   * They are related but don't need modification
 - **DEFAULT TO MODIFYING EXISTING EXTENSIONS** - Always prefer updating existing extensions over creating new ones
+- **AVOID DUPLICATING THE SAME EXTENSION** - Be careful about creating duplicates:
+  * If "Relevant Existing Extensions" shows an extension that can handle the request, modify it in currentExtensions
+  * Don't create a new extension to do the exact same thing as an existing one
+  * HOWEVER: If the user uses keywords like "new", "create", "add", "another" with an extension type, CREATE it in additionalExtensions
+- **DETECTING NEW EXTENSION REQUESTS - Look for these KEYWORDS:**
+  * "a new [extension type]" \u2192 CREATE new extension in additionalExtensions
+  * "create a [extension type]" \u2192 CREATE new extension in additionalExtensions
+  * "add a [extension type]" \u2192 CREATE new extension in additionalExtensions
+  * "another [extension type]" \u2192 CREATE new extension in additionalExtensions
+  * If user mentions "new" or "create" or "add" before an extension type, they want a NEW separate one
+  * Even if purpose seems similar to existing, if they say "new/create/add", honor that request
+- **Examples:**
+  * "add animation duration" + existing dashboard \u2192 modify existing dashboard ONLY
+  * "add animation duration AND a new dashboard" \u2192 modify existing + create NEW dashboard
+  * "add animation duration AND create a dashboard" \u2192 modify existing + create NEW dashboard
+  * "add X, and a new dashboard page to manage Y" \u2192 modify existing (if applicable) + create NEW dashboard (user said "new")
 - **Only create new extensions (additionalExtensions) when:**
-  1. The user EXPLICITLY asks to CREATE/ADD something entirely new
-  2. The functionality does NOT exist in any current extension
-  3. No existing extension can be modified to fulfill the request
-- **If an extension already exists that does similar things, MODIFY IT instead of creating a new one**
-- **When in doubt, use currentExtensions to modify existing code, NOT additionalExtensions**
+  1. The user EXPLICITLY uses keywords "new", "create", "add", or "another" before an extension type
+  2. OR: The functionality truly does NOT exist in any current extension
+- **If an extension already exists AND user doesn't use "new/create/add" keywords, MODIFY IT instead**
+- **When in doubt about "new" keyword presence, FAVOR CREATING the new extension - missing user intent is worse than creating extra**
 
 **IMPORTANT**: Before deciding on extensions, check if this is a data-only operation (handled by PlannerAgent). See common scenarios below.
 
@@ -114584,12 +114599,21 @@ ${(0, codegen_common_logic_1.getExtensionDecisionMatrix)()}`;
     exports2.iterationAgentCommonUseCasesGuide = iterationAgentCommonUseCasesGuideConst;
     exports2.iterationAgentChatHistoryContext = (0, iterationScenarios_1.getChatHistoryContext)();
     exports2.iterationAgentExtensionSelectionLogic = iterationAgentExtensionSelectionLogicConst;
-    var getIterationAgentConstraints = (supportedTypes) => `- **CRITICAL - AVOID CREATING NEW EXTENSIONS**: Only propose additionalExtensions if existing ones CANNOT fulfill the user's request. Review "Relevant Existing Extensions" carefully. If similar functionality exists, MODIFY it instead of creating new.
+    var getIterationAgentConstraints = (supportedTypes) => `- **CRITICAL - AVOID UNNECESSARY DUPLICATION**: Only propose additionalExtensions if existing ones CANNOT fulfill the user's request. Review "Relevant Existing Extensions" carefully. If an existing extension can handle the request, MODIFY it instead of creating new.
+- **SMART DUPLICATION DETECTION**: When deciding between modifying vs creating:
+  * If user says "add X feature" and an extension exists that handles X \u2192 modify the existing extension in currentExtensions
+  * If user says "add X AND create a new Y" where Y is explicitly requested as NEW \u2192 modify existing for X + create new for Y in additionalExtensions
+  * Same extension TYPE can appear in both currentExtensions and additionalExtensions if they serve DIFFERENT purposes
+  * Example: "add animation field" (existing dashboard) \u2192 modify only
+  * Example: "add animation field AND create new dashboard for analytics" \u2192 modify existing + create new
 - **STRONG DEFAULT**: Assume you should use currentExtensions (modify existing) unless there's a clear reason to create something entirely new
-- **additionalExtensions ONLY WHEN**: The user explicitly asks to "create", "add", or "build" something that doesn't exist at all in the current project
+- **additionalExtensions WHEN**:
+  1. The user explicitly asks to "create", "add", or "build" something new (look for keywords like "new", "create", "add")
+  2. The new functionality serves a DIFFERENT purpose than existing extensions (even if same type)
+  3. No single existing extension can be modified to fulfill the entire request
 - Be specific about which file paths are relevant for each current extension (all extension types)
 - Consider the full chat history context when making decisions
-- **PRIORITIZE REUSING EXISTING EXTENSIONS** over creating new ones - this is a hard requirement, not a suggestion
+- **PRIORITIZE REUSING EXISTING EXTENSIONS** over creating new ones when the purpose is the same
 - **SUPPORTED EXTENSION TYPES ONLY**: ${supportedTypes}
 - **IMPORTANT**: The "relatedSpis" field is ONLY for SERVICE_PLUGIN extensions - specify the SPI types
 - The "paths" field is for ALL extension types - specify relevant file paths to modify
@@ -114602,14 +114626,14 @@ ${(0, codegen_common_logic_1.getExtensionDecisionMatrix)()}`;
   * Referenced for information but don't need changes
   * Checked for correctness but remain unchanged
   * This is your DEFAULT choice for most requests unless the user explicitly wants something entirely new
-- **ADDITIONAL EXTENSIONS**: ONLY use when the user explicitly asks to CREATE/ADD entirely new functionality that has no existing equivalent. Do NOT use if you can modify existing extensions.
+- **ADDITIONAL EXTENSIONS**: Use when user explicitly asks to CREATE/ADD new functionality with a different purpose. CAN be the same type as extensions in currentExtensions if they serve different purposes.
 - For currentExtensions, ensure relevantUserRequest precisely reflects the change to be applied in those files (e.g., "Update static fee from 5 ILS to 10 ILS"), not a generic description
 - For additionalExtensions, ensure relevantUserRequest describes the new functionality being created (e.g., "Add new 10 ILS static fee calculator")
-- **KEY RULE - MODIFICATION FIRST**: Default to currentExtensions (modify existing). Only use additionalExtensions when the user's request is explicitly to CREATE something that has NO existing equivalent.
+- **KEY RULE - MODIFICATION FIRST**: Default to currentExtensions (modify existing). Only use additionalExtensions when the user's request explicitly includes creating NEW functionality with a different purpose.
 - **CRITICAL - EXTENSION-SPECIFIC DESCRIPTIONS**: The relevantUserRequest field becomes the extension's description and is passed directly to individual agents. Each agent ONLY sees its own extension - they don't have context about other extensions, the broader user request, or duplicate issues. Focus on WHAT THIS SPECIFIC EXTENSION should do, not WHY or how it relates to other extensions. Do not reference other extensions.`;
     exports2.getIterationAgentConstraints = getIterationAgentConstraints;
     var getIterationAgentKeyPoints = (supportedTypes) => `- currentExtensions: Existing extensions that need to be MODIFIED (use extensionType from: ${supportedTypes}) - **THIS IS YOUR DEFAULT CHOICE**
-- additionalExtensions: New extensions that need to be CREATED (use extensionType from: ${supportedTypes}) - **ONLY USE IF USER EXPLICITLY ASKS TO CREATE SOMETHING NEW**
+- additionalExtensions: New extensions that need to be CREATED (use extensionType from: ${supportedTypes}) - **USE WHEN USER EXPLICITLY ASKS TO CREATE SOMETHING NEW WITH A DIFFERENT PURPOSE**
 - summary: Brief summary combining the chat history and current user request
 - "name" field: REQUIRED for ALL extensions - provide a descriptive name for the extension
 - "relatedSpis" field: ONLY for SERVICE_PLUGIN extensions - specify the SPI name

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/ditto-codegen-public",
-  "version": "1.0.166",
+  "version": "1.0.167",
   "description": "AI-powered Wix CLI app generator - standalone executable",
   "scripts": {
     "build": "node build.mjs",
@@ -24,5 +24,5 @@
     "@wix/ditto-codegen": "1.0.0",
     "esbuild": "^0.25.9"
   },
-  "falconPackageHash": "f4fa79a226dd76d71e7123b20e0cc77f46c96764501c9af43a76a455"
+  "falconPackageHash": "8b47048eb36926399b2a9361f1c4cfebf5018b9e262861c92e2ccb73"
 }