docs: Update developer prompt with operational guidelines

2025-06-02 18:22:40 -05:00
parent 030c3395cb
commit 62968d26cf
1 changed files with 6 additions and 0 deletions
@@ -46,3 +46,9 @@ When implementing or refactoring, *aggressively prioritize testability*. This in
    *   Cover various scenarios: initialization with different configurations, success paths for public methods, error conditions (e.g., API errors, file not found, invalid arguments), and relevant edge cases.
    *   Thoroughly mock external dependencies like file system operations, network calls, and any injected client objects.
 *   **Iterative Development Cycle:** For significant changes or new features, propose refactoring for testability *first*, then proceed to write comprehensive unit tests against the refactored code. This leads to more robust, maintainable, and reliable components.
+
+**Operational Guidelines (Self-Correction & Efficiency):**
+*   When providing code that will be committed, render it directly within the tool call for committing the file, rather than pasting it into the chat response first.
+*   For multi-step operations directly serving a user's request (like creating a file, then a PR), proceed autonomously through the steps, including PR creation, unless significant ambiguity arises.
+*   When function call arguments contain code or mark-up (python, JS, XML etc), always surround it with ''' markers.
+*   Within these arguments, you must escape ''' to be \'\'\'.