Hey there! The question I keep getting lately, more than any other, is some version of: "How do I prompt this thing?" A lot of people are not sure how to talk to these tools, so this week I want to break it down and keep it simple. I will also show you exactly how I write my prompts.
Prompting is not just about the text you give the AI. It is about the context you give it: the files you attach, the examples you show it, the instructions you set, and the apps you connect.
I turned this into a full AI Basics page: How to prompt AI. That page has the full guide; this newsletter has the key points: what a prompt actually is, a five-line prompt template you can copy, and three techniques I use in my own prompts. No sponsorships here either: we read all three AI companies' prompting guides, tested them against my own prompts. These techniques work in whatever tool you already use.
A prompt is how you point the AI at what you want. It is not just the sentence you type; three things shape what you get back:
That is why two people can type "review my budget" and get completely different results. One attached the spreadsheet, or said where to find it. The other attached nothing. Same words, completely different prompt.
Before you send a prompt, ask yourself: would a colleague reading this with no other context know what to do? If not, the AI will not either.
The takeaway: give the AI the context it needs, and treat it like a brilliant but new employee.
Here is a task someone at a nonprofit might face. The vague version: "Write a thank-you email to the sponsor." The AI has to guess which sponsor, what they did, what you want next, and how your organization sounds. You get something generic, then spend three messages fixing it.
Now the strong version: "Write a thank-you email to the company that sponsored our fundraiser dinner last night. My notes from the event are attached. Thank them for the $5,000 sponsorship, mention that we hosted about 200 guests, and invite their team to visit one of our programs this fall. Keep it under 150 words, warm but professional. Don't ask about next year's sponsorship yet."
Same task, four changes: the situation is named, the AI can see the real notes, done is defined, and one boundary is explicit. That structure is repeatable. Here is the template:
What I want: [the task and the outcome, in one or two sentences] What you need to see: [attach the files, paste the notes, or name the source the AI should use] What done looks like: [format, length, audience, and anything that must be included] What to avoid: [anything off-limits, plus mistakes you have seen AI make on this before] Before you act: [for big or risky tasks: "show me a plan first and wait for my go-ahead"]
The above is not a checklist, just the shape of a good prompt: skip any line that does not apply. Quick questions do not need prompts like this, but for bigger tasks, filling it out takes 30 seconds and should save you from correcting the AI many times later.
The takeaway: make sure to give the AI the complete story in terms of what you want.
For this issue we analyzed about 2,800 of my real prompts to Codex and Claude from the past ten months. Three techniques showed up constantly, and they matter most with agents: AI tools that open files, use apps, and keep working for minutes, even hours.
One big tip: when you catch yourself repeating the same setup in every prompt, save it as a custom instruction, a project, or a skill so it is already loaded next time. Step 5 of the full guide explains this further.
Note: none of these are about clever wording. They are about being intentional about what the AI sees and what we want it to do.
See you next week,

Ky Tomita, The Playbooks AI