✍️Prompting tips
Get better output by being specific about what you want.
5 min read·Last updated 2026-05-17
Most build failures aren't model failures — they're prompt failures. A good prompt is short, specific, and stacks one concrete change at a time.
The shape of a good prompt
- Anchor: which screen or feature you're talking about.
On the home screen… - Verb: what to do.
add a banner…change the color…replace… - Detail: the smallest specific thing.
…to deep indigo (#4F46E5) with white text. - Constraint (optional): what not to break.
Keep the layout otherwise the same.
Examples
❌ Make the app look nicer
✅ On the home screen, replace the gray header with a deep-indigo gradient (#4F46E5 → #7C3AED) and switch the title to white serif Italiana.❌ Add a paywall
✅ Add a RevenueCat paywall before the Insights tab. Use the offering id `default_v1`. Show 7-day free trial then $4.99/mo.💡
One change per turn
Stacking five changes into one prompt is how you end up debugging four things at once. Move in small steps.