> ## Documentation Index > Fetch the complete documentation index at: https://docs.helloleo.dev/llms.txt > Use this file to discover all available pages before exploring further. # What to Avoid > Common mistakes when prompting Leo Avoiding these common mistakes will help you get better results from Leo. ## ❌ Being Too Vague Vague requests don't give Leo enough information to work with. ### Bad Examples ``` Make it better Fix the bugs Improve the design Add some features ``` ### Why It Fails Leo doesn't know what "better" means or which bugs to fix. Be specific about what you want. ### ✅ Better Alternatives ``` Add a search bar that filters products as I type Fix the form validation to show errors under each field Update the color scheme to use blue and white Add a "Save" button that saves data to Airtable ``` ## ❌ Asking for Too Much at Once Complex requests with multiple unrelated features are hard to execute well. ### Bad Examples ``` Build a complete CRM system with customer management, inventory tracking, order processing, and reporting ``` ``` Add authentication, payment processing, email notifications, and a mobile app ``` ### Why It Fails Too many moving parts make it hard to get everything right. Features may conflict or be incomplete. ### ✅ Better Approach Break it down: ``` First, create a customer list page showing all customers from Odoo. ``` Then: ``` Add a customer detail page that shows customer information and their orders. ``` Continue building step by step. ## ❌ Using Technical Jargon You don't need to know programming terms. Leo handles the technical details. ### Bad Examples ``` Create a React component with useState and useEffect hooks Use a REST API endpoint with POST method Implement a Redux store with actions and reducers ``` ### Why It Fails You're trying to tell Leo HOW to build it, but Leo already knows the best way. Focus on WHAT you want. ### ✅ Better Approach ``` Create a form that saves customer data when submitted Show a list of products that updates automatically Add a button that sends data to the server ``` ## ❌ Ignoring Context Not providing enough context makes it hard for Leo to understand your needs. ### Bad Examples ``` Add a button Create a page Show some data ``` ### Why It Fails Leo doesn't know where the button goes, what the page should show, or which data to display. ### ✅ Better Approach ``` Add a "Save" button at the bottom of the customer form that saves the data to Odoo ``` ``` Create a products page that shows all products from Odoo in a grid layout with images and prices ``` ``` Show customer data from Airtable in a table with name, email, and phone columns ``` ## ❌ Conflicting Requirements Asking for things that contradict each other causes confusion. ### Bad Examples ``` Make it simple but include all features Use a dark theme but keep it bright Make it fast but show lots of data ``` ### Why It Fails Conflicting requirements make it impossible to satisfy everything. ### ✅ Better Approach Prioritize: ``` Start with a simple product list. We can add filters and sorting later. ``` Or be specific: ``` Use a dark theme with bright accent colors for buttons and links. ``` ## ❌ Not Iterating Trying to get everything perfect in one prompt rarely works. ### Bad Examples ``` Build a perfect e-commerce site with everything Create the ultimate dashboard with all features ``` ### Why It Fails "Perfect" and "everything" are subjective and vague. You'll need to refine anyway. ### ✅ Better Approach Start simple, then refine: ``` Create a basic product page showing name, price, and image. ``` Then: ``` Add a description section below the product details. ``` Continue building and refining. ## ❌ Unrealistic Expectations Expecting Leo to know things it can't know. ### Bad Examples ``` Use my company colors (without specifying them) Connect to my API (without providing details) Use the same design as my other site (without showing it) ``` ### Why It Fails Leo doesn't have access to information you haven't provided. ### ✅ Better Approach Be explicit: ``` Use blue (#0066CC) as the primary color and white for backgrounds. ``` ``` Connect to my Odoo instance at https://mycompany.odoo.com using the credentials in project settings. ``` ## ❌ Not Using Memories Forgetting to save important context that Leo should remember. ### Bad Examples Always describing the same requirements in every prompt: ``` Use French language Always use dark mode Company name is Acme Corp ``` ### Why It Fails You're repeating yourself and wasting prompts. ### ✅ Better Approach Save important context in Project Memories: * "Always use French language" * "Default to dark mode" * "Company name: Acme Corp" Then Leo remembers automatically. ## Key Takeaways 1. **Be specific** - Describe exactly what you want 2. **One thing at a time** - Focus on single features 3. **Describe outcomes** - What should happen, not how 4. **Provide context** - Help Leo understand your needs 5. **Iterate** - Build and refine gradually 6. **Use memories** - Save important context ## Remember * **Error fixes are free** - Don't worry if something isn't right * **You can always refine** - Build features step by step * **Leo learns** - The more you work together, the better it gets Learn how to write effective prompts See examples of good prompts