The 2-Hour Claude Setup That Made Everything Click

The 2-Hour Claude Setup That Made Everything Click

Last Monday I wrote a LinkedIn post in 6 minutes. Used to take me 40.

Not because Claude got smarter overnight. Because I finally stopped treating it like a search engine and started treating it like a teammate that actually knows me.

Here's the thing: most people use Claude like a typing contest. They type a question, get an answer, close the tab. Every chat starts from zero. You re-explain who you are, what you're building, what your voice sounds like. You correct the tone four times. You give up and rewrite it yourself.

I did this for months. Then one Saturday morning with coffee and a clear head, I spent two hours setting it up properly. Uploaded a few files about how I think and how I work. Told it what I'm building, what I sound like, what I'm bad at, and what I want it to never do.

The output: my prompts shrank from 800 words to 12. I can say "write a LinkedIn post about yesterday's podcast" and Claude already knows my voice, my audience, my format, my banned words, my call-to-action style. The first draft comes back usable.

This is the most useful thing I've shared all year. Here's the full setup.

Why Claude Specifically

I use ChatGPT for image generation. I use Perplexity for real-time research. But for this specific setup — the "second brain" — Claude wins on three things:

Projects. Separate workspaces per use case. One for the newsletter, one for the business, one for personal stuff. Contexts don't bleed into each other.

It actually follows instructions. If you tell Claude "never use the word leverage," it doesn't. ChatGPT will use it by prompt 3, every time. Every single time.

File memory. Drop 10 documents into a Project and Claude reads all of them before every reply. No re-uploading. No re-explaining.

It's $20/month for Pro. Projects don't exist on the free plan.

Step 1: Create Your Project (5 Minutes)

Head to Claude.ai. Sidebar → Projects → Create project.

Name it after one thing you do a lot. "LinkedIn." "Client emails." "Investor updates." Start with the task you do every single week and want to be 5x faster at.

Step 2: Build Your About-Me File (30 Minutes)

Don't write this yourself. Have Claude interview you.

Open a new chat in your Project and paste this:

I want you to become my second brain. I want you to never invent facts about me and only use facts that I tell you, in everything you write for me and every decision we make together.

Interview me for the next 30 minutes. Ask one question at a time. Go deep on each answer before moving to the next. Cover: who I am, what I do, what I'm building right now, what my goals are for the next 12 months, what I'm scared of, what I've already tried that didn't work, who my audience is, what they care about, what they're skeptical of, and what's outside the scope of what I want to talk about publicly.

At the end, output everything as a single document called about-me.md, formatted with clear headers.

Answer everything honestly. Don't write what you wish were true — write what's actually true, including the messy stuff.

This is the most important file in the whole setup. Spend the 30 minutes. Future you will thank present you.

Step 3: Build Your Voice File (20 Minutes)

Same approach — don't describe your voice in the abstract. Let Claude figure it out from the work.

Open another chat and paste:

Here are 3 things I wrote that I love and that my audience or my investors loved. Read them. Analyze them deeply.

I want you to understand my tone of voice — the things I would never say, the things I love to say, how I sound when I'm excited, when I'm sad, when I'm being honest about a failure. Notice if I use emojis. Notice if I use double exclamation marks. Notice my sentence length patterns.

Then ask me follow-up questions to fill in what the writing doesn't show. Ask about words I hate. Ask about phrases I refuse to use. Ask about which adjective I'd never pick.

When you're done, output everything as my-voice.md.

Paste in 3 things you've written that sounded most like you. A LinkedIn post that hit. An email to a friend. A caption that got real engagement.

Step 4: Add the Anti-AI Writing Rules (10 Minutes)

This is the file that stops Claude from making your writing sound like Claude.

I built mine after watching my own newsletter drafts come back full of em dashes, "not just X but Y," and the word "navigate." Every AI tic I could spot — listed, banned, enforced.

It works really well. Mine is public — grab it as a starting point, then add your own banned words.

Step 5: Write Your Project Instructions (15 Minutes)

Inside your Claude Project there's a field called "Project instructions." This is your system prompt — it runs before every single chat in this Project.

This is your rules of engagement. What you want. What you don't want. How you want outputs formatted. What context to always include.

Write it like a job description for an employee who needs to know your standards.

Step 6: Add 3 Template Files (20 Minutes)

Take the 3 things you write most often. For me right now: newsletter intros, LinkedIn posts, and emails to podcast guests.

For each one, save your best example — the version that actually worked in real life — as its own file.

One important thing: templates have to live in the matching Project. The LinkedIn template goes in your LinkedIn Project, the pitch email template goes in your Sales Project.

Don't dump everything into one Project. Claude does so much better when each Project has tight, relevant context.

Step 7: Add Your Project Context (15 Minutes)

The step most people skip, and I really don't want you to skip.

Drop in everything that shows Claude where this project currently stands. Real files. Numbers. The messy reality.

If your Project is LinkedIn → upload your last analytics screenshot, a CSV of recent posts and their performance, paste in 5 of your best-performing posts.

If your Project is Sales → upload your pipeline, your win/loss data, a few closed deals.

Then write one line at the top of your Project Instructions: your big goal for this year.

Something like: "My goal this year is to grow my LinkedIn to 100K followers." Or "My goal this year is to close $2M in new revenue."

That one line changes everything. Now when you ask Claude "should I post this?" — it's not guessing what good means. It's checking your post against your real goal and your real numbers.

The Real Unlock: Close the Feedback Loop

Everything I just walked you through gets you to roughly the same place as a smart assistant who knows you. That's huge.

But the actual unlock is the next step, and it's what I'm most excited about: building a closed feedback loop.

Every time you give feedback to your team, every time you edit something Claude made, every time you say "no, change this" — that information has to find its way back into Claude. Otherwise Claude keeps making the same kinds of mistakes, and nothing compounds.

Here's what I'm experimenting with:

• Record every team conversation. Granola, Otter, Wispr Flow — the transcript is captured automatically. Drop those transcripts into Claude weekly. Every time you said "this doesn't sound right" — that's a data point Claude needs.
• Make your edits visible. When you rewrite something Claude wrote, tell it what you changed and why. "I cut the second paragraph because it sounded too motivational. I rewrote the close because it didn't have a CTA." Claude adjusts for next time.
• Capture feedback where AI can see it. Slack messages — yes. Phone calls — lost forever. Move more feedback into channels Claude can actually access.

The speed of your decision-making goes up dramatically the second Claude starts predicting your judgment instead of asking for it every time.

The Math

Two hours of setup. $20/month. 12-word prompts that come back usable.

Compare that to the alternative: every chat starts at zero, you explain who you are, you correct the tone four times, you give up.

I've spent 20 years building software. This is the highest-leverage time investment I've made in my work this year. And I'm not exaggerating.

The question isn't whether this works. It's whether you'll actually spend the two hours.

What's the one project in your work that would benefit most from Claude knowing you deeply? Start there. Everything else follows.