> ## Documentation Index
> Fetch the complete documentation index at: https://docs.morada.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Turn ideas into visual experiences

> Create simulators, pages, prototypes, reports, and explanations you can open and explore in chat. No coding needed.

You can ask for more than a text response. Morada OS also creates files that open like a small web page: you can click, change values, filter information, and explore an idea.

This helps when **seeing and trying something is more useful than reading about it**. Instead of explaining five scenarios in a long message, for example, you can open a simulator and change the assumptions during a meeting.

You do not need to know how to code or what a file format is called. Ask **"explain this to me visually,"** **"create a simulator,"** or **"show me an idea for this page."** The assistant may also choose a visual presentation when it helps.

## Choose what you need to do

Each recipe below includes a complete file generated by Morada OS, a prompt you can copy, and ideas for adjustments. The examples use fictional data; the result in chat will depend on your request.

<Note>The examples were generated in test conversations with Portuguese prompts, so their content remains in Portuguese. The prompts in this guide are English translations. Use **Enlarge example** to explore each complete file or **Download original file** to keep it.</Note>

<CardGroup cols={2}>
  <Card title="Create a simulator" icon="calculator" href="/morada-os/en/use-cases/build-a-miniapp">
    Change lead volume and conversion to explore a sales target without repeating the calculations.
  </Card>

  <Card title="See a page concept" icon="window-maximize" href="/morada-os/en/use-cases/draft-a-landing-page">
    See an idea for a promotional page before investing in building the website.
  </Card>

  <Card title="Test an app prototype" icon="mobile-screen-button" href="/morada-os/en/use-cases/try-an-app-mockup">
    Move between screens and discuss the flow with your team before developing the app.
  </Card>

  <Card title="Build an interactive report" icon="chart-column" href="/morada-os/en/use-cases/build-an-interactive-report">
    Switch periods, compare results, and explore questions with the numbers in view.
  </Card>

  <Card title="Explain a plan visually" icon="diagram-project" href="/morada-os/en/use-cases/explain-a-plan-visually">
    Organize the steps and show how a schedule change affects the rest of the plan.
  </Card>
</CardGroup>

## From request to result: how to open it

<Steps>
  <Step title="Describe your goal in the main chat">
    Choose a recipe and adapt the prompt. Say who it is for, what information to include, and what you want to change or explore. You can start with just an idea or attach reference material.
  </Step>

  <Step title="Click the file card">
    When finished, the assistant delivers a file with a name ending in **.html**, such as **interactive-plan.html**. **Click that card in the conversation** to open the preview. You do not need to copy code or install anything.
  </Step>

  <Step title="Explore and expand">
    Use the file's buttons, fields, and filters in the **Visualização** (Preview) tab. In the header, the **Expandir visualização** (Expand preview) icon fills the window with the content, without the code tab. **Restaurar tamanho** (Restore size) returns to the previous view; the values you entered remain while the preview is open.
  </Step>

  <Step title="Download or ask for an adjustment">
    The **Baixar arquivo** (Download file) icon in the header saves the HTML to your computer. To change the content, continue the conversation: "add a filter by development" or "make the explanation simpler." Open the new file the assistant delivers.
  </Step>
</Steps>

<Tip>
  The **Código** (Code) tab shows how the file was built, but you do not need to use it. Ask the assistant for changes in the conversation.
</Tip>

## A simple way to ask

```text wrap theme={null}
I want to help [audience] [understand or do something]. Build an interactive page with [information to include] and let me [change values, filter, move through steps]. Use the data below, make it comfortable to use on a phone, and deliver it as a file I can open in this conversation.
```

**Choose an interaction with a purpose.** A filter helps compare regions; a schedule control helps discuss delays. If a short answer solves the problem, it does not need to become a page. If you need a presentation, PDF, or spreadsheet, ask for that format.

## What to expect from this experience

* **It works with the content inside the file.** Ask for everything it needs to work to be included in the file. Elements loaded from other websites, such as images and fonts, do not load in the preview and may leave an imported file incomplete.
* **It is a local experience.** A simulator calculates and a prototype switches screens; this does not connect a CRM, submit a form, or publish a website. Real integration or publication takes additional work.
* **Changing a field does not save a new version of the file.** Closing and reopening the preview may reset the values. Downloading saves the original file, not changes made through its controls. To keep a scenario, ask the assistant for a new file with those values already set.
* **Check the content before using it.** Verify the data, calculations, and assumptions. A polished report does not replace checking the source.

<Accordion title="Why does the file name end in .html?">
  HTML is the format used to store the page and its interactions. You do not need to ask for it by its technical name, open the code tab, or install a program: just click the card. If you already have an HTML file from elsewhere, you can also attach it in the main chat to preview it. If something is missing, ask for a version with the necessary elements included in the file itself, where possible.
</Accordion>