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

# Overview

The Flow Screen Components tutorials live in the Flow documentation.

The step by step tutorials for Flow Screen Components live in the Flow documentation, next to the component reference they build on.

{% hint style="info" %}
[**Browse the Flow tutorials**](https://docs.avonnicomponents.com/flow/tutorials/projects)

Account management, bulk edit on the Data Table, the interactive contact list, router mode navigation, the marketing campaign calendar and the rest, all in one place.
{% endhint %}

Looking for a project rather than a tutorial? The gallery has twenty seven of them, grouped by the kind of screen they produce: [Browse all projects](https://docs.avonnicomponents.com/projects/use-cases/overview.md).


---

# 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.avonnicomponents.com/projects/flow-components/overview.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.
