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

# Learning resources

## Guide

This guide serves as an overview, outlining Vico’s core features and providing usage guidance.

## API reference

[The API reference](https://api.vico.patrykandpatrick.com/) describes every public API element. On each of the guide’s pages, the first mention of any class, function, or property is a link to the corresponding page in the API reference. Follow these links to learn about all the features of the APIs described, as well as more APIs.

## Sample app

Included in the repository is [a sample app](https://github.com/patrykandpatrick/vico/tree/stable/sample), which consists of [sample charts](https://github.com/patrykandpatrick/vico/tree/stable/sample/shared/src/commonMain/kotlin/com/patrykandpatrick/vico/sample/charts).

The sample app is the most practical Vico learning resource, recommended for beginner and advanced users alike. Sample charts are referenced throughout the guide.

Follow the links above to view the code on GitHub. For Android, you can also [download the APK](https://github.com/patrykandpatrick/vico/releases/download/v3.3.1/android-sample-debug.apk). To work with the sample app locally, clone the repository, switch to the right tag, open the project in Android Studio, and navigate to the [`sample`](https://github.com/patrykandpatrick/vico/tree/stable/sample) module.

```sh
git clone https://github.com/patrykandpatrick/vico
cd vico
git checkout v3.3.1
```


---

# 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://guide.vico.patrykandpatrick.com/learning-resources.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.
