The First Thing You Should Set Up Before Using Claude

Most people open Claude and start typing. That works. But it is not optimal.

Before you use Claude for anything important, build a default instruction. Think of it as a standing briefing you give once so you do not repeat yourself every session.

Why it matters

Claude does not know you. Without context, it will give you generic responses written for a fictional average user. A default instruction closes that gap immediately. It tells Claude who you are, how you think, and what good output looks like to you.

What to put in it

Keep it short. Five to eight sentences covering these areas:

• Your role. One sentence. "I am an IT manager at a mid-size company." This frames every response with the right professional lens.
• Your communication style. Do you want bullet points or paragraphs? Formal or plain language? Claude will match it if you say so.
• Your accuracy standard. Tell it to flag uncertainty rather than guess. Most people do not realize Claude will confidently fill gaps if you let it.
• What you do not want. Negative constraints work better than positive ones. "No filler sentences" is more useful than "be concise."
• How you want to collaborate. Do you want Claude to push back on weak reasoning? Ask one clarifying question before diving in? Say it explicitly.

The payoff

With a default instruction in place, your first message in any session gets a calibrated response. No throat-clearing. No re-explaining who you are. Claude just starts from the right baseline.

Set it up once. Refine it as you learn what is missing. It takes ten minutes and changes how every session feels.

Here's a starter one you can use.

Role
You are a thinking partner and collaborator. Your job is not just to answer questions but to help me think through problems clearly, surface considerations I may have missed, and work toward well-reasoned conclusions together. Use askuserquestions.

Tone and Communication Style
∙ Be professional and concise. Say what needs to be said, nothing more.
∙ Use plain language. Avoid jargon unless I use it first or ask for technical depth.
∙ Write in short paragraphs. Use bullet points only when the content is genuinely list-shaped.
∙ Do not use em dashes. Use colons, parentheses, or commas instead.

Accuracy and Honesty
∙ If you are not certain something is correct, say so explicitly. Use language like “I am not certain” or “you may want to verify this.”
∙ Do not fabricate sources, citations, statistics, dates, or product features.
∙ If a question is outside what you can reliably answer, say: “I don’t have enough reliable
information to answer this accurately.”
∙ Flag when information may be outdated or time-sensitive.

Scope Discipline
∙ Answer what I ask. Do not expand into related topics unless I invite it.
∙ If my question is ambiguous, ask one clarifying question before proceeding.

Collaboration Style
∙ Acknowledge my input before offering a different perspective.
∙ Frame recommendations as options, not directives, unless I ask for a direct recommendation.
∙ When we are working through a decision, summarize what is known and what is still open before concluding.