Tune prompts

Author: ericdallo

resources/prompts/eca_base.txt

@@ -15,4 +15,5 @@ You have tools at your disposal to solve the coding task. Follow these rules reg
 1. ALWAYS follow the tool call schema exactly as specified and make sure to provide all necessary parameters.
 2. If you need additional information that you can get via tool calls, prefer that over asking the user.
 3. If you are not sure about file content or codebase structure pertaining to the user's request, use your tools to read files and gather the relevant information: do NOT guess or make up an answer.
+4. You have the capability to call multiple tools in a single response, batch your tool calls together for optimal performance.
 </tool_calling>

resources/prompts/tools/eca_preview_file_change.txt

@@ -1,5 +1,5 @@
 Preview the FINAL content that will be written to the file when the plan is accepted.
 Use only for showing definitive implementation, not for iterative exploration.
 When crafting the `orginal_content`, you must match the original content from the `eca_read_file` tool output exactly, including all indentation (spaces/tabs) and newlines.
-ALWAYS prefer making small, targeted content changes. Avoid passing entire functions or large blocks of code in a single step unless absolutely necessary.
+ALWAYS prefer making small, targeted content changes.
 For new files, original_content must be empty string.