> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-custom-instructions.md).

# App Custom Instructions

### How to Access

Click on your application name in the top left corner of your workspace, then select Settings > Custom Instructions

### When to Use

* Working on a project with specific requirements or constraints
* Need the agent to follow particular coding standards for this app
* Want different behaviour for different projects

### Best Practices

* Recommended length: 50-500 characters
* Be specific about what makes this project unique
* Include any domain-specific terminology or business logic

#### Examples

> "This is a healthcare app. Always prioritize HIPAA compliance and patient data security."

> "Use TypeScript strict mode. Prefer functional components. Follow our company's design system."

> "This app targets non-technical users. Prioritize simple UI and clear error messages."


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.riff.ai/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-custom-instructions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.