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

# System Prompts

> Shape Navigator behavior with personal, team, and agent-level instructions.

System prompts define how the assistant should work before a user sends a message. In Navigator, prompts are most useful when they clarify role, constraints, available context, and tool-use preferences.

## Prompt layers

<CardGroup cols={2}>
  <Card title="Personal preferences" icon="user">
    Set tone, language, formatting, and recurring context for your own account.
  </Card>

  <Card title="Agent instructions" icon="robot">
    Give each custom agent a narrow job and clear boundaries.
  </Card>

  <Card title="Tool guidance" icon="wrench">
    Explain when a tool should or should not be used.
  </Card>

  <Card title="Workflow instructions" icon="workflow">
    Describe how a published workflow should interpret inputs and report results.
  </Card>
</CardGroup>

## Good prompt shape

```text theme={null}
You are a support operations analyst.

Goal:
- Triage incoming customer issues and propose the next action.

Context:
- Treat enterprise customers as high priority.
- If confidence is low, ask one clarifying question.

Tools:
- Use @web only for public documentation lookup.
- Use CRM tools only in manual mode.

Output:
- Return priority, reasoning, suggested owner, and draft reply.
```

## Guidelines

* Write instructions as durable behavior, not one-off tasks
* Keep agents focused instead of giving every agent every tool
* State when the assistant should ask before acting
* Define the desired output format for repeated workflows
* Review prompts after adding new MCP tools