> For the complete documentation index, see [llms.txt](https://docs.idew.org/code-chatbot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/code-chatbot/warm-up-project-outline/6-chatbot-improvement-and-reflection.md). # 6 Chatbot Improvement and Reflection ## Objective Implement changes to your chatbot based on the previous evaluation and reflect on the key principles of chatbot design. ## Instructions **1. Incorporate Improvements in your Chatbot** Based on your feedback in the previous activity, update your chatbot script and test it to ensure it works as expected. **2. Reflect on Key Learning** Now that you have completed your first basic chatbot, reflect on the key aspects of building a successful chatbot. Create a document and write what you have learned in the following three areas of chatbot design, as if you were advising people on how to develop their own chatbot. * **Chatbot Purpose:** What are important ideas to keep in mind when developing the chatbot's purpose and the problem to be solved? * **Chatbot Personality:** What are key things to consider when determining a chatbot personality and why are they important? Provide some example dialogue between the user and chatbot to help explain your ideas. * **Chatbot Scripting and Code:** What did you find challenging, but very important, when creating the actual script/code for the chatbot? How do you think these challenges will affect a larger chatbot project that will have more complexity and features? ## ✓ Deliverables Submit your document (about one page in length). Make your document easy to follow and ensure the three items above are clearly covered. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.idew.org/code-chatbot/warm-up-project-outline/6-chatbot-improvement-and-reflection.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.