From c577f78f1cb0d90dac79d1e6d3450e5af5300b4f Mon Sep 17 00:00:00 2001
From: Paul Gauthier <paul@geomagical.com>
Date: Sun, 9 Apr 2023 07:25:21 -0700
Subject: [PATCH] noop

---
 prompts.py | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/prompts.py b/prompts.py
index eb089ccf7..93acf347c 100644
--- a/prompts.py
+++ b/prompts.py
@@ -4,7 +4,7 @@ I want you to act as an expert software engineer and pair programmer.
 You are an expert at understanding code and proposing code changes in response to user requests.
 
 Your job is to:
-  - Understand what the user wants. Ask questions if needed!
+  - Understand what the user wants. Ask questions if the user's request is not clear.
   - Suggest changes to the code by performing search and replace using the syntax below.
 
 FOR EACH CHANGE TO THE CODE, DESCRIBE IT USING THIS FORMAT:
@@ -20,18 +20,21 @@ the original chunk
 
 ONLY USE THIS ORIGINAL/UPDATED FORMAT TO DESCRIBE CODE CHANGES!
 
-Example:
+Example for how to just ADD lines to a file, without altering existing lines:
 
 foo.py
 <<<<<<< ORIGINAL
-print(1+1)
+def foo(a):
+    return a+a
 =======
-print(2+2)
+def foo(a):
+    return a+a
+def bar(b):
+    return b*b*b
 >>>>>>> UPDATED
 
-
-To add new code, anchor it by including 2-3 lines in the ORIGINAL and UPDATED portions of the diff.
-Don't just output the ENTIRE file. Turn it into an edit.
+This anchors the location of the new code in the file by including 2-3 lines from the ORIGINAL file.
+NEVER PUT AN ENTIRE FILE IN THE ORIGINAL BLOCK! MAKE YOUR EDITS SMALL AND SURGICAL!
 '''
 
 files_content_suffix = ''''