> 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/making-a-great-vizzy-studio-app.md).
# Making a great vizzy studio app
A great Studio visualization starts with a clear prompt and gets better with small, specific refinements. Here are our best tips.
### Creating a good prompt
Your first prompt is the most important. Think about what exactly you want to achieve.
**Audience:** Who is this visualization for?
**Core views:** What's at its core? Think KPI cards, chart types, tables, maps, funnels or comparisons.
**Interaction:** Do you want to add filters, details on hover, or any quick actions?
An example of a good prompt, would be one like this:
> "Build a Tableau extension for **regional sales leaders** reviewing monthly performance. Put **three KPI cards at the top** for revenue, profit, and revenue versus target. Below them, show a **monthly revenue trend** and a ranked bar chart of regions by variance to target. **Add filters** for month, region, and customer segment. When a user selects a region, **show its top five products and a short plain-language summary of the performance.** Use a clean executive layout, currency formatting, and green or red only to show performance against target. Include a clear empty state when the current filters return no data."
{% hint style="info" %}
The create page has a **reference image** option, but Vizzy doesn't use the image yet. Describe the layout and styling you want in words instead.
{% endhint %}
### Optimize Your Vizzy Studio Extension
Your first prompt gives you a strong starting point. Next, refine it in the [workspace](/trulyp/vizzy-studio/the-studio-workspace.md) so it answers a clear business question, works with the right Tableau fields, and is ready for your users.
### Refine with small, specific requests
Use the **Vizzy** panel in the workspace to improve your visualization in place. Make one change at a time and review the result in the preview before moving on.
Good refinement requests describe both the desired outcome and the part of the extension that should change.
> **Example prompts**
>
> * "Make the primary KPI revenue versus target, with the variance shown underneath."
> * "Replace the table with a ranked bar chart of the five lowest-performing regions."
> * "Add a compact filter for segment and keep the chart visible without scrolling."
> * "Use a calm executive style with strong contrast and green only for positive performance."
> * "Add a short empty-state message when no marks are selected."
### Make precise visual adjustments
For small visual changes, use the element picker: the pointer button at the top of the **Live preview**, or **Pick** on the **Elements** tab.
Click an element, in this example the Sales number. Then choose whether to change only this **exact** element (only this number), or every **generic** element with the same style (here also the Profit and Profit ratio numbers).
Then adjust the **Text**, **Font size**, **Padding**, **Border radius**, **Text color** or **Background**, and click **Save**.
Use **Elements** for final polish, such as improving a heading, adding space around a KPI, or making a table header easier to read.
Use **Vizzy** instead when a change affects the extension's structure, logic, interactions, or data behavior.
### Test in Tableau and publish
Before you share your visualization, test it in a non-production Tableau workbook: see the checklist in [Use it in Tableau and Analytics](/trulyp/vizzy-studio/use-in-tableau-and-analytics.md#test-before-you-share).
> **Tip:** If a field is ambiguous, describe its business meaning in your prompt rather than relying only on its field name. For example, use **"monthly recurring revenue"** instead of **"value."**
When it's ready, **Save** your latest changes, check the **Live preview**, and **Publish** it if you want to use it in Analytics. **Download TREX** works at any time, also without publishing.
Saving changes to a published visualization unpublishes it until you publish it again, so the published version always matches what you reviewed. Happy building! 🎨
---
# 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/making-a-great-vizzy-studio-app.md?ask=&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.
