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

# Create a custom visualization

Every Studio visualization starts with a short description of what you want to see. Vizzy AI turns it into a working extension in a few minutes. Here's how.

### The Studio overview

Go to **Studio** › **Custom visualization**. You see all visualizations made in Studio, with a live thumbnail, their description and badges for their status (**Draft**, **Built**, **Published**), type (**Viz Extensions**) and source.

<figure><img src="https://2312557015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWbWxEBax8PKTjFYRLWgi%2Fuploads%2Fgit-blob-1958a49559fca7a6a68b9da2f227620252e6123d%2FStudio_Overview.png?alt=media" alt=""><figcaption><p>Studio › Custom visualization</p></figcaption></figure>

* Click a visualization, or its pencil, to open it in the [workspace](/trulyp/vizzy-studio/the-studio-workspace.md).
* Click the download icon to download its `.trex` file for Tableau.

### Describe your visualization

Click **Create new viz**.

{% stepper %}
{% step %}

### Write a short brief

Under **What should it show?**, describe your visualization like a creative brief, not a technical spec. Good prompts mention:

* **Audience**: who will use it?
* **Core views**: KPI cards, a chart type, a table, a map…
* **Interactions**: filters, details on hover, actions when someone clicks.

Need inspiration? Click one of the **Prompt ideas** to start from it: **KPI card with BAN and sparkline**, **Ranked bar chart with conditional colors** or **Writeback table with inline editing**.

<figure><img src="https://2312557015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWbWxEBax8PKTjFYRLWgi%2Fuploads%2Fgit-blob-a7c0052b906242b32bffb354ec6fa5ad09f19739%2FStudio_Create_Prompt.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Start building

Click **Start building** (or press ⌘ + Enter / Ctrl + Enter). The Vizzy panel opens and shows the progress: **Review prompt**, **Prepare draft**, **Generate renderer logic** and **Build preview**.

<figure><img src="https://2312557015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWbWxEBax8PKTjFYRLWgi%2Fuploads%2Fgit-blob-ddcf1405ff2e81c41fca41fb77bf974a79ae3e84%2FStudio_Building.png?alt=media" alt=""><figcaption></figcaption></figure>

Sometimes Vizzy asks a short question first, for example whether a form should write data or only show it. Simply answer in the panel, and it can start creating!
{% endstep %}

{% step %}

### Your visualization is ready

When Vizzy is done, the [workspace](/trulyp/vizzy-studio/the-studio-workspace.md) opens with a live preview of your new visualization. 🎉
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Reference image.** The create page lets you upload a screenshot as a reference for layout and styling (an image smaller than 8 MB). In the current version, Vizzy doesn't use the image yet, so describe the layout you want in your prompt.
{% endhint %}

Next: [refine your visualization in the workspace](/trulyp/vizzy-studio/the-studio-workspace.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.infotopics.com/trulyp/vizzy-studio/vizzy-studio-basics.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.