> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/interactive-demo/readme/quick-start.md).

# Quick Start

Getting set up on Arcade.

## 🕹 How to get started with Arcade.

Navigate through the Arcade below for tips on how to get started and make the most of the tool. 

***

{% @arcade/embed flowId="9VaLqDRYKGi3qpvrOj79" url="<https://app.arcade.software/share/9VaLqDRYKGi3qpvrOj79>" %}

With [the Chrome extension](https://chromewebstore.google.com/detail/arcade/gagidkjllbdgggpboolfmmdpeagghjlm), building and updating an Arcade is *much* easier and faster. You just focus on the story, and we handle the rest!

**What does it do?**\
With the extension, you can resize your screen, record an interactive demo, take a screenshot to add to an existing Arcade, or record a video with a personal touch.

**How does it work?**

The Arcade Chrome Extension captures all your actions, including clicks, scrolls, and typing, and saves them as video snippets and screenshots for easy editing.

👉 [**Download it here**](https://chrome.google.com/webstore/detail/arcade/gagidkjllbdgggpboolfmmdpeagghjlm)

***

## How to create great Arcades.&#x20;

A three-part collection of (short!) Arcades designed to teach you how to build your first demo.&#x20;

### Part 1: How to Record&#x20;

{% @arcade/embed flowId="LHDkrd4YjpLp3EoCohVl" url="<https://app.arcade.software/share/LHDkrd4YjpLp3EoCohVl>" %}

### Part 2: How to Edit&#x20;

{% @arcade/embed flowId="ebSvOAhxZreGAwCORNsR" url="<https://app.arcade.software/share/ebSvOAhxZreGAwCORNsR>" %}

### Part 3: How to Publish&#x20;

{% @arcade/embed flowId="dlVC7VbMWrsWX61VXrui" url="<https://app.arcade.software/share/dlVC7VbMWrsWX61VXrui>" %}


---

# 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.arcade.software/kb/interactive-demo/readme/quick-start.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.