{"slug":"writing-prompts","title":"Write better prompts","summary":"The assistant builds what you describe. Name the people, the job, and the screens; change one thing at a time; and say what to keep.","body":"A good request is short and concrete. It tells the assistant who the app is for, what should happen, and where. You do not need to write code or name files.\n\n## A first brief\n\nCover four things: the audience, the main job, the first screens, and the tone.\n\n```\nA booking app for a small yoga studio. Members browse this week's classes,\nbook a spot, and see their upcoming bookings. Screens: class schedule by day,\nclass detail with instructor and spots left, my bookings, and profile.\nCalm and airy, with a soft sage accent. Email sign-in.\n```\n\n## Follow-up requests\n\nChange one thing at a time, and say what to leave alone.\n\n| Instead of | Try |\n| --- | --- |\n| 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. |\n| Fix the design. | The schedule cards feel cramped. Add more space between cards and make the class time larger than the title. |\n| Add payments. | Add a monthly membership with RevenueCat. Members without it can see the schedule but not book. |\n| It's broken. | Tapping a class on Home opens a blank screen. It should open the class detail for that class. |\n\n## Show, don't describe\n\nAttach a screenshot of a layout you like, or of the bug you see. For a whole designed flow, [import it from Figma](/docs/figma) so the assistant builds from the real frames.\n\n## Point at the code\n\nWhen you know where the problem is, open **Code**, highlight the lines, and send them with your request. The assistant edits that part and leaves the rest.\n\n## Data and services\n\nSay which backend the data lives in. Connect it first under [Connections](/docs/connections), then ask the assistant to use it, for example: \"Supabase is connected. Store bookings in a table with the member, the class, and the time. Only the member can see their own bookings.\"\n\n## Things to avoid\n\n- Secrets in chat. Keys go in Connections.\n- Many unrelated changes in one message. Split them so each can be reviewed and undone on its own.\n- Restating the whole app on every message. The assistant already reads the project.\n\n> [!TIP]\n> If a turn goes the wrong way, undo it and send a clearer request rather than piling corrections on top.","sectionSlug":"build","sectionTitle":"Build your app","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"work-with-the-assistant","title":"Work with the assistant"},"next":{"slug":"preview","title":"Preview"}}