Prompting best practices
The quality of your prompts directly determines the quality of Cadrant's output. Here are best practices to get the most out of the AI.
Be specific and concise
- Prefer 'Add a contact form with name, email and message fields' over 'Add a form'.
- Describe the expected result, not the technical method.
- One prompt per change: avoid asking for 5 different modifications in a single message.
Provide visual context
- Specify colors ('use a dark background with blue accents').
- Indicate layout ('two columns on desktop, single column on mobile').
- Reference known styles ('a minimalist style like Stripe' or 'a colorful design like Notion').
Iterate rather than start over
- If something doesn't look right, ask for a targeted change rather than regenerating the entire page.
- Use phrases like 'Modify the header to...' or 'Replace the hero section with...'.
- Be specific about WHAT should change and WHAT should stay.
Prompts for backend
- Describe your data in business terms: 'a products table with name, price, description and image'.
- Specify relationships: 'each user can have multiple orders'.
- Indicate access rules: 'only the author can edit their own articles'.
If you get an unexpected result, don't delete everything. Use version history to roll back, then rephrase your prompt more explicitly.