Most Claude setup guides open with a feature tour. The setup that actually changed my work started with a handful of plain text files.
To set up Claude AI, choose a plan, install the desktop app, and write a few short context files before you ask for anything: one about you, one about the content you create, and one listing the AI habits you want it to avoid. That hour of setup is what makes every prompt after it short.
I create SEO content for a living. Claude runs the work side of my day, and ChatGPT handles my personal projects. I’ve been on a paid Claude plan since the start, and the order below is the one I’d hand a friend who asked me to set them up tonight.
Three Key Takeaways: Setting Up Claude AI
- Match the plan to the job. Claude’s Free plan covers chat, memory, connectors and up to five projects, while Pro at $20 a month adds Cowork, scheduled tasks and Claude Code.
- Write your rules before your first request. An about-me file, a content preferences file and an anti-AI rules file do the work that long prompts used to do.
- Done beats perfect in hour one. Skills, automation and Claude Code can wait until rough versions of your files are running on real work.
Which Claude Plan Should You Start On?
Start on Free if you’re testing Claude for personal use, and on Pro if you’ll use it for paid work. As of November 2026, Free covers chat, memory, connectors and up to five projects. Pro costs $20 a month and adds Cowork, scheduled tasks and Claude Code.
| Plan | Price (USD, November 2026) | What stands out |
|---|---|---|
| Free | $0 | Chat, memory, connectors, skills, up to 5 projects |
| Pro | $20 a month, or $17 a month billed annually ($200) | Unlimited projects, Cowork, scheduled tasks, Claude Code |
| Max | $100 a month | Everything in Pro with higher usage limits |
| Ultra | $200 a month | The top individual tier |
I went straight to Pro. I write for a living, so paying $20 a month for the tool I write with was a no-brainer. If Claude is going to touch paid work, the Pro features are the ones that save real hours.
The catch: plan names, prices and limits shift every few months, so check Claude’s pricing page before you subscribe. If you’re unsure, start on Free and upgrade the day you need Cowork or hit a usage wall.
Do You Still Need the Claude Desktop App?
Yes, if you want Claude working with files on your computer, but the line between the apps has blurred. Claude chat and Cowork, the mode built for multi-step tasks, now share one home across web, desktop and mobile, and sessions sync between them. The desktop app still handles anything that touches your local folders.
When Cowork launched, it was a big deal for me. That’s where Claude went from chat toy to teammate. Before Cowork, every job meant walking Claude through it one prompt at a time. With Cowork, it wasn’t hand holding step by step anymore, and for months I worked in Cowork almost exclusively for its desktop capabilities.
Today the distinction matters less. I run the same setup from my phone and switch laptops without losing my place, because the sessions live in the cloud. Use whichever app fits the moment, and keep the desktop app for anything that needs your files.
A few details from Anthropic’s Cowork guide worth knowing on day one:
- Sessions run in the cloud, so they keep going if you close the app.
- Anything that touches your local files needs the desktop app open.
- Scheduled tasks run in the cloud even when your device is offline.
Not everyone wants an AI connected to their computer, and that’s a fair call. If that’s you, the web app handles the chat side without connecting a single folder.
What Files Should You Write Before You Ask Claude for Anything?
Write three or four short Markdown files before your first real request: an about-me file, a content preferences file, an anti-AI rules file and, if you publish online, an SEO rules file. Claude reads them as standing context, so you stop re-explaining yourself in every chat.
Here’s what goes in each one:
- About you. Who you are, what you do, what you know, the content you create, even how you work. Mine notes that I work in two-hour blocks.
- Content preferences. Branding, formatting and tone. Mine asks for conversational but authoritative: professional, not boring, and warm.
- Anti-AI rules. Words and patterns Claude should avoid and fix on sight. Mine bans “delve” and the “It’s not X, it’s Y” construction, among others.
- SEO rules (optional). Keyword placement, header style, answer paragraphs, linking.
Before this setup, every writing job started with me pasting the same context: who it’s for, what we’re writing, my rules. Now that context sits in place ahead of time for each brand, content type and audience. I tell Claude which client and market I’m writing for and what kind of piece I need, and it knows what to get me.
Claude’s Projects feature keeps this tidy. Each project holds its own files, instructions and memory, so one brand’s rules never bleed into another’s. For the full eight-file version, see 8 Files That Make Claude Actually Useful.
Renzie’s Take:
Most people meet Claude like a search box: type a question, hope for the best. I treat the first hour more like onboarding a new hire: tell it who I am, what we make, what we never say.
You can establish a whole bunch of rules before it even starts doing content, and once those rules exist, my prompts shrank to a single line: here’s the topic, here’s the angle, go.
What Should You Ignore in Your First Hour?
Ignore anything that tempts you to perfect the setup. Skip skills, scheduled tasks, plugins and Claude Code for now. Write rough versions of your files, run one real task, and fix the files when the output misses. Done beats perfect, and the files get better with use.
My day job runs on time budgets for a reason. It’s easy to lose an afternoon researching one more angle or polishing one more paragraph, and setup is the same trap. Done is better than perfect, and a rough about-me file that’s working tonight beats a flawless one you finish next month.
When a draft does come back off, check your own files first. In my experience, most misses trace back to an unclear or conflicting instruction, and Claude will often point that out if you ask it what wasn’t clear. Better yet, add one line to your rules telling Claude to ask questions whenever something is unclear.
The advanced features earn their place later, once your context files are carrying real work. And if you only ever want a smarter chat window, you may never need them. That’s a perfectly good way to use Claude.
The Bottom Line: Write the Rules, Then Let Claude Work
- Pick the plan that fits the job: Free to test, Pro for paid work.
- Install the desktop app if you want Claude working inside your files.
- Write your context files before your first real request, and keep them rough.
Write your about-me file tonight, then give Claude one real task tomorrow.
Once your setup is running, the Complete Guide to Claude AI walks through the next four stages. For the bigger picture, start with AI for Real People or see how to build a personal AI workspace.
