> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mythos.new/introduction/getting-started/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server.

# Build your first app

> Start with one clear prompt, review the working preview, make a focused change, and publish when the result is ready.

This guide takes you from an idea to a live first app. You will build one focused page for a fictional
coffee roaster, review it in Preview, make one improvement, and publish it.

> **Note**
>
> Start by signing in to an account with access to your workspace. This guide
> begins at the dashboard. See [Signing in and accounts](/introduction/sign-in)
> if you need help getting there.

## Before you start

Have three things ready:

* The outcome you want, such as a landing page, portfolio, or dashboard.
* The content or sections that matter most.
* Enough balance for the action. [Credits and usage](/introduction/credits-and-usage) explains the
  usage-based Build costs, limits, and refund behavior.

You do not need a finished specification. A clear audience, purpose, and visual direction are enough
for a useful first result.

## Build the first version

#### Start a project

Open the dashboard and use the main composer. For this guide, enter:

```text
Build a one-page website for North Slope, a neighborhood coffee roaster.
Include a hero, featured beans, a short wholesale section, opening hours,
and contact details. Use a warm, minimal visual style with generous spacing.
```

This prompt names the business, the page structure, and the desired feel while leaving room for
Mythos to make sensible design decisions.

#### Choose Build or Plan

Choose **Build** when the brief is ready and you want to go straight to a result. Choose
**Plan** when you want Mythos to ask focused questions and prepare an editable plan before it
changes the project. See [Plan mode](/features/plan-mode).

#### Follow the progress

Mythos shows progress in the conversation while it creates and checks the app. Keep the workspace
open; there is no need to resend the prompt while the run is active.

#### Review the preview

When the result card appears, inspect the page as a visitor would. Check the headline, section
order, links, and the layout at more than one viewport size. A delivered result becomes the
current project version.

## Ask for one improvement

You do not need to repeat the original brief. Describe the exact section and the change you want:

```text
In the featured beans section, add three roast cards with a short tasting note
and price for each. Keep the existing warm palette and spacing.
```

Review the updated preview when the edit finishes. If the change moved in the wrong direction, use
[Version history](/features/version-history) to inspect an earlier version or revert safely.

> **Tip**
>
> Focused follow-ups are easier to verify. Ask for one coherent outcome at a
> time, then look at the result before sending the next request.

## Publish when it is ready

Choose **Publish** in the workspace, review the project name and URL, and confirm. Publishing uses the
latest delivered version; later workspace edits do not change the live site until you publish again.

> **Warning**
>
> A published site is public on the internet. Remove private information and
> test the visible content before you confirm.

## Continue from here

* [Dashboard and workspace](/introduction/dashboard-overview) — learn where each part of the project
  lives.
* [Writing good prompts](/prompting/writing-good-prompts) — turn a rough idea into a useful brief.
* [Managed Supabase backend](/integrations/supabase) — add saved data, uploads, or app authentication.
* [Publishing](/publishing/publish) — understand updates, public URLs, and publish states.

> Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.