> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/brand/logo.md). # Logo 💠 Your logo identifies your business. It conveys the product, story and tone all in one. When you've created your logo, it's important to ensure its usability across all platforms and experiences. * [ ] Color variations What colors (and grayscales) your logo can appear in ⭐️ Consider variations on light, dark and colored backgrounds for contrast * [ ] Usage The do's and don'ts of how and where the logo can be applied e.g. on different platforms, clear space, variations ⭐️ Show visual examples of your logo usage ⭐️ Consider when the symbol is used versus the wordmark (or both combined!) * [ ] Responsiveness The flexibility of the logo detail at varying sizes * [ ] Guidelines Documentation outlining all of the above to cement the principles --- # 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.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/brand/logo.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.