> 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/topics/ux-writing.md). # UX Writing ✏️ UX writing is not copywriting. It's not writing ads, marketing copy or what goes on the merch. UX writing is interface copy. It's text that explains what features do, and tells a user what action will occur by interacting with that element. * [ ] Clear and concise Say exactly what will happen, in as few words as possible ⭐️ Read your copy back and remove redundant words ⭐️ Don't invent new words for actions, keep it familiar * [ ] Useful Take the user to an intentional direction ⭐️ A user should understand what an action is going to do before they interact with it ⭐️ Remove jargon that doesn't help the user * [ ] Tone How your brand comes across through messaging ⭐️ Avoid humour, particularly sarcasm as a tone in general as you leave room for interpretation * [ ] Consistency Wrap a certain action under one word e.g. don't interchange 'Next' and 'Continue' when moving screen to screen ⭐️ Consistency helps users notice a purposeful change in copy e.g. a number of 'Next' steps followed by a final 'Confirm' step tells them something different will happen next * [ ] Avoid dark patterns This isn't your chance to be sarcastic or antagonise the user ⭐️If you have a preferred action for the user, change visual hierarchy - don't make the secondary option intentionally sound worse ⭐️ Don't hide relevant information or actions from the user out of concern it leads to churn --- # 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/topics/ux-writing.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.