> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/build-and-improve/overview/instructions-and-behaviour.md).

# Instructions and behaviour

Configure the organisation, Project and task-level instruction layers that shape how the Agent approaches work.

Set the Agent's general behaviour before encoding individual tasks.

## Project instructions

In the current product, **Project description is the Project-level instruction channel**. It is injected into the Agent at the start of a session. Use it to explain both what the Project is for and durable behavioural rules that should apply across the Project.

The same Settings surface also contains **Agent tone**, which changes response style rather than business rules, plus current Project controls such as organisation branding.

![Control → Settings → General with Project title, description, Agent tone and branding controls.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-6a9aebc780e36a6e4dace04fd7aaf4953dbc11df%2Fsettings-agent-current.png?alt=media)

A practical instruction stack is:

1. **Organisation and user context** — broad background captured outside the Project.
2. **Project description** — persistent Project purpose and cross-task behavioural direction.
3. **Skills** — task-specific methods, checks and tools for recurring work.
4. **Session context** — the current task, attachments, evidence and conversation.

Do not duplicate the same rule across all of these layers. Put it at the narrowest durable level that fits.

## Agent responsibility

Write down what the Agent is responsible for in business language. For example:

> Handle incoming sales-order questions for the Benelux order desk. Use the connected ERP for current customer and order facts. Do not invent product mappings or commercial terms. Ask when a requested customer or product cannot be resolved confidently.

A good Project-level setup usually establishes the operational area the Agent owns, authoritative sources, important boundaries, business terminology and what a satisfactory result looks like.

## Skill-specific instructions

Rules that only apply to one recurring task belong in that Skill. Maintained business facts belong in Tables, Knowledge or the source system rather than being copied into instructions.

After changing Project-level instructions, rerun representative work because the change can affect many sessions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/build-and-improve/overview/instructions-and-behaviour.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.