CLAUDE QUICK SETUP GUIDE

Claude settings I would change on day one - 4 parts.

Part 1 of 4

Privacy

Model training and location metadata. The two switches I check before I type anything.

Download the PDF See the LinkedIn post
Part 2 of 4

Memory

Turn on Memory so Claude knows you and your work, and decide what it remembers.

Download the PDF See the LinkedIn post
Part 3 of 4

About you

Fill in Instructions for Claude. It's the setting that changes Claude's answers the most.

Coming soon
Part 4 of 4

Claude in Chrome

Let Claude work in your browser, and set it to ask before it acts.

Coming soon

Follow me on LinkedIn so you don't miss the next guide.

Part 3: Interview Prompt · coming soon

Let Claude generate its own Instructions by interviewing you.

Available October 17, when Part 3 goes live.

Part 3: Interview Prompt

Let Claude generate its own Instructions by interviewing you.

Show the promptHide the prompt

To help you create your first set of instructions, like how Claude should behave and what it should know about you, copy the prompt below and paste it into Claude to start the interview. You can also edit the prompt in the box before copying it.

<task>
Interview me to write my "Instructions for Claude": a short text I will paste into Claude's Settings. Claude reads it at the start of every new chat I have, as my own saved settings. So every line must change how Claude responds across all my conversations, or it doesn't belong.
I may never have used Claude before. Keep the interview fast, simple and free of jargon. Your job: learn who I am and how I want to work with Claude, then turn it into the best possible instructions.
</task>

<interview_rules>
- Ask 10 questions, one per message, numbered "n/10". Ask an 11th or 12th only if a section of the output would otherwise be empty or contradictory.
- Use your clickable-choice tool (AskUserQuestion) if available: one question per call, 3 options plus the automatic "Other" field. Use multi-select when several answers can be true at once (apps, formatting). If the tool is unavailable, show the same options as a numbered list and tell me I can type my own answer.
- Questions: under 15 words, plain words. Options: specific, worded the way I would say them, each a plausible complete answer.
- Choose each next question yourself. No fixed script. After every answer, find which item in <coverage> you know least about and ask about that. One answer can settle several items: merge or drop questions accordingly. Use your last questions to close gaps, never to repeat.
- Build the 3 answer options from my earlier answers in this conversation. Question 1 has no earlier answers, so offer 3 contrasting generic options. For later questions, make one option deliberately different from the other two so I'm not anchored.
- What I type in "Other" or in free text outranks your options.
- If I type "skip", move on and don't return to it. If an answer is vague, ask once for a concrete example (also as clickable options). If it stays vague, drop it rather than guess.
- If two of my answers conflict, resolve it in your next question.
- No praise, commentary or recaps between questions. Reply in the language I write in.
</interview_rules>

<coverage>
By the end you must understand the following. Each group becomes one section of my instructions.

Who I am
- Role and industry
- Experience level, and what to skip explaining
- Who I work with or write for
- Languages I work in, including spelling or regional variant
- Context true in every conversation

What I usually ask for
- 2-3 recurring task types
- Tools or apps, only if they change how Claude should respond
- My main goal this year, in one line

How I want answers
- How I take in information best (prose, bullets, tables, visuals, one thing at a time)
- Length and tone, with the reason behind them

Avoid
- Defaults I want turned off (openers, filler, closing offers)
- What Claude should never assume about me
- Words or jargon Claude might read generically

Test every answer: is this true in every conversation? If it applies only to one project or client, tell me it belongs in a Project, not here, and move on.
</coverage>

<output>
After the last question, write my instructions as one code block of plain text, under 400 words.
- Voice: first person for facts about me ("I'm a...", "I work with..."), plain imperatives for rules aimed at Claude ("Lead with the answer"). "You" means Claude and "I/me" means me. Never write about me in the third person ("The user is...", "You are helping a...") and never give Claude a persona: the text is my own settings, and mixing who "you" is causes confusion.
- Structure: four short labeled sections (Who I am, What I usually ask for, How I want answers, Avoid), then the working rules below. If I gave nothing for a section, omit it. Never invent or pad.
- Content: use only what I told you, in my words where possible. Every line specific and testable. Add a short reason where it helps Claude apply the rule.
- Language: write in the language I use, and state my working languages inside.
- End with these working rules, reworded to fit me:
  - Say "I don't know" instead of guessing.
  - Only state facts, quotes and sources you can back up.
  - Ask me a question when my request is ambiguous.
  - Tell me when I'm wrong, and why. Don't agree just because I seem invested.
  - Separate what you know, what you're inferring and what you're guessing.
</output>

<after_the_block>
Tell me:
- I can keep, edit or drop any line, especially the working rules.
- To install: click my initials (lower left), open Settings, find "Instructions for Claude". The tab name varies (Account or Profile), so look for the field by name. Don't state a path for the mobile app.
- Rules specific to one project or client belong in a Project, not here.
- Review it monthly.
</after_the_block>

Start with question 1.

Want to go further?

Interested in getting better with Claude, or building your own AI tool?

I teach a 3-week live cohort for coaches, consultants and founders. Two live sessions a week, on your own data, and you finish with one tool you built for yourself.

$750 CAD for the first cohort ($2,250 CAD after)
10 spots, first cohort
Starts Oct 26. Registration closes Oct 19.
Registration for the first cohort is closed. The next cohort starts November 30, at $2,250 CAD.

Save my spot → Join the list for the next one See the full course page

Claude settings I would change on day one - 4 parts.

Privacy

Memory

About you

Claude in Chrome

Let Claude generate its own Instructions by interviewing you.

Let Claude generate its own Instructions by interviewing you.

Interested in getting better with Claude, or building your own AI tool?