Using Claude well: ask clearly, give context, iterate

Start with what you actually want

Claude is an AI assistant you talk to in plain language. It cannot see your screen, your files, or your plans unless you tell it about them, so the quality of what you get back depends heavily on what you put in.

Begin by finishing this sentence for yourself: 'I want help with ___ so that I can ___.' The second half matters. 'Help me write an email' is a request. 'Help me write an email so that my landlord fixes the heater this week' is a goal, and a goal lets the assistant make better choices about tone, length, and what to include.

Give context it cannot guess

Think of Claude as a capable new colleague who has just walked in. They are smart, but they know nothing about your situation. Tell them who the audience is, what you have already tried, what is fixed, and what is flexible.

A useful habit is to add three short lines of background before your request: who you are writing for, what the situation is, and any limits such as word count, deadline, or things to avoid. You do not need to be formal. Short, honest sentences work well.

Be careful about what you paste in. Do not share passwords, account numbers, or other people's private details. Read the privacy settings of whichever service you use, because they differ and change over time.

Describe what a good answer looks like

If you do not say what shape you want, you will get the assistant's default shape, which is often longer and more general than you need. Say whether you want a short paragraph, a bulleted list, a table, a draft email, or three options to choose from.

You can also say what level of reader the answer is for. 'Explain this to someone who has never used a spreadsheet' produces a very different answer than 'explain this to someone who uses spreadsheets daily.'

Iterate instead of starting over

The first answer is a draft, not a verdict. The most effective users treat the conversation as a back and forth. Read the reply, notice what is close and what is off, and say so specifically.

Useful follow-ups sound like this: 'Keep the second paragraph, but make the opening warmer.' 'That is too formal; write it the way I would say it to a friend.' 'Give me two other versions with a different angle.' Specific feedback beats 'make it better.'

If a conversation drifts or gets tangled, it is fine to start a fresh one and paste in only the good parts. A clean start often beats rescuing a muddled thread.

Keep your own judgment switched on

Claude can be wrong, and it can sound confident while being wrong. Names, numbers, dates, quotations, and anything about recent events deserve a second look from a reliable source. For anything affecting your health, money, or legal position, treat the answer as a starting point for a conversation with a qualified professional, not as the final word.

You can also ask Claude to help you check itself: 'What parts of your answer are you least sure about?' or 'What would I need to verify before relying on this?' The reply is not a guarantee, but it often points you to the weak spots.

Practice

1. Pick a small real task from this week, such as a message you need to write. Write your request in one sentence, then add three lines of context: audience, situation, and limits. Send it and read the result.
2. Reply with two specific changes, for example one thing to keep and one thing to fix. Notice how much closer the second draft gets compared with the first.
3. Ask Claude what in its answer you should verify before relying on it, then actually check at least one of those items yourself.

Check yourself