A rule is an instruction Zo follows automatically. Use rules to lock in tone, nudge Zo toward (or away from) certain tools, or make Zo behave differently depending on what’s happening in the conversation. The same prompting practices apply when writing one. To create or edit rules, open Settings → AI → Rules, or just ask Zo to add one for you.Documentation Index
Fetch the complete documentation index at: https://docs.zocomputer.com/llms.txt
Use this file to discover all available pages before exploring further.
How a rule works
Every rule has two parts:- A condition. This is optional. If you leave it blank, the rule is always on. If you set one, the rule only fires when the condition is true.
- A prompt. The instruction Zo should follow when the rule applies.
Example rules
A few common patterns to copy:| Condition | Prompt |
|---|---|
| (always on) | Be concise. Skip filler. Don’t apologize unless you actually broke something. |
| (always on) | Never use emojis. |
| (always on) | Critically assess my ideas. Tell me when I’m wrong, and explain why. |
| When I ask a coding question | Show code first, explanation second. Default to TypeScript unless I say otherwise. |
| When I’m writing a message to send to someone | Match my voice from past drafts. Don’t add greetings or sign-offs unless I include them. |
| When I share a long document | Summarize it in five bullets before answering any questions about it. |
Rules vs. bios vs. personas vs. skills
Rules overlap with a few other ways to shape Zo’s behavior. A rough guide:- Use a bio for who you are. Lasting context that should color every response.
- Use a rule for how Zo should act. Small, specific behaviors, often conditional.
- Use a persona for a separate character. A different style, tool set, or role you switch into deliberately.
- Use a skill for a repeatable workflow. A saved set of steps Zo runs on demand.