> 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.md).

# App Preference Features

### What’s an “App” in Riff?

An **app** is a contained project with a **frontend** (UI) and a **backend** (APIs, jobs). The agent plans, edits code, runs, and deploys this app inside a single workspace.

* **Frontend:** pages, components, copy, and styles the agent can generate or modify.
* **Backend:** API routes, data access, integrations, schedules, and background work.

> Think of App Preferences as the “operating brief” the agent reads before it plans and writes code for this app.

### What are App Preferences?

**App Preferences** are high-level settings that tell the agent how to approach work in this specific app. They don’t change production by themselves -they guide the agent’s planning and execution when you ask it to build, fix, or enhance something.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>Agent Behaviour</strong></td><td>Guardrails and defaults for how boldly or cautiously the agent operates.</td><td><a href="/archive/features-legacy-databutton-web-app-builder/app-preference-features/agent-preferences.md">Agent Preferences</a></td></tr><tr><td align="center"><strong>Custom Instructions</strong></td><td>Plain-language context, constraints, and goals for this app</td><td><a href="/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-custom-instructions.md">App Custom Instructions</a></td></tr><tr><td align="center"><strong>Design</strong></td><td>Visual direction and UX tone the agent should follow when touching the UI.</td><td><a href="/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-design.md">App Design</a></td></tr><tr><td align="center"><strong>Pitch, Description &#x26; Audience</strong></td><td>Provide context that helps the AI agent understand your application better.</td><td><a href="/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-management.md">App Management</a></td></tr></tbody></table>

###


---

# 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.riff.ai/archive/features-legacy-databutton-web-app-builder/app-preference-features.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.