Secure Your Spot
← Guides
Getting Started · Guide 1 of 7

How to learn Claude Code without being an engineer.

MakerSquare 10 min read Beginner

Claude Code is Anthropic's coding agent. You tell it what you want in plain English. It reads the files in a folder on your computer, writes new ones, edits existing ones, and runs commands. You watch, approve, and check the result.

You do not need to write code to use it. You need to say clearly what you want and check whether you got it. If you have ever briefed a contractor, you already have the core skill.

This guide gets you from nothing installed to three small things built. Every command below was checked against Anthropic's setup docs on November 3, 2026.

What you need before you start

1
A paid Claude plan or an API account
Claude Code works with a Claude Pro, Max, Ultra, Team, or Enterprise plan, or a Claude Console account with prepaid API credits. The free claude.ai plan does not include Claude Code. The learning material is free. The tool is not.
2
A Mac, Windows, or Linux computer
macOS 13 or newer, Windows 10 (version 1809) or newer, or a recent Ubuntu or Debian. At least 4 GB of RAM and an internet connection.
3
About an hour for the first session
Most of that hour goes to the terminal, not Claude Code. That time pays off once and you don't spend it again.

Don't want the terminal at all? Anthropic also ships Claude Code as a desktop app, a VS Code extension, and on the web at claude.ai/code. They work. This guide uses the terminal because Anthropic's docs and most of the help online assume you're there. It's also where we teach it.

Step 1: Get comfortable in the terminal

The terminal is a window where you type commands instead of clicking. It looks hostile because it gives you no buttons. You only need five commands to get around.

1
Open it
On a Mac, press Cmd+Space, type Terminal, and press Enter. On Windows, open the Start menu, type PowerShell, and press Enter.
2
Learn where you are and how to move
pwd              # where am I right now?
ls               # what's in this folder?
mkdir projects   # make a new folder called projects
cd projects      # go into it
cd ..            # go back up one level

These work in the Mac Terminal and in Windows PowerShell. None of them can damage anything. Type them until they feel boring.

3
Open the current folder in a normal window
On a Mac, type open . On Windows, type explorer . The dot means "this folder." It's the fastest way to see that the terminal and your regular files are the same thing.

Anthropic has a longer terminal guide for first-timers if you want more practice.

Step 2: Install Claude Code

Copy the line for your computer, paste it into the terminal, and press Enter.

# Mac, Linux, or WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex
1
Wait. It shows no progress.
The installer downloads quietly. When your prompt comes back, it's done.
2
Close the terminal and open a new one

Then check the install:

claude --version

You should see a version number followed by (Claude Code). If you see "command not found," the new terminal can't find Claude Code yet. Anthropic's install troubleshooting page walks through the fix.

3
Windows only: install Git for Windows
Anthropic recommends Git for Windows so Claude Code can use its Bash tool. Without it, Claude Code falls back to PowerShell. You'll want git anyway for Step 5.

Already use Homebrew on a Mac? brew install --cask claude-code works too. Homebrew installs don't update on their own, so run brew upgrade claude-code now and then. The installer above updates itself.

Step 3: Start your first session

Claude Code always works inside one folder. Make a practice folder and start it there.

mkdir my-first-project
cd my-first-project
claude
1
Log in
The first time, Claude Code opens your browser to sign in. Use the account with your paid plan. You only do this once.
2
Ask it something before you ask it to build

Type a question and press Enter:

what can Claude Code do, and what should a beginner try first?

This costs nothing and shows you how it answers. It can also answer questions about itself, so use it as your help desk.

3
Know the five controls that matter
Esc           # stop Claude mid-task so you can redirect it
Esc Esc       # (empty prompt) open the rewind menu to undo edits
Shift+Tab     # switch permission mode (more on this below)
/clear        # start a fresh conversation
/exit         # leave Claude Code

To pick up where you left off later, run claude -c from the same folder.

Step 4: Build three small things

Tutorials teach you a tool. Small real projects teach you how to work with it. Each of these takes one session and teaches something different. Start a new folder for each one.

Build 1 teaches: describe, look, adjust
A one-page website about something you know

Your side business, your neighborhood, a hobby. The subject doesn't matter. Being able to judge the result does.

