diff --git a/e2e-tests/snapshots/astro.spec.ts_astro-1.txt b/e2e-tests/snapshots/astro.spec.ts_astro-1.txt
index d552d13..6d2b804 100644
--- a/e2e-tests/snapshots/astro.spec.ts_astro-1.txt
+++ b/e2e-tests/snapshots/astro.spec.ts_astro-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/chat_mode.spec.ts_chat-mode-selector---default-build-mode-1.txt b/e2e-tests/snapshots/chat_mode.spec.ts_chat-mode-selector---default-build-mode-1.txt
index e6f7d35..d05ffe2 100644
--- a/e2e-tests/snapshots/chat_mode.spec.ts_chat-mode-selector---default-build-mode-1.txt
+++ b/e2e-tests/snapshots/chat_mode.spec.ts_chat-mode-selector---default-build-mode-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/context_manage.spec.ts_manage-context---default-1.txt b/e2e-tests/snapshots/context_manage.spec.ts_manage-context---default-1.txt
index 070a991..412b72e 100644
--- a/e2e-tests/snapshots/context_manage.spec.ts_manage-context---default-1.txt
+++ b/e2e-tests/snapshots/context_manage.spec.ts_manage-context---default-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/context_manage.spec.ts_manage-context---smart-context-2.txt b/e2e-tests/snapshots/context_manage.spec.ts_manage-context---smart-context-2.txt
index dac3506..82c65ca 100644
--- a/e2e-tests/snapshots/context_manage.spec.ts_manage-context---smart-context-2.txt
+++ b/e2e-tests/snapshots/context_manage.spec.ts_manage-context---smart-context-2.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/context_window.spec.ts_context-window-1.txt b/e2e-tests/snapshots/context_window.spec.ts_context-window-1.txt
index 642a826..a48e6ea 100644
--- a/e2e-tests/snapshots/context_window.spec.ts_context-window-1.txt
+++ b/e2e-tests/snapshots/context_window.spec.ts_context-window-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/context_window.spec.ts_context-window-2.txt b/e2e-tests/snapshots/context_window.spec.ts_context-window-2.txt
index f03980c..52718bb 100644
--- a/e2e-tests/snapshots/context_window.spec.ts_context-window-2.txt
+++ b/e2e-tests/snapshots/context_window.spec.ts_context-window-2.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/context_window.spec.ts_context-window-3.txt b/e2e-tests/snapshots/context_window.spec.ts_context-window-3.txt
index 688b950..91cb63f 100644
--- a/e2e-tests/snapshots/context_window.spec.ts_context-window-3.txt
+++ b/e2e-tests/snapshots/context_window.spec.ts_context-window-3.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/context_window.spec.ts_context-window-5.txt b/e2e-tests/snapshots/context_window.spec.ts_context-window-5.txt
index f036301..b3fa837 100644
--- a/e2e-tests/snapshots/context_window.spec.ts_context-window-5.txt
+++ b/e2e-tests/snapshots/context_window.spec.ts_context-window-5.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/dump_messages.spec.ts_dump-messages-1.txt b/e2e-tests/snapshots/dump_messages.spec.ts_dump-messages-1.txt
index b7aeba0..61c3f86 100644
--- a/e2e-tests/snapshots/dump_messages.spec.ts_dump-messages-1.txt
+++ b/e2e-tests/snapshots/dump_messages.spec.ts_dump-messages-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/import.spec.ts_import-app-with-AI-rules-1.txt b/e2e-tests/snapshots/import.spec.ts_import-app-with-AI-rules-1.txt
index 014d7ef..9a65852 100644
--- a/e2e-tests/snapshots/import.spec.ts_import-app-with-AI-rules-1.txt
+++ b/e2e-tests/snapshots/import.spec.ts_import-app-with-AI-rules-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/partial_response.spec.ts_partial-message-is-resumed-1.txt b/e2e-tests/snapshots/partial_response.spec.ts_partial-message-is-resumed-1.txt
index 308f119..4a6f900 100644
--- a/e2e-tests/snapshots/partial_response.spec.ts_partial-message-is-resumed-1.txt
+++ b/e2e-tests/snapshots/partial_response.spec.ts_partial-message-is-resumed-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-1.txt b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-1.txt
index c77ce20..c58bbf2 100644
--- a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-1.txt
+++ b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-2.txt b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-2.txt
index 7c82611..5b398da 100644
--- a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-2.txt
+++ b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---complex-delete-rename-write-2.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-1.txt b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-1.txt
index bee4d5d..b09bc77 100644
--- a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-1.txt
+++ b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-2.txt b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-2.txt
index 899dd09..4a32a6e 100644
--- a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-2.txt
+++ b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---enabled-2.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-1.txt b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-1.txt
index 6ef28c4..b101ada 100644
--- a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-1.txt
+++ b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-2.txt b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-2.txt
index 663a757..809c2d9 100644
--- a/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-2.txt
+++ b/e2e-tests/snapshots/problems.spec.ts_problems-auto-fix---gives-up-after-2-attempts-2.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/select_component.spec.ts_select-component-1.txt b/e2e-tests/snapshots/select_component.spec.ts_select-component-1.txt
index a00b01d..04bc0be 100644
--- a/e2e-tests/snapshots/select_component.spec.ts_select-component-1.txt
+++ b/e2e-tests/snapshots/select_component.spec.ts_select-component-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/e2e-tests/snapshots/select_component.spec.ts_select-component-next-js-1.txt b/e2e-tests/snapshots/select_component.spec.ts_select-component-next-js-1.txt
index 62e2200..5b7120c 100644
--- a/e2e-tests/snapshots/select_component.spec.ts_select-component-next-js-1.txt
+++ b/e2e-tests/snapshots/select_component.spec.ts_select-component-next-js-1.txt
@@ -201,8 +201,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -226,8 +224,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -240,7 +236,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.
diff --git a/src/prompts/system_prompt.ts b/src/prompts/system_prompt.ts
index 9ecebad..403874b 100644
--- a/src/prompts/system_prompt.ts
+++ b/src/prompts/system_prompt.ts
@@ -257,8 +257,6 @@ const ProfileCard = ({ user }) => {
           <p className="text-gray-500">{user.email}</p>
         </div>
       </div>
-      
-      {/* ... keep existing code (user details section) */}
     </div>
   );
 };
@@ -282,8 +280,6 @@ const Dashboard = () => {
       <h1 className="text-2xl font-bold mb-6">Dashboard</h1>
       
       <ProfileCard user={currentUser} />
-      
-      {/* ... keep existing code (rest of dashboard content) */}
     </div>
   );
 };
@@ -296,7 +292,7 @@ I've renamed the UserProfile component to ProfileCard, updated its styling, remo
 # Additional Guidelines
 
 All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like letting the user know that they should implement some components or partially implementing features.
-If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
+If a user asks for many features at once, implement as many as possible within a reasonable response. Each feature you implement must be FULLY FUNCTIONAL with complete code - no placeholders, no partial implementations, no TODO comments. If you cannot implement all requested features due to response length constraints, clearly communicate which features you've completed and which ones you haven't started yet.
 
 Immediate Component Creation
 You MUST create a new file for every new component or hook, no matter how small.