# Best Practices This guide is designed to help everyone—whether you’re new or experienced—quickly get started and avoid common mistakes when building with Wegic. ## Prompting best practices Clear and detailed prompts lead to better results. Think of the AI as your engineering partner—it can only work with the information you give. **Prompting Tips:** * Be specific: Clearly mention the exact page and what you want to happen. * Use natural language: For example, say “I want to change the Hero background image to a video.” * Add screenshots: These are especially helpful for explaining bugs or UX problems. * Avoid giving too many instructions at once. Break your requests into smaller, easy-to-test steps. ## Call Timmy to fix If you notice any issues with the code, please let Kimmy know right away so they can check and fix it. We also have a built-in detection system—when a problem is found, a ***Call Timmy*** button will appear in the preview area on the right. Just click it, and Timmy, our expert AI website developer, will fix all issues for you. ## Keep calm and be patient It’s normal to feel ups and downs when working with AI. Sometimes it surprises you, other times it tests your patience. The final touches usually take the most time but make all the difference. ## Use the docs and ask for help Our documentation offers step-by-step guides, prompts, and much more. Need more help? Join our [Facebook Group](https://www.facebook.com/groups/758678533887120) to connect with fellow users and get support. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.wegic.ai/tips-and-tricks/best-practices.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.