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 prompt is your design tool. Fabricate’s AI agent plans, generates, and previews a full-stack app from what you write — so a clear prompt is the difference between a rough sketch and a strong starting point. This page gives you a repeatable framework for writing prompts that work.
You don’t need technical language. Fabricate already knows it’s building React, Tailwind, a Cloudflare Workers backend, and a D1 database. Describe the product, not the stack.

​
The Five Principles

Be specific

Name the screens, the data, and the actions. Vague prompts produce vague apps.

Describe the outcome

Say what the user should be able to do and see — not how to code it.

One feature at a time

Start with a focused core, then add features in follow-up messages.

Show references

Attach images or name a layout pattern you want the app to echo.

​
1. Be specific

The agent fills gaps with assumptions. Every detail you leave out is a decision made for you. Spell out the screens, the data each screen holds, and what users do there. 
Build me a fitness app.
The second prompt names three screens, the exact fields, and the auth requirement. The agent has far less to guess.

​
2. Describe the outcome and the user

Tell Fabricate who the app is for and what success looks like for them. Audience context shapes layout, language, and defaults — an app for accountants looks different from one for teenagers. 
Add a dashboard with some charts.
A useful sentence to include: “The main thing a user should be able to do is ___.” It forces the prompt to have a point.

​
3. Give one feature at a time

It’s tempting to describe the entire product in your first message. Resist it. Fabricate builds in phases, and a focused first prompt produces a cleaner foundation you can then extend. Start with the core, confirm it works in the live preview, then layer features through follow-up messages.
1

First prompt: the core

“Build a recipe-saving app. Users can add a recipe with a title, ingredients, and steps, and see all their recipes in a list.”
2

Follow-up: one addition

“Add a search bar that filters the recipe list by title.”
3

Follow-up: the next addition

“Add categories to recipes and let users filter the list by category.”
This gives you more control, makes it obvious which change caused which result, and is easier to revert if a step goes wrong. See Iterating on Your App for the full follow-up workflow.

​
4. Provide examples and references

Words describe function well but visuals describe feel better. You can attach images to a prompt — screenshots, sketches, mockups, or a photo of a whiteboard — and the agent will use them as a reference. You can also name a familiar layout pattern as shorthand. 
Make it look nice and modern.
Reference a pattern for its structure (“a card grid like a typical marketplace listings page”), not to clone a specific brand. Describe the pattern you want and Fabricate will build an original version.

​
5. Iterate — the first build is a starting point

No prompt produces a finished product in one shot, and that’s by design. Fabricate is built for iteration: a live preview updates as it builds, follow-up messages refine the result, version history lets you revert to an earlier snapshot, and Discuss Mode lets you plan before you build. Treat your first prompt as a strong opening move, not the whole game. When something isn’t right, describe it concretely: 
The dashboard is wrong.

​
A Prompt Checklist

Before you send a prompt, run through this:
List the main pages or views — home, dashboard, detail page, settings. The agent uses these to plan the app’s structure.
For each thing users create or view, name its fields. “A task has a title, due date, and priority” is far more actionable than “tasks.”
Audience drives tone, density, and defaults. One sentence about the user goes a long way.
If your prompt has five major features, build the most important one first and add the rest as follow-ups.
A sketch or screenshot communicates layout faster than a paragraph. Use one when the look matters.
Avoid bundling unrelated requests into one message — “add a calendar, fix the login bug, and change all the colors.” Each gets less attention, and if one goes wrong it’s harder to isolate. Send them as separate messages.

​
What’s Next?

Prompt Examples

A library of strong starter prompts grouped by app type.

Iterating on Your App

Refine your app with follow-up prompts, version history, and the Prompt Queue.

Prompting by Persona

Tailored prompting tips for founders, developers, designers, and more.

Build Mode

See how Build Mode turns your prompts into code.