Iterate one change at a time
A message asking for one clear change is cheaper and more accurate than one asking for six. Check the preview after each one.
Describe outcomes, not code
Say what a person should be able to do and what they should see. Naming files or libraries rarely helps and often narrows a good solution into a bad one.
Give real examples
Two or three sample rows, a real price, an actual message a user would send — concrete examples produce far better screens than abstract descriptions.