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

# Prompt Chips

> Suggested starter prompts that help you begin a project or find your next idea.

Prompt chips are suggested prompts shown on the prompt composer. They give you a running start — a tap puts a ready-made idea into the composer so you can build without staring at a blank box.

## What Prompt Chips Are

Each chip is a short, concrete prompt suggestion. They appear on the composer to spark ideas, whether you're describing a brand-new app or thinking about what to add to one you've already started.

<Tip>
  Stuck on how to phrase a request? A prompt chip shows you the kind of clear, specific description that gets the best results from the AI agent.
</Tip>

## Using a Prompt Chip

<Steps>
  <Step title="Pick a chip on the composer">
    Browse the suggested chips and choose one that's close to what you have in mind.
  </Step>

  <Step title="Edit it to fit your idea">
    The chip's text drops into the composer. Tweak the wording — change the app's purpose, name, or features — so it matches what you actually want.
  </Step>

  <Step title="Send it">
    Submit the prompt and Fabricate generates a blueprint, then builds your app in phases.
  </Step>
</Steps>

## Starting a New Project

When you're beginning from scratch, a prompt chip gives you a complete starting point to react to. It's often easier to refine an existing idea than to invent one from nothing — start with a chip, reshape it, and send.

## Extending an Existing Project

Prompt chips aren't just for the first prompt. When you're partway through a build and wondering what's next, they can suggest features or improvements worth adding. Use a chip as a jumping-off point, then describe how it should work in your specific app.

<Note>
  Prompt chips are suggestions, not limits. You can always ignore them and write your own prompt — anything you can describe in plain English, Fabricate can build.
</Note>

## Writing Strong Prompts

Whether you start from a chip or your own words, specific prompts produce better results:

* **Say what the app is for** — "a habit tracker for daily routines" beats "an app."
* **Name concrete features** — pages, fields, and actions you expect to see.
* **Iterate** — you don't need the perfect prompt up front. Build, review the [Live Preview](/build/preview), and refine with follow-up prompts.

## Where to Go Next

<CardGroup cols={2}>
  <Card title="Build Overview" icon="hammer" href="/build/overview">
    See how prompts turn into a deployed app.
  </Card>

  <Card title="Live Preview" icon="eye" href="/build/preview">
    Watch your app build as you iterate.
  </Card>
</CardGroup>