Why Prompt Quality Matters
Rey AI has full context of your app, but it can only act on what you tell it. When your prompt is clear and specific, the agent can match your intent more accurately — producing screens that fit your design, tables with the right structure, and copy that suits your audience. Spending a few extra seconds on your prompt consistently saves time on revisions.Prompting Principles
Be specific about what you want
Describe the screen’s purpose, the key UI elements it should include, and any constraints. Instead of “add a dashboard,” write “add a dashboard with a summary card for total revenue, a bar chart of orders by week, and a table of recent customers.”
Mention your app context
Include a short description of your app so Rey AI can tailor its output. Phrases like “for a fitness tracking app” or “for a B2B invoicing tool” give the agent the frame it needs to make relevant choices.
Reference existing components or tables by name
If your prompt involves something already in the app, use its exact name. For example: “Update the BookingForm screen to include the Instructors table as a dropdown.” Named references prevent ambiguity.
Example Prompts for Common Tasks
Generating a screen
Generating a screen
Use this pattern when you want Rey AI to build a new screen from scratch. Include the screen’s name, its purpose, and the main components you expect.Why it works: It names the app context (yoga studio), identifies the screen type (welcome), and lists the exact components needed (hero image, tagline, button with a specific label).
Generating a table
Generating a table
When asking Rey AI to create a table, specify the table name, each field name, and the type for each field.Why it works: Rey AI gets the exact schema you need — no guessing about field names or types, and the resulting table is immediately usable.
Writing copy
Writing copy
Give Rey AI the element you need copy for, the quantity of options you want, and the tone or audience.Why it works: Asking for multiple options gives you choices. Specifying the tone (“motivational and approachable”) steers the agent away from generic output.
Getting design feedback
Getting design feedback
Point Rey AI at a specific flow or screen and ask a targeted question about the user experience.Why it works: It names the flow, defines a clear goal (reduce drop-off), and frames the request as a review — inviting analysis rather than a rebuild.
Asking a data question
Asking a data question
Ask in plain language, as if you’re asking a colleague who knows your app’s data.Why it works: The question is specific and answerable. Avoid broad questions like “tell me about my data” — the more focused your question, the more useful the answer.
When the Result Isn’t Right
If Rey AI’s output isn’t what you expected, you have two options:- Refine with a follow-up prompt. Keep the panel open and give Rey AI a correction. For example: “The layout is good, but move the button to the bottom of the screen and change the label to ‘Get Started’.” Follow-up prompts build on the current result rather than starting over.
- Undo and try a different prompt. If the result is too far off, reject the changes and rewrite your prompt with more detail or a different framing. Consider which of the prompting principles above you could apply more thoroughly.