Know what you want to make
Before you write a prompt, write one sentence about the work itself. Who is it for? What should the reader understand or do? Which constraints matter? A clear brief gives you a way to judge the result, even when you explore several very different directions.
Keep the useful context close
Add the information that changes the answer: the intended audience, the format, the tone, and a few examples. Avoid collecting context just because it is available. A compact, deliberate brief is easier for your team to maintain and easier to revisit when the project changes.
Ask for distinct directions
Instead of asking for a perfect final answer, ask for a few genuinely different approaches. Compare what each one emphasizes, what it leaves out, and how it serves the audience. Then choose a direction and refine it with specific feedback.
Save the reasoning, too
When a draft becomes useful, keep the brief and the decisions that shaped it. The next person should be able to understand why the work looks the way it does. That small habit turns a good one-off result into a starting point the whole team can learn from.
Put the idea into practice.
Tell us about your team, your workflow, and the next thing you want to build.