Setup · Get Set Up
Your first useful query
The first query most people send is a test — "write me a poem about coffee" or "what is the capital of France." That wastes the session. This lesson builds the habit of writing queries that produce something you could actually use today.
What makes a query useful
A useful query specifies three things on the first message: audience, format, and constraint. Audience is who reads the output — you, your manager, a customer. Format is the shape — bullet list, draft email, table, code snippet. Constraint is what limits apply — word count, tone, what not to include.
Without these three, Claude produces a generic middle. With them, it produces a first draft you can actually edit.
Walk-through
Pick one item from your actual inbox or task list right now. Something you would write anyway this week. Then build your query in this shape:
You are helping me [role/context].
Write [format] for [audience].
Constraints: [length], [tone], [what to omit].
Here is the input: [paste the raw material].
A real example:
You are helping me reply to a client who asked why a feature is delayed.
Write a two-paragraph email for a non-technical product manager.
Constraints: under 150 words, professional but not cold, do not mention the specific developer's name.
Here is their message: [paste].
Send it. Read the output. Note what is right and what is off. Then do one thing: send a single follow-up message that names exactly one thing to change. Not "make it better" — one specific change.
If you get stuck
- "The output is too generic" — You skipped the audience or the constraint. Add both and re-send.
- "I don't know what to ask" — Open your email and find the most recent message you have not replied to yet. That is your first query.
- "The follow-up made it worse" — That is useful data. Ask Claude to show you what changed between the two versions so you can see where the instruction was ambiguous.
Cross-reference
Once you have a query that works well, "One workflow you do every day" shows you how to save and standardize it so you are not rewriting it from scratch each time.
Deliverable
You have sent a query that produced a draft you could edit and send. The success criterion: you could copy the output into an email or document and make fewer than five edits before it was ready to use. If you needed more than five edits, the query was missing a constraint — go back and add it.
Try these prompts
- Rewrite this vague query as a useful one by adding audience, format, and one constraint: "Help me write an email."
- You are helping me reply to a client who asked why a feature is delayed. Write a two-paragraph email for a non-technical project manager. Constraints: under 150 words, professional but not cold, do not mention the specific developer's name. Here is their message: [paste your own message here].
- I sent Claude a query and the output was too generic. Write one follow-up message that asks Claude to change exactly one specific thing about its previous response.
Sign in to keep your place and tick off lessons. Reading stays open either way.