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

# Scoping and iterating on your app

> Build in phases so every step stays fast and reliable

Bilt works best when you build in small steps instead of asking for everything in one message. A smaller, focused request is easier for the AI to get right than one big, complex prompt.

## A good order to build in

<Steps>
  <Step title="Structure first">
    Ask for the main screens and how you move between them. "Build a meal planning app with a weekly calendar and a recipe screen."
  </Step>

  <Step title="One feature at a time">
    Add features one by one. "Add a grocery list that fills in from selected recipes."
  </Step>

  <Step title="Then design">
    Once it works, refine the look. "Use a teal and white color scheme with bottom tab navigation."
  </Step>

  <Step title="Then the backend">
    Add saving and sign-in last. "Add sign-in so users can save their meal plans."
  </Step>
</Steps>

## Do

* **Name the screen you're changing** — "On the recipe screen, add a button below the ingredients."
* **Make one change per message.**
* **Build on what's there** — Bilt remembers the conversation.

## Avoid

* **Repeating earlier instructions** — it makes each request larger and slower.
* **Packing many features into one message.**
* **Giving conflicting instructions** in the same message.

<Note>
  When a chat gets very long, start a new project for the next phase. Your current app stays saved — and each project keeps its own focused history.
</Note>

For prompt wording, see the [Prompting Guide](/docs/guides/prompting).