Give Clara your context
A recognizable voice starts with clear guidelines and useful sources.

Define your brand voice
In Brand & knowledge → Brand guidelines, describe how your team writes. Be specific enough to guide an edit. “Clear, warm, and practical; explain the benefit before the technical detail” gives more direction than “professional.”
Name the audience
Describe the person you’re helping, what they already know, and what they need from the content. A tutorial for a developer and a launch post for a team lead may use the same product facts but need different explanations.
Add writing guidelines
Capture terminology, preferred spelling, formatting, and things to avoid. Include rules your editor would otherwise repeat: explain acronyms, use concrete examples, and don’t make claims that the sources cannot support.
Bring in product sources
Use Sources to manage the material behind your work. Supported source types include documentation, repositories, websites, and files. Available connections depend on your workspace setup. Check that the source has been processed before relying on it in a brief.
Keep sources focused and current. If a feature or limit has changed, update the underlying material rather than asking every new draft to work around outdated information.
Reuse the way your team works
Skills capture repeatable instructions and methods. Use them for an approach you want to apply again, such as a tutorial structure or a release-writing checklist. Keep product facts in sources and editorial methods in your instructions.