When to Use the Code Editor
Use the Code Editor when:- Making quick fixes - Small adjustments Leo missed
- Reviewing changes - See what Leo modified
- Custom code - Add code Leo doesn’t handle
- Learning - Understand how your project works
Features
File Navigation
- Browse files - Navigate your project structure
- Search files - Find files quickly
- View code - See all your project files
Code Editing
- Syntax highlighting - Easy to read code
- Auto-save - Changes saved automatically
- Error detection - See issues as you type
File Management
- Create files - Add new files to your project
- Delete files - Remove files you don’t need
- Rename files - Organize your project
Best Practices
When to Edit Manually
- Small tweaks - Quick fixes and adjustments
- Custom logic - Special cases Leo doesn’t handle
- Configuration - Settings and environment setup
When to Ask Leo
- Major changes - Large features or refactoring
- Complex logic - Multi-file changes
- Integration work - Connecting to APIs
Tips
- Use sparingly - Let Leo handle most changes
- Test changes - Check preview after editing
- Ask Leo first - Often Leo can make the change
- Learn from code - See how Leo structures things
Working with Leo
After making manual edits:- Tell Leo about changes - So it knows what you did
- Ask for help - Leo can explain the code
- Request improvements - Ask Leo to enhance your edits