Getting started
Prompting best practices
The quality of your prompt directly impacts the quality of the generated application. Follow these guidelines to get the best results from Rytora BuildLabs AI.
Be specific about what you want
The more detail you give, the closer the output will be to your vision on the first try. Include the type of app, its purpose, and the main features you need.
Tip
Instead of 'Build me a dashboard', say 'Build a project management dashboard with a Kanban board, task list view, team member sidebar, and a top nav with notifications.'
Describe the UI you have in mind
Tell the AI about layout, color schemes, component placement, and visual style. Reference well-known products if that helps convey the look and feel.
Tip
Example: 'The layout should be similar to Notion — clean sidebar on the left, main content area with a breadcrumb at the top. Use a light neutral color palette with blue accents.'
Mention the stack when it matters
Rytora BuildLabs defaults to React + Vite + Supabase. If you need specific integrations, auth methods, or database tables, mention them explicitly in your prompt.
Tip
Example: 'Include Stripe integration for payments, use Supabase Auth with role-based access (admin, user), and create tables for Users, Projects, and Tasks.'
Iterate step by step
Don't try to build everything in a single prompt. Start with the core structure, review the output, then ask for additions and refinements incrementally.
Tip
First prompt: 'Create a blog platform with a post list page and single post page.' Follow-up: 'Add a rich text editor for creating new posts with title, content, and tags.'
Good vs. bad prompts
Here are side-by-side examples showing the difference a well-crafted prompt makes.
“Make me a website”
“Create a landing page for a SaaS product called CloudSync with a hero section, feature grid, pricing table with 3 tiers, and a contact form. Use a modern dark theme.”
“Add a login page”
“Add a sign-in page with email and password fields, a 'Forgot password' link, Google OAuth button, and a link to the sign-up page. Show validation errors inline below each field.”
“Make it look better”
“Update the dashboard to use a sidebar navigation on the left (240px wide, dark background), move the stats cards into a 2x2 grid, and add a line chart for revenue below the cards.”
Remember
You can always iterate. Start with a clear first prompt, review the generated app, then refine with follow-up instructions. Each iteration builds on the previous output, so small, focused changes work better than rewriting everything at once.