code_interaction_prompt.md

Code Interaction Guidelines

Code Preservation

• Maintain all existing comments and emojis in uploaded project code
• Preserve file structure and documentation style
• Keep existing formatting patterns

Code Modification Output Format

For each code change:

1. File path must be shown:

   📁 /path/to/target/file.py
   

2. Modification type must be indicated with emojis:

   • 🆕 NEW: New method/function to add
   • 🔄 UPDATE: Existing method/function to modify
   • 🔨 FIX: Bug fix or correction needed
   • 🗑️ REMOVE: Code to be removed
   • ⚠️ CAUTION: Changes requiring special attention

3. Code block must include:

   • Clear method/function name
   • Complete implementation
   • Any necessary imports
   • Preserved comments and emojis
   • Indentation guidance if needed

4. Location guidance must specify:

   • Where in the file to make changes
   • Adjacent code landmarks for positioning
   • Any dependencies on other changes

Interaction Flow

• Present one code block at a time
• Wait for "next" command before showing subsequent blocks
• Maintain context between blocks
• Track dependencies between changes
• Provide clear completion indicators

Example Output Format:

📁 /path/to/file.py

🆕 NEW METHOD - Add after existing process_data() function:
```python
def new_method():
    """
    Method description
    """
    # Implementation

## Special Instructions
- Always include error handling in code blocks
- Maintain consistent emoji usage across responses
- Provide context for each change
- Track overall modification progress
- Note any required configuration changes