Write better prompts
Get the result you want: name the people, the job and the screens, change one thing at a time, and say what to keep.
Updated Oct 18, 2026
A first brief
Cover the audience, the main job, the first screens and the tone.
A booking app for a small yoga studio. Members browse this week's classes,
book a spot, and see their upcoming bookings. Screens: class schedule by day,
class detail with instructor and spots left, my bookings, and profile.
Calm and airy, with a soft sage accent. Email sign-in.Follow-ups
Change one thing at a time and say what to leave alone.
| Instead of | Try |
|---|---|
| Make it better. | On the class detail screen, move the Book button to a sticky bar at the bottom and show spots left next to it. |
| Fix the design. | The schedule cards feel cramped. Add more space between cards and make the class time larger than the title. |
| Add payments. | Add a monthly membership with RevenueCat. Members without it can see the schedule but not book. |
| It's broken. | Tapping a class on Home opens a blank screen. It should open the class detail for that class. |
Data and services
Connect the backend under Server first, then say where the data lives and who may see it:
Supabase is connected. Store bookings in a table with the member, the class,
and the time. Only the member can see their own bookings.Good to know
- Show, don't describe: attach a screenshot of a layout you like or a bug you see. For a flow designed in Figma, send its screens with the plugin; from anywhere else, one image per screen. See Build from a Figma design.
- To change one place, highlight the lines in Code and send them with your request.
- Keep secrets out of chat, split unrelated changes, and don't restate the whole app: the assistant reads the project.
Related
Did this page help?