Skip to main content

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.

The best way to learn Fabricate is to watch one app come together end to end. In this guide you’ll build a team task tracker — a small, realistic app — from the first prompt all the way to a live URL.
Follow along by typing the prompts into your own Fabricate project, or just read through to see how the workflow flows. The same pattern works for any app you have in mind.

​
1. Write the first prompt

Start on the home screen and describe the whole app in plain English. Cover the core feature, who uses it, and anything that matters to you up front — like authentication.
1

Describe what you want

Build a team task tracker. Users can sign up and log in, create
tasks with a title, description, due date, and status (To Do,
In Progress, Done), and see all tasks on a board grouped by status.
Each user only sees tasks from their own account.
2

Send it

Fabricate reads your prompt and turns it into a build plan.
Mention authentication, the main data model, and the primary view in your first prompt. These are expensive to bolt on later, so it pays to be clear early.

​
2. Review the blueprint

Before writing code, Fabricate generates a blueprint — a plan describing the pages, data model, and features it intends to build. For the task tracker, expect something like:
  • Auth — sign up, log in, and per-user data isolation
  • Database — a tasks table linked to users
  • Board page — tasks grouped into To Do / In Progress / Done columns
  • Task editor — create and edit tasks in a dialog
Read it over. If something’s missing or wrong, say so before the build starts — it’s the cheapest moment to course-correct.

​
3. Watch the first build

Fabricate builds in phases and the live preview runs as it goes:
1

Structure and database

The app skeleton, routes, and your D1 schema are created.
2

Auth and API

Sign-up, log-in, and the API routes for tasks are generated.
3

UI

The board, columns, and task editor are built with Tailwind and shadcn/ui.
4

Preview ready

Sign up inside the preview and create a task — it’s fully functional.

​
4. Iterate with follow-up messages

Your first build is a starting point, not the finish line. Refine it one focused change at a time: 
Add a priority field to tasks (Low, Medium, High) and show a colored
dot for priority on each task card.

Add a search bar above the board that filters tasks by title in real time.

Make the board responsive — stack the three columns vertically on
mobile screens.
One change per message gives you cleaner results and easier troubleshooting. If a change looks wrong, you can revert that message from version history and try again.

​
5. Polish and deploy

When the app does what you need, do a final pass:
  • Click through every flow in the preview — sign up, create, edit, filter.
  • Use the device-size toggle to check mobile layout.
  • Fix anything off with one more prompt, e.g. "The due date isn't showing on task cards — display it under the title."
Then ship it:
1

Click Deploy

Hit Deploy in the top right of the editor.
2

Get your URL

Your app goes live on Cloudflare’s global network at a yourapp.fabricate.build URL.

​
Keep going

Prompting Best Practices

Write prompts that get the result you want the first time.

Working with Images

Use screenshots and mockups to guide the build.

Design Fixes

Sharpen the look and feel of your app.

Troubleshooting

Resolve common issues as you build.