Most "prompt engineering" advice is either obvious or overhyped. The real skill isn't finding a magic phrase - it's giving Claude the same things you'd give a smart new hire on their first day: context, a clear goal, and a sense of what "good" looks like.
The four-part structure that works almost every time
- Role or context. Who is this for, and what's the situation? "I'm writing to a client who's already frustrated about a delay."
- The task, specifically. Not "write an email" but "write a short email acknowledging the delay, giving a concrete new date, and offering one goodwill gesture."
- Constraints. Length, tone, what to avoid. "Keep it under 120 words. No corporate jargon. Don't over-apologize."
- Format. How should the answer come back? Plain text, a table, three options to choose from?
Notice none of that requires special syntax. It's just being as clear with Claude as you'd want a colleague to be with you.
Give it examples when the stakes are high
If the output really matters, show Claude one or two examples of what good looks like before asking for the real thing. "Here's an example of the tone we use in client emails: [paste]. Now write one for this situation: [describe]." This single technique - called few-shot prompting - closes most of the gap between a mediocre first draft and something you can send as-is.
Iterate instead of starting over
Your first response doesn't need to be perfect. Treat the conversation like a real editing pass: "make it shorter," "cut the third paragraph," "make the opening line stronger." Each follow-up carries the context forward, so refining is almost always faster than rewriting your original prompt from scratch.
Ask Claude to ask you questions
For anything genuinely ambiguous, try: "Before you answer, ask me anything you need clarified." It's a small trick that turns a guessing game into a real briefing, and it usually saves a round of unnecessary revisions.