> For the complete documentation index, see [llms.txt](https://help.imagine.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.imagine.art/imagine-computer/build.md).

# Build

Build is a part of Computer that generates working websites and web apps from a plain language prompt. Instead of a static mockup, Build writes real, responsive code and shows you a live preview as it works, so what you see is what actually runs.

You can start from a blank prompt or from a ready made template, and refine everything afterwards by chatting, the same way you work with the rest of Computer. Build is good for portfolios, landing pages, storefronts, simple games, and internal tools or dashboards, without needing to write any code yourself.

Build also supports connecting real services. Add GitHub to own and sync your code, Supabase to give your app a real backend, Figma to bring in existing designs, or Shopify to power a real storefront.

<figure><img src="/files/UK7zbWAU66bVlPSGw2Iu" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.imagine.art/imagine-computer/build.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.