How to Use Claude Code: Step-by-Step for Beginners

In my last post I explained what Claude Code is, in plain words. Today is the hands-on part. I've watched the same scene play out many times: someone hears that AI can build websites and bots on its own, gets excited, opens Claude Code, sees a black window with a blinking cursor, and closes it five minutes later. I get it. I used to look at a terminal like it was an airplane cockpit.

The good news: all the difficulty lives in the first twenty minutes. After that it's a regular back-and-forth, like working with a freelancer, except this one never sleeps, never gets sick, and never disappears for a week. So I've laid out the path so you can walk it step by step with a cup of tea and finish the evening holding your first real result.

Section 01What you need before you start

Gather everything up front so you don't have to hunt for anything midway. The list is short.

• A computer. Mac, Windows, or Linux. A phone won't do for this: the Claude mobile app can hand a task to the web version, but you'll want a real screen while you learn.
• A Claude account with a paid plan. Claude Code comes with Pro (about $20 a month, cheaper if you pay yearly) and Max ($100 or $200 a month). It isn't available on the free plan.
• An email address and a card. Any email works for the account, and a regular credit or debit card covers the subscription.
• Half an hour of quiet time and one small task. There's a whole section on picking the task below, but start thinking now about what's been bugging you: a personal site nobody has time to build, a folder of photos, a sales export you never get around to totaling.

You don't need to know how to program. You don't need technical vocabulary either: Claude Code understands everyday language and answers the same way. If you're still unsure whether to start with Claude at all, I wrote an honest comparison: Claude vs ChatGPT.

Section 02Where to run it: 4 options and which to pick

There's one Claude Code and several doors into it. Behind each one it's the same AI with the same abilities. The difference is how the window looks and how easy it is to get going. Here's a comparison so you don't burn the evening deciding.

My advice is simple. If you've never opened a terminal, start with the Claude app. It looks like any other program on your computer, and the first task goes by without stress. In a week or two, once you're comfortable, try the terminal: everything is the same there, just faster, with a couple of extra features. From here on I show both paths, the app and the terminal. Pick yours.

Section 03Step 1. Account and plan

If you already have a Claude account with Pro, skip ahead to step 2. If not, let's go in order.

That's it, your account is ready. One subscription unlocks both the regular chat on claude.ai and Claude Code. There's nothing extra to buy, and they share the same usage limits.

Section 04Step 2. Install Claude Code

Pick one of the two options and follow it through. Both take about five minutes.

Option A. The Claude app (easiest)

Option B. The terminal (one command)

The terminal is a text window where you type commands. On a Mac it's called Terminal, and you can find it through Spotlight (Cmd + Space, type "Terminal"). On Windows, open PowerShell from the Start menu. There's nothing scary in there. We're going to type exactly one line.

Section 05Step 3. Project folder and first sign-in

Claude Code works inside a folder. Everything it creates goes there, and everything in there, it can see. So the very first rule: one task, one separate folder. Don't open it on your desktop or in your Documents folder where your whole life lives. Create an empty folder with a clear name, like "personal-site" or "sales-review."

Now you're looking at an input box. You can type like you would in a messaging app. The hardest part is behind you. The fun part starts now.

Section 06Step 4. First task: a live dialogue

For your first run, pick a task whose result you can see with your own eyes in a couple of minutes. A one-screen personal site is perfect: you open it in the browser right away and understand how the whole thing works. Here's the full dialogue as it looks on screen, so you know what to expect.

Notice two things. First, it told you the plan and then did the work. Second, before creating the file it showed you exactly what it would write and asked permission. You click "yes" (or press 1 in the terminal), and the file appears in the folder.

Double-click index.html and take a look. You'll probably want to change something. That's normal, that's the whole idea. Keep going in the same plain language:

That's the whole secret. You describe, it builds, you look and refine. Two or three rounds and the site is done. By the way, Claude Code can also help you put a page like this online if you ask, but that's the next step and needs your hosting access. For a full project from voice notes to a finished site, see building a site by voice with Claude Code.

Section 07Step 5. Permissions and modes

