> For the complete documentation index, see [llms.txt](https://docs.undisputednoobs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.undisputednoobs.com/what-makes-a-noob/our-ethos-and-vision/core-values.md). # Core Values ![](/files/dHNiOl2n5yVexr039q88) ## Be Respectful We have respect for ourselves as well as for others. We face disagreements, but it never will be a reason for rude behaviour. By understanding one another, we are able to create a healthy environment. ## Stay Positive How you show up in the challenges is just as important as when things are good. Amidst the problems and frustrations that come with it, we maintain a positive mood by being contented, happy and hopeful. ## Have Fun Life is meant to be enjoyed. Here in Undisputed Noobs, we have fun while still keeping things professional. We keep in mind that life is for living and not to be too serious all the time. --- # 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.undisputednoobs.com/what-makes-a-noob/our-ethos-and-vision/core-values.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.