Writing Great Prompts
Flarite understands plain English. A few simple habits will consistently get you better results.
Be specific about what you want
The more specific you are, the better the output. Compare:
- ❌ "Show me customers"
- ✅ "Show me the last 10 Stripe customers who signed up this month, sorted by most recent first"
Name the provider or resource type
If you have multiple integrations active, naming the provider helps avoid ambiguity:
- "Show me my Stripe invoices that are past due"
- "List all Cloudflare Workers in account 12345"
- "Which Supabase tables are missing RLS?"
Include filters upfront
- By status — "List active subscriptions only"
- By time — "Show payments from the last 30 days"
- By identity — "Find customer [email protected]"
- By amount — "List invoices over $500"
Chain multi-step requests
"Find the Stripe customer [email protected] and show me their most recent 5 payments"
"List Cloudflare zones with WAF disabled, then check which have a Workers deployment"
"Show Supabase edge functions not updated in 60+ days"✨
TipYou don't need API terminology. "subscriptions about to expire" works just as well as "subscriptions with status=trialing and trial_end in the next 7 days".
Quick reference patterns
List all [resource] where [condition]
Find [customer/user] by [email/name/ID]
Show me [resource] from the last [N days]
Which [resources] have [missing thing]?
Create a [resource] with [parameters]
Summarize [data topic] for me