Here's 90% of everything you need to know to start using Claude Code effectively, in under 5 minutes.
Claude Code is the best tool in my opinion, for founders who want to automate their business, even if you aren't a coder and don't plan on writing any code. You can use it for marketing, sales, and operations, tasks that have nothing to do with coding. (And it's also better than Claude Cowork, I'll cover that later).
So here it goes, if you just follow and understand these 9 steps, you can use Claude Code almost like a pro.
Step 1: Pick the Right Interface (Not the Terminal)
There are currently three ways to run Claude Code:
The Claude desktop app
The CLI (terminal)
A plugin inside an IDE like VS Code or Cursor
The CLI is the classic version. It lives in your terminal and looks technical, which is exactly why people think Claude Code is only for coders. The capabilities are the same as the desktop app, it just looks scarier.
As a non-coder, ignore the terminal. Google "Claude desktop app," download it, and switch to the Code tab. It does everything the terminal does with a friendly interface, and you can preview and edit files right inside the app. About 95% of my usage is through the desktop app.
Step 2: Understand the Local Folder
The biggest difference between Claude chat and Claude Code is where they run.
Think of it like Microsoft Word vs Google Docs.
Claude chat lives on the internet, like Google Docs. Claude Code lives on your machine, like Microsoft Word. But, because it runs locally, it has more power. It can read and write a bunch of files for you fast and take actions across your computer.
When you start a new chat, select "Local", then pick the folder it should operate from. When you're starting out, just create one empty folder in your home directory and select it. That's your "home base". Now when you tell it to create a file for example, it will create it inside of this folder.
(If you want to optimize this folder structure, watch my youtube video about my ClaudeOS system).
FYI this doesn't lock it to that folder. It just defaults there. If you paste it the path to any other folder on your machine, it can go read and operate in the other folder too.
Step 3: Turn On Auto Permissions
Under the chat box there's a permissions setting: manual, accept edits, plan, auto, bypass (see screenshot above).
Set it to auto. On manual, it pops up and asks every single time it wants to read or write a file, which gets annoying fast and slows you down. Auto decides for you when it actually needs to ask. Plan mode is mostly for writing big features in code, so as a beginner you can skip it.
Step 4: Set Your Model and Effort
Two settings worth knowing:
Model: I run Opus 4.8 with fast mode for most things. For quick, simple questions, drop to Sonnet 5 or Haiku since they're faster and cheaper. Fable 5 is the smartest, but you only need it for something really complex or long-running. If you're on the Max $100 you usually don't run into limits if you use it normally like this. If you're on the Pro $20 plan, then lean towards using Sonnet and Haiku.
Effort: a slider for how hard it thinks. High is a good default. Bump it up when the result really matters, drop it when the task is small. High to extra is the sweet spot between smart and fast.
That's the entire setup and basics out of the way. Next let's make it actually useful.
Step 5: Know How It's Different From Other Tools
This trips beginners up, so here's the quick map:
Claude chat: you ask, it answers.
Claude Cowork: it does things for you, but it's sandboxed in the cloud.
Claude Code: fewer shackles, runs on your whole machine, most powerful. This is what I use for most things.
Codex / ChatGPT work: OpenAI's version of the same idea.
OpenClaw, Hermes, Viktor: same engine, but you talk to it through Slack, Discord, or WhatsApp as a bot.
N8N and Make: classic automation tools that are basically outdated now. Anything you'd build there, you can build faster in Claude Code.
My guess is all of these modes eventually merge into one. For now, Claude Code is the strongest option imo.
Step 6: Connect Your Tools (This Is What Unlocks It)
Claude Code gets powerful when you connect it to your other software and let it work across those tools.
Easiest way: In the Claude desktop app click Customize, then Connectors, then Browse connectors. That's the Claude marketplace/directory. Click into any tool, like Figma, read what it can do under Tools, then hit Connect and log in.
If a tool isn't in the marketplace, search "[tool] mcp" on Google. Some tools will have an MCP, but are not in the official marketplace. Just find the MCP connection URL in their docs, then click Add custom connector and paste it.
For tools with no MCP at all, let Claude use the browser. There's the Claude in Chrome extension, and now a browser built directly into the desktop app where you can stay logged into your accounts. Just tell it "open YouTube" and it does.
One more: meta connectors like Composio. You connect Composio once, then connect all your other apps inside it. Sometimes those connections are more capable than the native ones (Google Sheets, for example), and if you ever switch from Claude to another ecosystem, you only migrate one connection instead of all of them.
Step 7: Use Skills (Saved Prompts)
A skill is just a saved prompt. That's the simplest way to think about it.
To create one, open a chat and describe the steps. For example: "Create a skill. Step one, go into Fathom and fetch the transcript. Step two, summarize it," and so on.
Skills you create in Claude Code save locally, inside the hidden .claude/skills folder in your working directory. Each one just contains a plain English SKILL.md file. Skills you create in Cowork save to your Claude account instead.
Once saved, trigger a skill by typing "/" and selecting it. That's the whole point, describe a workflow once, run it whenever you need by typing the slash command.
Step 8: Set Up Routines (Automations)
Routines are automations: a trigger plus what it should do when it fires.
Create one in the Routines tab, or just ask in chat: "Create a test routine." It builds it and it shows up in the tab.
There are two types:
Local: runs on your machine. Simple to set up, but only fires when your computer and Claude desktop are on. Most of my routines are local because my app is always running.
Cloud: hosted in the cloud, so it runs even when your computer is off. Takes a bit more setup, but it's the way to go for anything that needs to run constantly, like a daily job. This is your replacement for N8N and Make.
Step 9: Mobile Options (Not Great Yet)
I'll be honest, mobile phone usage isn't great yet. There are some options though, if you want to use claude code on your phone:
Remote Control: turn it on in the Claude Code settings, and new chats become accessible from your phone's Claude app. It's good for continuing a session you started on your laptop. But it doesn't really let you start one, as long as it's local.
Dispatch: one channel you can reach from both desktop and phone. This feature was actually built for Cowork, but can also be used through Claude code. It's not great because it's all one big chat, but works for simple things.
The big problem with both of these options is, that it only works if your laptop is on and claude code is running.
So if your usage in general is heavy on your phone, a tool like OpenClaw, Hermes, or Viktor might fit you better. If you mostly work on your laptop, Claude Code is excellent.
That's 90% of everything you need to start using Claude Code as a non-coder.
Download the desktop app, create a folder, set it to auto, connect one tool, and build your first skill. You'll be automating parts of your business the same day.
Hope this helped.
-Moritz
P.S.
If you want help automating your business, come work with me. We'll look at your business and map out which parts to automate so you get more done with better margins: joinagentos.com
For more free prompts, guides, and AI automation tips, join the Prompt Warrior community: skool.com/promptwarrior
