> 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/social-media.md). # Social Media 🔉 Social media is a critical part of a company's online presence. So, it's important that the content shared throughout these platforms is consistently on brand. * [ ] Username A unique identifier on a platform ⭐️ Be consistent to be found more easily across different social media platforms * [ ] Avatar A profile picture for each social media platform ⭐️ Be consistent to stay recognizable across all platforms * [ ] Colors Links and actions whose color can be customized ⭐️ Primary color is best to go with, unless it is inaccessible then choose alternative * [ ] Tone of voice The character in your posts and messages on social media * [ ] Post guidelines The do's and don'ts of what content you can post * [ ] Image guidelines A background or cover image that typically sits on the profile * [ ] Type of content Memes, user-generated, professional or behind the scenes --- # 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/social-media.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.