diff --git a/backend/agent/gemini_prompt.py b/backend/agent/gemini_prompt.py index e20ebd83..bf171c8b 100644 --- a/backend/agent/gemini_prompt.py +++ b/backend/agent/gemini_prompt.py @@ -211,19 +211,16 @@ You have the ability to execute operations using both Python and CLI tools: - Store different types of data in appropriate formats ## 3.5 FILE EDITING STRATEGY -- **PREFERRED FILE EDITING APPROACH:** - 1. **For intelligent edits:** Use `edit_file` with natural language instructions - - Ideal for: Code and Doc Editing, adding features, refactoring, complex modifications, following patterns - - Provide clear instructions and use `// ... existing code ...` format - - Example: "Add error handling to the login function" or "Update the CSS to use dark theme" - 2. **For simple replacements:** Use `str_replace` when you need exact text replacement - - Ideal for: Simple text substitutions, specific string changes - 3. **For complete rewrites:** Use `full_file_rewrite` when replacing entire file content -- **TOOL SELECTION PRIORITY:** - - Prefer `edit_file` for most editing tasks that require intelligence or pattern-following - - Use `str_replace` only when you need single line text substitution - - Use `full_file_rewrite` only when completely replacing file contents -- The `edit_file` tool is designed to apply changes intelligently and quickly, making it ideal for most code and doc modifications. +- **PREFERRED FILE EDITING TOOL: `edit_file`** + - **Always prefer the `edit_file` tool for all file modifications.** It is a powerful and intelligent tool that can handle everything from simple text replacements to complex code refactoring. + - **How to use `edit_file`:** + 1. Provide a clear, natural language `instructions` parameter describing the change (e.g., "I am adding error handling to the login function"). + 2. Provide the `code_edit` parameter showing the exact changes, using `// ... existing code ...` to represent unchanged parts of the file. This keeps your request concise and focused. + - **Examples:** + - **Adding a feature:** Your `code_edit` would show the new code block surrounded by `// ... existing code ...`. + - **Correcting a typo:** Your `code_edit` would show the line with the typo, and then the corrected line, surrounded by `// ... existing code ...`. + - **Rewriting a section:** Your `code_edit` would contain the entire new section, surrounded by `// ... existing code ...`. +- The `edit_file` tool is your primary tool for changing files. While other file writing tools exist, you should default to using `edit_file` for its flexibility and intelligence. # 4. DATA PROCESSING & EXTRACTION @@ -1670,17 +1667,25 @@ Let's combine all our work into a comprehensive package for you to download. Fir - -todo.md -# Japan Trip Planning Todo + +todo.md +I am marking all remaining tasks as complete in my todo list. + +# Japan Trip Planning Todo ## Research Phase - [x] Research flight options from Seattle to Japan - [x] Research best cities/regions to visit based on interests (historical sites, hidden gems, cultural experiences) - [x] Research transportation options within Japan -- [ ] Research accommodation options within budget +- [x] Research accommodation options within budget - [x] Research proposal location options +## Flight & Transportation Recommendations +- **Flights**: Seattle to Tokyo flights range from $800-1,200 roundtrip +- **JR Pass**: 14-day pass recommended for $435 (covers most transportation) +- **Recommended Route**: Tokyo → Kyoto → Nara → Osaka for optimal cultural experience +- **Local Transport**: IC cards (Suica/Pasmo) for city transportation + ## Itinerary Creation - [x] Create detailed day-by-day itinerary - [x] Balance activities between major attractions and hidden gems @@ -1705,41 +1710,8 @@ Let's combine all our work into a comprehensive package for you to download. Fir - [x] Ensure all interests are addressed - [x] Verify budget alignment - [x] Finalize proposal location recommendation -- [x] Proofread and finalize all documents -# Japan Trip Planning Todo - -## Research Phase -- [x] Research flight options from Seattle to Japan -- [x] Research best cities/regions to visit based on interests (historical sites, hidden gems, cultural experiences) -- [x] Research transportation options within Japan -- [ ] Research accommodation options within budget -- [x] Research proposal location options - -## Itinerary Creation -- [x] Create detailed day-by-day itinerary -- [x] Balance activities between major attractions and hidden gems -- [x] Include cultural experiences (kendo, tea ceremonies, Zen meditation) -- [x] Include visit to Nara for deer park -- [x] Plan walking tours of cities -- [x] Identify and integrate romantic proposal location -- [x] Calculate estimated costs for activities, accommodations, and transportation - -## Travel Handbook Development -- [x] Create HTML structure for travel handbook -- [x] Add CSS styling for handbook -- [x] Create maps section with key locations -- [x] Create attraction descriptions -- [x] Compile essential Japanese phrases -- [x] Write travel tips section -- [x] Add budget management section -- [x] Test handbook functionality - -## Final Review -- [x] Review itinerary for balance and pacing -- [x] Ensure all interests are addressed -- [x] Verify budget alignment -- [x] Finalize proposal location recommendation -- [x] Proofread and finalize all documents +- [x] Proofread and finalize all documents + diff --git a/backend/agent/prompt.py b/backend/agent/prompt.py index fe028fc9..eb190a4b 100644 --- a/backend/agent/prompt.py +++ b/backend/agent/prompt.py @@ -236,19 +236,16 @@ You have the abilixwty to execute operations using both Python and CLI tools: - Store different types of data in appropriate formats ## 3.5 FILE EDITING STRATEGY -- **PREFERRED FILE EDITING APPROACH:** - 1. **For intelligent edits:** Use `edit_file` with natural language instructions - - Ideal for: Code and Doc Editing, adding features, refactoring, complex modifications, following patterns - - Provide clear instructions and use `// ... existing code ...` format - - Example: "Add error handling to the login function" or "Update the CSS to use dark theme" - 2. **For simple replacements:** Use `str_replace` when you need exact text replacement - - Ideal for: Simple text substitutions, specific string changes - 3. **For complete rewrites:** Use `full_file_rewrite` when replacing entire file content -- **TOOL SELECTION PRIORITY:** - - Prefer `edit_file` for most editing tasks that require intelligence or pattern-following - - Use `str_replace` only when you need single line text substitution - - Use `full_file_rewrite` only when completely replacing file contents -- The `edit_file` tool is designed to apply changes intelligently and quickly, making it ideal for most code and doc modifications. +- **PREFERRED FILE EDITING TOOL: `edit_file`** + - **Always prefer the `edit_file` tool for all file modifications.** It is a powerful and intelligent tool that can handle everything from simple text replacements to complex code refactoring. + - **How to use `edit_file`:** + 1. Provide a clear, natural language `instructions` parameter describing the change (e.g., "I am adding error handling to the login function"). + 2. Provide the `code_edit` parameter showing the exact changes, using `// ... existing code ...` to represent unchanged parts of the file. This keeps your request concise and focused. + - **Examples:** + - **Adding a feature:** Your `code_edit` would show the new code block surrounded by `// ... existing code ...`. + - **Correcting a typo:** Your `code_edit` would show the line with the typo, and then the corrected line, surrounded by `// ... existing code ...`. + - **Rewriting a section:** Your `code_edit` would contain the entire new section, surrounded by `// ... existing code ...`. +- The `edit_file` tool is your primary tool for changing files. While other file writing tools exist, you should default to using `edit_file` for its flexibility and intelligence. # 4. DATA PROCESSING & EXTRACTION diff --git a/backend/agent/sample_responses/1.txt b/backend/agent/sample_responses/1.txt index 33aff2f1..189d4960 100644 --- a/backend/agent/sample_responses/1.txt +++ b/backend/agent/sample_responses/1.txt @@ -611,9 +611,10 @@ render(); Let me update our todo.md file to reflect our progress: - -todo.md - + +todo.md +I am marking all tasks as complete in my todo list. + # Pong Game Development Plan ## Project Setup diff --git a/backend/agent/sample_responses/2.txt b/backend/agent/sample_responses/2.txt index 169e0b7f..9d0569d0 100644 --- a/backend/agent/sample_responses/2.txt +++ b/backend/agent/sample_responses/2.txt @@ -999,9 +999,11 @@ Now let's check that our files are in place and update our todo list: - -todo.md -# Japan Trip Planning Todo + +todo.md +I am marking all remaining tasks as complete in my todo list. + +# Japan Trip Planning Todo ## Research Phase - [x] Research flight options from Seattle to Japan