Everyone around you seems to run their life with AI. You opened it once, typed a question, got an answer, closed the tab. That was months ago.

The gap between those two people is not talent. It is setup. Claude out of the box is a very smart stranger. Claude set up properly knows your work, your family, your files, and your calendar, and that is a different tool entirely.

This is the whole setup, in order. Do it once, over a weekend or a couple of evenings, and you land where I am: books, payroll, captions, meal plans, and my calendar, all running through it.

The setup checklist Work top to bottom. Each one is a section below. Create your account Download the desktop app Put it on your phone Pick your plan Give it access to your desktop Create your context files Set up connectors Add the Chrome extension Make your first project Build your first skill Schedule a recurring task
Eleven boxes between you and a Claude that actually knows you. All of them are below.

1. Start at claude.ai

One URL: claude.ai. Sign up with your email or your Google account and you are in. The browser version is fully usable, and for day one it is all you need.

But do not stop there, because the browser version is the smart stranger. The next few steps are what turn it into yours.

2. Download the desktop app

Go to claude.ai/download and grab the app for your computer. There is a version for Mac and a version for Windows, pick whichever machine you actually live on.

Why bother when the browser works? Two reasons. The desktop app can work with the files on your computer, which becomes a big deal in step 5. And it lives one keystroke away instead of buried in tab number forty, which sounds small until you notice you actually use it now.

3. Put it on your phone

Same account, from the App Store or Google Play. The phone app is not the place for deep work. It is the place for the camera, and that is why it earns a spot.

My real uses: Olive brings home a camp flyer, I take a picture, and ask Claude to pull the dates and put them on my calendar. A handwritten note or a whiteboard, snap it, and it transcribes the whole thing before I lose it. A confusing email while I am in the school pickup line, screenshot, and I ask what they are actually asking me for.

Snap the flyer summer camp, week 3 Claude reads it dates, times, address On the calendar camp drop-off, mon 8am
The phone app is a camera with a brain. Flyer in, calendar event out.

4. Pick your plan

Start free. Genuinely. Use it hard for a week or two and let yourself hit the limits, because hitting the limits is the signal that it is earning a subscription.

When you upgrade, Pro is $20 a month, and the annual plan brings that down. The biggest thing you are buying is usage, the amount you can actually talk to it in a day. Pro also comes with the builder tools like Claude Code, which matter later if you want deeper customization, but usage is the real reason.

Free $0, start here Learn on it, set everything up Daily usage limits Upgrade when you hit them twice Pro $20/mo, less on annual Way more usage, the real reason Claude Code for custom builds Required for the Microsoft 365 connector if you live in Outlook
Free until you feel the ceiling, then Pro. Usage is the thing you are actually paying for.
Outlook people, one important note: the Microsoft 365 connector, which is how Claude reads your Outlook email and calendar, needs a paid plan. If your life runs on Outlook, Pro is not optional, it is the price of entry.

5. Give it access to your desktop

This is the first moment Claude stops being a chatbot. In the desktop app, allow it to work with your files. Now it can grab documents and create them.

What that looks like in practice: point it at three messy PDFs and get one clean summary saved to your desktop. Hand it a folder of receipts and get a spreadsheet. Ask it to draft the letter and it is sitting in the folder when you open it, a real file, not text to copy out of a chat window.

6. Create your context files

Here is the single highest-leverage thing in this whole article. Claude does not know you. Fix that once, in a file, and every conversation afterward starts warm instead of cold.

Do not write it yourself. Have Claude interview you:

Interview me so you can really know me. Ask one question at a time: my work, my family, how I like things done, what I am always juggling. When we are done, save everything to a file called about-me.md and read it before you help me with anything.

Just answer out loud, it writes the file. Mine knows my job, my girls and what they will and will not eat, how I sign my emails, and that I am a 5am person. The drafts stopped sounding like a press release the day that file existed.

Then go further, because this is where the real quality jump lives. Make your documents accessible. I gave it my business files and everything about my content. Now when I ask a question, it answers from my actual numbers and my actual history, not from generic advice.

Here is a folder with my key documents. Read through them and keep them as context. When I ask you questions, pull from these files first before giving me a general answer.