The thought that scares beginners most is "what if it deletes something." Here's how it actually works. By default, Claude Code asks permission for anything that changes files or runs programs. It shows what it wants to do and waits for your answer. The options usually look like this:

• Yes – do this action once.
• Yes, and don't ask again for this kind of action in this folder. Handy when it asks to create a file for the tenth time.
• No – and tell it right away what to do instead. It'll adjust.

On top of that there are work modes you switch with Shift + Tab (in the app it's a toggle next to the input box):

I strongly recommend plan mode for anything bigger than a one-page site. Turn it on, describe the task, get a plan of five to ten points, edit it in plain words ("drop point three, the site is one page"), and only then let it run. That way you don't burn your limits on work that went the wrong way.

Two more keys take away almost all the fear. Esc stops Claude Code mid-sentence when you see it heading the wrong way. Double Esc opens a list of previous steps, and you can roll back to the moment before a bad edit. The /rewind command does the same thing. Think of it as "undo" in Word, but for the whole job at once.

Section 08Step 6. Project memory: the CLAUDE.md file

Every new Claude Code session starts with a blank slate. It doesn't remember that yesterday you agreed on beige colors, or that you call the people you work with clients, not patients. So you don't have to explain it every time, the project has memory: a CLAUDE.md file in the folder. Claude Code reads it on every launch.

Setting up memory is easy: type the /init command. It studies the folder and creates CLAUDE.md with a description of the project. After that you can add to it in ordinary words, right in the conversation:

It adds these rules to the file, and tomorrow, when you open the same folder, you pick up right where you left off. What's usually worth saving to memory:

• who you are and what you do, in a sentence or two;
• who the project is for and what tone it has;
• colors, fonts, contacts, and links that keep repeating;
• rules like "don't delete old versions, move them to an archive folder";
• mistakes it has already made and shouldn't repeat.

The last one is the most valuable. Every time you correct Claude Code, say "remember this in CLAUDE.md." A month later you'll have an assistant that knows your habits better than a new hire. The same knowledge-base idea exists in the regular chat too, I wrote about it in Claude Projects.

Section 09Beginner command cheat sheet

Commands start with a slash and go right into the input box. You don't need to learn all forty. Here are ten that will cover your first months. /help shows the full list.

Two more tricks make life much easier. The @ symbol plus a file name points Claude Code at a specific file: "look at @price.xlsx and total the revenue." And you can simply drag a screenshot into the window or paste it from the clipboard, and it will see the image. That's a lifesaver when it's easier to show an error than to describe it.

Models are simple. By default, work on Sonnet 5: it's a sensible balance of speed, quality, and limit usage. For hard tasks that need a lot of thinking, switch to Opus. Light errands like "rename these files" are easy work for the fast Haiku 4.5.

Section 10How to give tasks: a formula and 12 ready phrases

Claude Code is exactly as good as your task is clear. People who say "nothing works" write something like "make me a nice website" nine times out of ten. That's like walking up to a designer and saying "just make something." They will. Something.

I use a simple four-part formula. Keep it in front of you for the first few weeks.

1. Who I am and why. "I'm an English tutor and I need a page for parents."
2. What already exists. "The folder has my prices in price.xlsx and three testimonials in reviews.txt."
3. What the result should be. "One page: who I am, prices from the price list, testimonials, and a booking button."
4. Constraints. "No animations, large font, must open fine on a phone."

And here are twelve phrases you can copy and fill in with your own details. Each one has been tested on real tasks.

• "First look through the folder and tell me what's in it. Don't change anything."
• "Show me a step-by-step plan. I'll approve it, then go."
• "Ask me whatever questions you need to do this well."
• "Build a one-screen personal site: [who you are, how you help, where the button goes, colors]."
• "Look at the export @sales.csv and calculate revenue by month, the top 10 clients, and the average order value. Save the result to a report.xlsx spreadsheet."
• "Sort all the photos in this folder into subfolders by the year and month they were taken. Don't delete anything."
• "Rename every file in the folder using the pattern date-title. Show me the list of new names first."
• "Turn my notes in the notes folder into one guide in Word with a table of contents."
• "Make a page with a booking form: name, phone, preferred time. Save submissions to a file."
• "Check this site for problems: broken links, typos, how it looks on a phone."
• "Explain in plain words what you just did and which files you changed."
• "Save what we just decided to CLAUDE.md."

I especially recommend the third one. When you're not fully sure what you want, ask Claude Code to question you. It'll ask about your audience, colors, copy, and where to send people, and after five answers the task gets several times clearer. More ways to talk to AI are collected in the AI prompt library.

Section 11Five first projects by profession

So you're not staring at an empty input box, here are first-project ideas for people who sell services, courses, and consulting. Each takes one evening and brings real value.

Notice that not one row says "write code." You describe the result the way you'd describe it to an office assistant. Once you feel confident, move on to bigger tasks: a Telegram bot that answers common questions (walkthrough in a Telegram bot without a programmer), or connecting your own tools through MCP, covered in MCP in Claude. For the big picture on building things by conversation, read the piece on vibe coding.

One client, a sales mentor, started with exactly a spreadsheet. First he asked Claude Code to pull every lead from his message history into it, then to calculate conversion from lead to payment, then to chart it week by week. Three evenings later he had his own small analytics setup that he'd been planning to hire a contractor for. And the main thing, in his words: "For the first time I saw at which step people drop off."

Section 12When something goes wrong

Every beginner hits the same snags. I've collected them in one place so you don't have to dig through forums.

The general principle: show any confusing message to Claude itself, in Claude Code or in the regular chat. It's better at untangling its own errors than any forum. For a big rundown of typical mistakes with AI, see beginner mistakes with AI.

Section 13Usage limits and how to stretch them

On Pro you don't pay per request, but it isn't unlimited either. There's a limit over a few hours and a weekly limit. Claude Code uses noticeably more than the regular chat, because it reads files, tries things, and checks its own work. For tasks like "personal site, spreadsheet, report," Pro is plenty. Once you're spending several hours a day in Claude Code, take a look at Max.

Here's what actually saves limits:

• One task, one conversation. Finished the site? Type /clear and start the sales report on a clean slate. A long conversation drags all the previous text along and costs more.
• The right model. Sonnet 5 for everyday work, Opus only for genuinely hard stuff, Haiku 4.5 for small errands.
• Plan mode before a big task. Agreeing on the approach in words is cheaper than redoing finished work.
• Small folders. Don't open Claude Code in a folder with thousands of files, it will try to study them. A dedicated folder per task saves both time and limits.
• A precise task the first time. Every "no, not that" round costs limit. The four-part formula pays for itself right here.

Check what's left with the /usage command. If you want a broader overview of which AI tools to use for which tasks and what they cost, see the best AI tools of 2026.

Section 14Safety: five simple rules

Claude Code gets access to your computer, so a little hygiene doesn't hurt. The rules are simple and easy to follow.

1. A separate folder for every task. Never launch it at the root of your drive or in the folder with all your documents.
2. Read permission requests. Especially when it wants to delete, send, or install something. If you don't understand an action, ask: "Explain in plain words what this command will do."
3. Don't type passwords or keys into the chat. If it needs access to a service, ask Claude Code where to store the key safely, and put it there yourself.
4. Back up anything important. Working with valuable files? Copy the folder first. Two seconds, and you'll sleep better.
5. Check everything that goes out. Numbers in a report, links on a site, the text of an email campaign. Final review is on you, especially where money and client data are involved.

Section 15The whole path in one minute

Let's run through the essentials so it all clicks into one picture.

• You need a computer and a Claude Pro or Max plan.
• The easiest start for a beginner is the Claude app, Code tab. The terminal installs with one command and gives you the same abilities.
• Create a separate empty folder for each task and open Claude Code right there.
• Keep the first task small and visible: a personal site, a spreadsheet, a report. Use the formula: who you are, what exists, what result you need, constraints.
• Approve important actions, turn on plan mode before a big task, undo a bad step with double Esc.
• Create project memory with /init and add everything you agree on.
• One task, one conversation, /clear between tasks, Sonnet 5 by default. That way your limits last a long time.

That's it. Honestly, the hardest part of Claude Code is deciding to open it for the first time. After that you talk and it does the work. Pick one small task that's been hanging over you and get it done tonight. Ready to try? 🙂