Update system prompt to reduce Dyad hallucinating imports (#344)

e2e-tests/snapshots/context_window.spec.ts_context-window-1.txt

@@ -44,9 +44,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.

e2e-tests/snapshots/context_window.spec.ts_context-window-2.txt

@@ -44,9 +44,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.

e2e-tests/snapshots/context_window.spec.ts_context-window-3.txt

@@ -44,9 +44,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.

e2e-tests/snapshots/context_window.spec.ts_context-window-5.txt

@@ -44,9 +44,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.

e2e-tests/snapshots/dump_messages.spec.ts_dump-messages-1.txt

@@ -44,9 +44,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.

e2e-tests/snapshots/import.spec.ts_import-app-with-AI-rules-1.txt

@@ -44,9 +44,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.

src/prompts/supabase_prompt.ts

@@ -71,7 +71,7 @@ useEffect(() => {
 }, []);
 
 
-Login page:
+Login page (NOTE: THIS FILE DOES NOT EXIST. YOU MUST GENERATE IT YOURSELF.):
 
 <dyad-write path="src/pages/Login.tsx" description="Creating a login page.">
 import { Auth } from '@supabase/auth-ui-react';

src/prompts/system_prompt.ts

@@ -100,9 +100,18 @@ If new code needs to be written (i.e., the requested feature does not exist), yo
 - Use <dyad-add-dependency> for installing packages.
   - If the user asks for multiple packages, use <dyad-add-dependency packages="package1 package2 package3"></dyad-add-dependency>
   - MAKE SURE YOU USE SPACES BETWEEN PACKAGES AND NOT COMMAS.
-- Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use <dyad-add-dependency>.
 - After all of the code changes, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary.
 
+Before sending your final answer, review every import statement you output and do the following:
+
+First-party imports (modules that live in this project)
+- Only import files/modules that have already been described to you.
+- If you need a project file that does not yet exist, create it immediately with <dyad-write> before finishing your response.
+
+Third-party imports (anything that would come from npm)
+- If the package is not listed in package.json, install it with <dyad-add-dependency>.
+
+Do not leave any import unresolved.
 
 Important Notes:
 - If the requested feature or change has already been implemented, only inform the user and do not modify the code.