Prompting well

Say these four things

1. Who it's for and what it's for. "A booking manager for a small yoga studio."
2. The main screens or views. "A weekly timetable, a class detail view and a customer list."
3. The data it keeps. "Each class has a time, teacher, capacity and booked count."
4. The feel. "Calm, light, lots of whitespace, green accents."

Weak

A fitness app.

Strong

An App for interval workouts: create a workout with rounds, work and rest times; a big countdown screen with sounds; a history of finished workouts. Dark theme, orange accents.

Ask for behaviour, not just looks

"When I mark a task done it moves to the bottom and the progress bar updates" is better than "make the tasks nicer".

Use realistic examples

Mention real-looking sample data ("three sample classes on Monday morning") so the preview isn't empty.

Keep the first prompt focused

Build the core first, then add features one message at a time. Big lists of features in one message make it harder to get each one right.

What to avoid

• API keys or passwords. Never paste secrets into a prompt. See Credentials and connections.
• Other packages. Projects use a fixed, preview-safe set of libraries (see Apps vs Web Apps). Asking for other npm packages won't work in the preview.
• Real backends. Projects save data on the device today. See Data, sign-in and storage.