Make a single index.html page for my dog-walking business in East Austin. Sections: what I offer, prices, service area, and how to book. Use a clean layout with large text. No frameworks, just one HTML file.

Open it with open index.html (Mac) or start index.html (Windows). Then ask for changes in plain English: "make the prices a table," "the header is too big." That loop is most of the job.

Build 2 teaches: running code, checking output
A cleanup script for a messy spreadsheet export

Put a copy of a CSV export in the folder. Customer list, transactions, anything with duplicates or bad formatting.

Read customers.csv. Write a script that removes duplicate rows by email address and saves the result as customers-clean.csv. Run it, then tell me how many rows you removed and show me three examples.

Now Claude Code runs commands, not just edits files. Check its count against the file yourself. If it needs to install something to run the script, it will say so. Read what it wants to install before you approve it.

Build 3 teaches: planning, memory, shipping
A small tool you'll use next week

A quote calculator for your service, a checklist page for a process you repeat, a page that formats your weekly numbers. Something with a real user: you.

Start in plan mode (press Shift+Tab until it says plan). Claude researches and proposes a plan without changing files. Push back on the plan before it builds. Then run /init to create a CLAUDE.md file so the next session remembers the project. Our CLAUDE.md guide shows what to put in it.

When it works, put it online. The Vercel and GitHub guide gets you a live URL.

Step 5: The walls everyone hits

1
"I'm afraid I'll break my computer"
Typing pwd, ls, and cd can't break anything. The real risk is Claude deleting or overwriting files, and you control that through permissions. Work in a dedicated project folder, and keep copies of anything you can't lose somewhere else.
2
Permission prompts, or the lack of them

The permission mode decides what Claude can do without asking. Manual asks before every edit and command. Plan only reads and proposes. Auto runs most things on its own with background safety checks. Recent versions start new terminal sessions in Auto.

For your first few sessions, press Shift+Tab until you're in Manual. Seeing every step is how you learn what it's doing. When a prompt shows a command you don't recognize, press Esc to decline and ask "what does that command do?" first.

3
Git, and why you need it on day one

The rewind menu (Esc Esc or /rewind) undoes Claude's file edits within a session. Anthropic is clear that it isn't a replacement for version control. Changes made by commands it runs aren't always tracked. Git is your real undo button.

You don't have to learn git commands first. Ask Claude:

Set up git in this folder and commit everything with a clear message. From now on, commit after each change that works.

Then read our git workflow for non-coders so you know what it's doing.

4
It says it's done, and it isn't
Claude Code will sometimes report success on something that doesn't work. Never take "done" on faith. Open the page, check the file, count the rows. A good habit is to ask "how do I check this worked?" before you move on.
5
It forgets everything between sessions
Each session starts fresh. A CLAUDE.md file in the folder fixes most of this, because Claude reads it at the start of every session. Run /clear between unrelated tasks too. A long conversation about one thing makes it worse at the next.
6
Vague requests get vague results
"Fix the bug" gets a guess. "When I submit the form with an empty email, the page goes blank. Make it show an error instead" gets a fix. Our guide to prompts that work applies here word for word.

How to keep going for free

Once the three builds work, you've learned the basics. These are the free resources worth your time, all from Anthropic:

1
Claude Code 101 on Claude Academy
Anthropic's self-paced intro course: 12 lessons, about an hour and a half. It assumes a little command-line familiarity, which you now have.
2
Claude Code in Action
The follow-on course for people already using it, covering longer tasks, configuration, and automating repeat work. Take it after a few weeks of real use.
3
The official docs
Start with the quickstart and best practices. They're written for engineers, but after this guide you'll follow them.

The resource that matters most is a backlog of your own small problems. Keep a list of tasks you do by hand that annoy you. Each week, pick one and hand it to Claude Code. You'll learn more from that than from another course.

If you'd rather learn it in a room

Some people do fine alone with the free material. Others start it twice and stall. If that's you, the problem is usually structure, not content. MakerSquare's 2-week in-person program in Austin teaches Claude Code in the terminal from day one, alongside GitHub, Vercel, and Supabase, and you build on your own project the whole time.

Keep reading

Claude Code is the main build tool in MakerSquare's 2-week program in Austin. Students open it on day one and use it to ship their own project, with a real database and a live URL.

See the 2-week program See the curriculum