> ## Documentation Index
> Fetch the complete documentation index at: https://www.wirebase.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Best practices

> Practical ways to get better, more consistent answers from Wirebase.

## Tell the assistant about yourself once

Fill in **Settings → User Instructions**: what to call you, what you do, and how you like answers. These preferences apply to every chat, so you don't repeat them. See [Settings](/docs/user-guide/account/settings).

## Pick the right model for the task

Fast, inexpensive models are fine for drafting and quick questions. Use a reasoning model for complex analysis, math or code. When you're unsure, [compare](/docs/user-guide/chat/compare) two or three models on the same prompt and keep the best answer.

## Use projects for ongoing work

If you keep giving the same background in new chats, create a [project](/docs/user-guide/chat/projects). Its instructions, files and knowledge bases apply to every chat inside it.

## Turn repeated prompts into tools

* Prompts you reuse word-for-word → save them as [prompts](/docs/user-guide/workspace/prompts) with `{{variables}}`.
* A persona or role with specific tools → build an [agent](/docs/user-guide/workspace/agents).
* A fixed multi-step process → build a [workflow](/docs/user-guide/workspace/workflows).
* Something that should happen on a schedule → create an [automation](/docs/user-guide/workspace/automations).

## Ground answers in your documents

For questions about your own material, add it to a [knowledge base](/docs/user-guide/workspace/knowledge) and mention it with `@`. Answers then cite the passages they came from, so you can check them.

## Keep tool use under control

Use **@mentions** to tell the assistant exactly which agent, workflow or connector to use. If you want to approve each tool call before it runs, switch the tool mode to **Manual**. See [Tools](/docs/user-guide/chat/tools).

## Write clear instructions

When writing instructions for an agent or project:

* Say who the audience is and what a good answer looks like.
* Give formats explicitly ("answer in a table with columns X, Y, Z").
* Say what to do when information is missing ("ask a clarifying question" or "say you don't know").
* Keep them short. Long instructions are harder for models to follow consistently.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.