[Documentation](https://fluxnative.app/docs) / Build your app

# 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.

![A first brief with four parts marked: what the app does, who it is for, the first screens, and the look](https://fluxnative.app/guide-media/writing-prompts.d34d9c02.webp)

A good brief answers four questions: what it does, who it is for, which screens come first, and how it looks.

## 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](https://fluxnative.app/docs/connections) 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](https://fluxnative.app/docs/figma).
- 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.

**Tip:** If a turn goes the wrong way, undo it and send a clearer request instead of piling corrections on top.

## Related

[Work with the assistant](https://fluxnative.app/docs/work-with-the-assistant) · [Revisions and undo](https://fluxnative.app/docs/revisions)

Previous: [Work with the assistant](https://fluxnative.app/docs/work-with-the-assistant) · Next: [Preview](https://fluxnative.app/docs/preview)

---

Get the result you want: name the people, the job and the screens, change one thing at a time, and say what to keep.

Page: https://fluxnative.app/docs/writing-prompts