Skip to main content
The fastest way to learn good prompting is to read good prompts. Each example below is a complete, copyable starting prompt for a different kind of app, with a note on why it works. Copy the one closest to your idea, swap in your own details, and send it.
These are first prompts — they describe a focused core. After your app builds, refine it with follow-ups. See Iterating on Your App.

​
SaaS Dashboard

Build a SaaS analytics dashboard for marketing teams. After signing up,
users land on a dashboard with four summary cards (visitors, sign-ups,
conversion rate, revenue) above a line chart of daily visitors for the
last 30 days. A "Campaigns" page lists campaigns in a table with name,
channel, spend, and conversions, with a button to add a new campaign.
Include email-and-password authentication so each user sees only their
own data. Clean, professional, light theme with one blue accent color.
Why it works: it names every screen, the exact metrics and table columns, the auth model, and a clear visual direction — so the agent isn’t guessing at structure or style.

​
Marketplace

Build a two-sided marketplace for handmade furniture. Sellers can list
an item with a title, description, price, category, and photo. Buyers
browse a homepage grid of listings with search and a category filter,
and open a listing detail page with the full description and a "Contact
seller" button. Users sign up as either a buyer or a seller. Sellers get
a simple dashboard showing their active listings. Use Stripe for buyers
to pay for an item directly on the listing page.
Why it works: it defines both sides of the market, the listing data model, the core browse-and-buy flow, and the payment method — the essentials of a marketplace without over-scoping.

​
Booking App

Build an appointment booking app for a hair salon. Visitors pick a
service from a list (each service has a name, duration, and price),
choose an available time slot on a calendar, and enter their name and
email to confirm. The salon owner logs in to an admin page that lists
all upcoming bookings by date and lets them block off unavailable times.
Send a confirmation message on screen after a booking is made.
Why it works: it separates the customer flow from the owner flow, specifies what data a service and a booking carry, and keeps the first version to one location — easy to extend later.

​
Internal Tool

Build an internal tool for our support team to track customer issues.
Team members log in and see a table of issues with title, customer name,
priority (low/medium/high), status (open/in progress/closed), and
assignee. They can add a new issue, edit an existing one, and filter the
table by status and assignee. Add a simple board view that groups issues
into columns by status. Keep it dense and functional — this is a daily
work tool, not a marketing page.
Why it works: it states the audience and the “dense and functional” intent up front, enumerates every field and its allowed values, and names two views (table and board) so the agent plans for both.

​
Landing Page

Build a landing page for a productivity app called Focusly. Sections,
top to bottom: a hero with a headline, subheadline, and "Get started"
button; a three-column features section; a pricing section with three
tiers; a short FAQ; and a footer. Modern and minimal with a dark theme
and a green accent. The "Get started" button scrolls to the pricing
section. No backend needed — this is a marketing page only.
Why it works: it lists the page sections in order, gives a precise visual direction, defines the one interaction, and explicitly says no backend — so the agent builds a focused static page.

​
Portfolio Site

Build a personal portfolio site for a freelance illustrator. Pages: a
home page with a short intro and a grid of featured work; a projects
page showing all work as a filterable gallery (filter by type:
editorial, branding, character design); an about page with a bio and
contact email; and a simple contact form. Warm, editorial feel with
large images and generous spacing. Make the project grid the visual
centerpiece.
Why it works: it names every page, the gallery’s filter categories, and the visual priority (“centerpiece”), giving the agent a clear hierarchy to build around.

​
Productivity App

Build a personal task manager. Users sign up and create tasks with a
title, optional notes, due date, and priority. The main screen shows
today's tasks and overdue tasks in two sections. A separate "All tasks"
view lists everything with filters for priority and completion status.
Checking a task marks it complete. Keep the interface fast and
keyboard-friendly with a quick "add task" input always visible at the top.
Why it works: it covers the task data model, two clearly-defined views, the core complete-a-task interaction, and a usability goal (“fast and keyboard-friendly”) that shapes the layout.

​
Slide-Deck App

Build a pitch-deck presentation for a startup called GreenRoute, a
carbon-tracking app for delivery fleets. Ten slides: title, problem,
solution, product demo, market size, business model, traction,
competition, team, and a closing call-to-action. Modern and confident
with a dark background, a green accent, and bold headlines. Keep each
slide to a headline and a few short supporting points.
Why it works: Fabricate can build slide-deck apps as well as web apps. This prompt lists every slide in order, gives a consistent visual direction, and sets a “headline plus a few points” rule so slides stay clean.

​
Adapting These Prompts

To reshape any example for your idea:
1

Swap the domain

Replace the subject — “hair salon” becomes “dentist,” “handmade furniture” becomes “vintage cameras.” The structure carries over.
2

Adjust the data fields

Change the listed fields to match what your users actually create and view.
3

Set your own visual direction

Replace the theme and accent color, or attach a reference image instead.
4

Trim to your true core

If a section isn’t essential to the first build, cut it and add it as a follow-up later.
Not sure which features belong in the first build? Paste your draft prompt into Discuss Mode and ask, “What’s the smallest version of this worth building first?” It’s free.

​
What’s Next?

Prompting Best Practices

The framework behind every prompt on this page.

Iterating on Your App

Turn a strong first build into a finished app.

Prompting by Persona

Prompting tips tailored to what you’re building.

Quickstart

Build and deploy your first app end to end.