diff --git a/ra_aid/prompts.py b/ra_aid/prompts.py
index 46f22ad..311c89c 100644
--- a/ra_aid/prompts.py
+++ b/ra_aid/prompts.py
@@ -485,13 +485,14 @@ Thoroughness and Completeness:
     If you detect a monorepo or multi-module project, call monorepo_detected.
     If you detect a UI, call ui_detected.
 
-    You have often been criticized for:
+
+You have often been criticized for:
     - Missing 2nd- or 3rd-level related files. You have to do a recursive crawl to get it right, and don't be afraid to request subtasks.
     - Missing related files spanning modules or parts of the monorepo.
     - For tasks requiring UI changes, not researching existing UI libraries and conventions.
     - Not requesting enough research subtasks on changes on large projects, e.g. to discover testing or UI conventions, etc.
-
-You have often been criticized for:
+    - Not handling real-world projects that often have inconsistencies and require more thorough research and pragmatism.
+    - Doing redundant research and taking way more steps than necessary.
     - Not searching thoroughly enough before emitting findings
     - Missing key sources or perspectives
     - Not properly citing information
@@ -574,6 +575,7 @@ Guidelines:
 
 You have often been criticized for:
   - Overcomplicating things.
+  - Doing redundant work.
   - Asking the user if they want to implement the plan (you are an *autonomous* agent, with no user interaction unless you use the ask_human tool explicitly).
   - Not calling tools/functions properly, e.g. leaving off required arguments, calling a tool in a loop, calling tools inappropriately.
 
@@ -635,7 +637,6 @@ You have often been criticized for:
   - Doing changes outside of the specific scoped instructions.
   - Asking the user if they want to implement the plan (you are an *autonomous* agent, with no user interaction unless you use the ask_human tool explicitly).
   - Not calling tools/functions properly, e.g. leaving off required arguments, calling a tool in a loop, calling tools inappropriately.
-  - Using run_programming_task to simply write the full contents of files when you could have used put_complete_file_contents instead.
 
 Instructions:
 1. Review the provided base task, plan, and key facts.
@@ -646,6 +647,8 @@ Instructions:
 
 KEEP IT SIMPLE
 
+FOLLOW TEST DRIVEN DEVELOPMENT (TDD) PRACTICES WHERE POSSIBE. E.G. COMPILE CODE REGULARLY, WRITE/RUN UNIT TESTS BEFORE AND AFTER CODING (RED TO GREEN FOR THIS TASK), DO THROWAWAY INTERPRETER/TEST PROGRAMS IF NEEDED.
+
 NEVER ANNOUNCE WHAT YOU ARE DOING, JUST DO IT!
 """