> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/design/design-overview.md).

# Design Overview

## **What the Design app does**

The Design app is where you build and evolve the admin experience. It covers the full loop from screen layout, to API wiring, to data shape, so you can ship UI changes fast without coupling them to backend code releases.

<figure><img src="/files/2lP6ZEbKedZvn9y30zog" alt=""><figcaption><p>Design App</p></figcaption></figure>

## **Core Design capability areas**

Design capabilities fall into three main areas:

* **User Interface:** Design apps, screens, navigation, and interaction patterns for admins.
* **API Mapping:** Connect UIs to backend endpoints via Sources and environment settings.
* **Data Schema:** Define and govern the structure of records used across UIs and APIs.

## **How Design components work together**

In practice, you usually touch all three. You define a UI (listers, editors, widgets), point it to a Source (list/get/create/update/delete endpoints), and align the fields with a Schema so validation and defaults stay consistent across screens. That separation keeps screens reusable and makes it easier to change API routes or data models without rebuilding everything from scratch.


---

# 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.rierino.com/design/design-overview.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.