7. Set up connectors

Context files are what Claude knows. Connectors are what it can see live. A connector plugs Claude into software you already use, so it pulls real data in real time instead of asking you to paste things in.

The way to choose them: sit for two minutes and list the software your life actually runs on. Your email. Your calendar. Your payroll system. Your business tools. Slack if that is where your team talks. Those are your connectors, in that order.

Remember: a connector is the difference between "here is generally how to check a calendar" and "you are double-booked Thursday at 2, and the dentist is the one to move."

8. Add the Chrome extension

One connector deserves its own step. Claude for Chrome is an extension you install on your Chrome browser, and it lets Claude actually see and control the page you are on.

That means it can click around, fill things in, and work inside the websites you use, with you watching. And you can talk to it right there on the page instead of flipping between tabs. Install it from the Chrome side, sign in, and it connects to the same account.

It can draft an email in your actual email client or set up the calendar event right on the screen. My rule, the same one I use everywhere: let it draft anything, let it send nothing. You are the send button.

9. Think in projects

A project is a home for any topic you keep coming back to. The house renovation. Your content. A client. The job search. Instead of re-explaining the backstory in every new chat, the project holds the context and the history, and every conversation inside it already knows the story so far.

Throw in the relevant files, or point it at a folder on your computer, and let it accumulate. Mine include my content project, with every caption and script, and my books project, which knows my accounts and my categories. Ask a question inside the right project and the answer is startlingly specific.

10. Turn repeat work into skills

My rule: anything I have done one to three times, I make into a skill. A skill is a saved process. You walk Claude through the task once, the whole thing, then ask it to turn what you just did together into a skill.

We just went through my whole process for writing a caption. Turn everything we did into a skill called new-caption, with my rules and my voice baked in, so next time I can just call it and go.

Next time, you call the skill by name and it runs the entire process again on the new thing. This is how I run my books, run payroll, write captions, do research, plan what we eat for the week, and audit my calendar. Each one started as a task I did by hand three times and never wanted to explain again.

11. Schedule recurring tasks

The last layer is the one where you stop showing up. A recurring task runs on a schedule without you, and this is where the setup starts paying you back daily.

The best ones are the jobs that need doing but do not need you deciding: a daily brief of your day before you have coffee. A weekly calendar audit that flags the conflicts and the meetings that should be emails. A research task that watches a competitive landscape and reports what changed. Set the schedule once, and the work is just done, sitting there when you wake up.

The truth about prompting

Now the part everyone overcomplicates. There is no secret prompt. Nobody talking to Claude well is using magic words. They are giving it two things: context and information to base the answer on.

"Write me a meal plan" gets you a generic meal plan. "Read about-me.md, check the calendar for our activities this week, and plan five dinners around them" gets you your actual week, handled. The difference is not phrasing. It is everything you set up in steps 6 through 8.

And when you want Claude to act, not just answer, remember what acting requires: a connection. That is what the connectors are, the bridge that lets it create the calendar event or draft the email instead of describing how you would. If you get deeper into building, Claude Code can talk to tools through APIs directly. Either way the principle is the same, and my rule stays the same too: it drafts, you send.

Context files what it knows Connectors what it sees live Projects where work lives Skills what it can repeat Recurring tasks what runs itself
Each layer builds on the one under it. Context makes connectors smarter, connectors make skills possible, skills become recurring tasks.

What to notice

  • Setup beats talent. The people getting real value are not better prompters. They did the eleven boxes.
  • Context is the multiplier. The about-me file and your documents change the quality of every single answer.
  • Answering needs context, acting needs a connection. Files and projects for knowing, connectors for doing.
  • One to three times, then it is a skill. Stop re-explaining processes you have already perfected.
  • It drafts, you send. Keep the last look on anything that leaves your name.
Claude out of the box is a smart stranger. An hour of setup makes it the assistant who has worked for you for years.

If this list feels long, start with the three that matter most: the account, the context file, and one connector. That is the short version, and I wrote it up as the day-one cheat sheet. When you are ready for the payoff of all this setup, go build the email agent.