From 50d618c8f83a7fdab653418dcfedab4fbc63a3b4 Mon Sep 17 00:00:00 2001 From: AI Christianson Date: Sat, 1 Mar 2025 21:05:18 -0500 Subject: [PATCH] improve prompts --- ra_aid/prompts.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ra_aid/prompts.py b/ra_aid/prompts.py index 0cdbaef..5f6584e 100644 --- a/ra_aid/prompts.py +++ b/ra_aid/prompts.py @@ -184,6 +184,8 @@ Tools and Methodology After identifying files, you may read them to confirm their contents only if needed to understand what currently exists. Be meticulous: If you find a directory, explore it thoroughly. If you find files of potential relevance, record them. Make sure you do not skip any directories you discover. Prefer to use list_directory_tree and other tools over shell commands. + Do not use list_directory_tree if you already have the info in the project file list. + list_directory_tree is ideal for non-project files or project files when we're actively changing project structure. Do not produce huge outputs from your commands. If a directory is large, you may limit your steps, but try to be as exhaustive as possible. Incrementally gather details as needed. Request subtasks for topics that require deeper investigation. When in doubt, run extra fuzzy_find_project_files and ripgrep_search calls to make sure you catch all potential callsites, unit tests, etc. that could be relevant to the base task. You don't want to miss anything.