Prompt library

Ready-to-use prompts, tuned to how the agent hears best. Copy one, swap the specifics for yours, and go. Each carries a note on why it is shaped the way it is; the habits behind the shapes are in the prompting guide.

Starting an app

A booking app

Build a booking app for a hair salon called Salt Studio. Customers pick a service (cut $60, color $140, blowout $45), then a date and a free 30 minute slot on weekdays 9 to 5, and leave their name, phone, and email. I need a page where I can see the day's bookings in order. Clean and calm, sage green and cream.

Names, prices, hours, and both sides of the app (customer and owner) are stated, so nothing load-bearing is guessed.

A client portal

Build a client portal for my bookkeeping practice. Clients sign in and see only their own documents and a status card for their current month. I can see every client, upload documents to a client, and mark their month as in progress or complete. Professional and quiet, navy and white.

The privacy sentence ("only their own") is the most important line; it becomes a real database rule.

An internal tracker

Build an inventory tracker for a coffee roastery. Items have a name, category (beans, packaging, supplies), quantity, and reorder level. Anyone on the team can adjust quantities; a red badge shows anything at or below its reorder level. Start it with ten realistic sample items.

Asking for sample data up front means the first preview already looks like the real thing.

A landing page

Build a landing page for a meal prep service called Sunday Chef. Hero with a strong headline about saving weeknights, three plan cards ($89, $129, $169 per week) with a "get started" button each, a how-it-works section in three steps, six testimonials, and an email signup form that stores addresses so I can export them. Appetizing and warm; here is our logo.

Every section is enumerated, and the signup form says what happens to the data.

A marketplace-style directory

Build a directory of local wedding vendors. Vendors have a name, category, price range, photo gallery, and description. Visitors browse and filter by category without signing in; vendors sign in to create and edit only their own listing. I approve new listings before they appear.

Three roles (visitor, vendor, you) each get one sentence. The approval step is stated, not assumed.

Adding to an app

A sign-in wall

Add sign-in to the app. Anyone can view the home page, but the dashboard and everything under it requires an account. Use email code sign-in and Google.

Says which pages are public, which are walled, and which providers to enable.

An admin page

Add an admin page at /admin that lists every order with a status I can change (new, shipped, done). Only admins can open it; hide the link from everyone else. Make my account an admin.

Role-gated pages are a solved pattern; naming the role makes the gate real, not cosmetic.

Payments

Add a checkout to the pricing page using my connected Stripe account. The three plans should charge the prices already set in Stripe. After payment, show a thank-you page and mark the user's account as paid.

Prices live in Stripe, so the prompt points there instead of retyping them. The Stripe guide has the full recipe.

A confirmation email

When a booking is completed, email the customer a confirmation with the service, date, time, and our address, using Resend. Subject: "You're booked at Salt Studio". Friendly, short, signed "The Salt Studio team".

Exact subject and tone included, so the email reads like you wrote it.

A notification to your team

When a new order comes in, post to our #orders Slack channel: customer name, total, and what they ordered.

Trigger, destination, and message contents in one line each.

An analytics event

Track a "signup_completed" analytics event when a user finishes creating an account, and a "checkout_started" event when they open the payment page.

Named events make the analytics conversion view meaningful.

Importing your data

I attached our client list as a CSV. Create a clients table from it that only signed-in team members can see, and build the client page around the real columns.

Attaching the file beats describing it; the privacy phrase rides along. More in data import.

Changing an app

A redesign that keeps what works

Restyle the whole app: deep forest green as the brand color, off-white background, a serif for headings. Do not change any functionality or page structure, only the look.

The "do not change" sentence is what makes broad restyles safe to ask for.

A focused layout change

On the products page only: make the grid three columns on desktop, put the price under the name instead of beside it, and remove the category badge from the cards.

Scoped to one page, three concrete changes, nothing about the rest of the app.

Tightening copy

Rewrite the home page copy for busy parents deciding in ten seconds. Headline under eight words, one sentence per section, benefits not features. Keep the layout exactly as it is.

Audience plus constraints produces far better copy than "make the text better".

Mobile behavior

On phones: the sidebar becomes a bottom tab bar with Home, Orders, and Settings; tables scroll horizontally instead of shrinking; buttons stay at least full thumb size.

Describes the phone experience concretely instead of asking to "make it responsive".

Before you launch

Review the app as a first-time visitor on a phone: list anything confusing, broken, or unstyled, but do not change anything yet.

The "do not change anything yet" turns the agent into a reviewer, so you decide what is worth fixing. Plan mode is this habit as a switch.

Frequently asked

Should I paste these word for word?

Swap every specific (names, prices, colors) for yours first; the specifics are what make them work. The shape is the part to keep.

Can I combine several prompts into one message?

Combine what belongs together (an app and its sign-in rules), and split what does not (a new feature and a redesign land better as two turns).

What if the result is close but not right?

Say what is off, specifically, in a follow-up: "the slots show weekends, they should not". Short corrections beat re-sending a longer version of the original prompt.