PART 1: THE FOUNDATION

Chapter 1: Getting Started Without Being a Developer#

What Claude Code Actually Is#

Before we install anything, let me give you the clearest mental model I can for what Claude Code is and how it differs from every other AI tool you have used.

Claude Code is a program that runs inside your computer’s terminal. When you launch it, it opens a text-based conversation interface — similar to a chat window, but inside the terminal instead of a browser. You type instructions in plain English. Claude reads them, thinks about what to do, and then takes action using the tools available on your computer.

Those tools include everything your computer can do: reading and writing files, running programs, accessing the internet, processing images and video, analyzing data, and managing projects. Claude Code does not just tell you what to do — it does it, right there on your machine.

The key distinction from Claude’s web interface (claude.ai) is this: the web interface is a brain without hands. Claude Code is a brain with hands. It can reach into your file system, grab a PDF, extract the data, create a chart, save it to your desktop, and tell you it is done — all from a single instruction.

The Terminal: Demystified in Five Minutes#

The terminal is the single biggest psychological barrier for non-technical users, so let me dismantle it right now.

The terminal (also called “Terminal” on Mac, or “Command Prompt” / “PowerShell” on Windows) is simply a text-based way to interact with your computer. Everything you do by clicking icons and dragging files in Finder can also be done by typing text commands in the terminal. The terminal is not more powerful because it is harder — it is more powerful because it is more precise and more automatable.

Here is all you need to know:

Opening the terminal on Mac: Press Cmd + Space to open Spotlight, type “Terminal,” and press Enter. A window with a text prompt appears. That is it. You are in the terminal.

What the prompt looks like: You will see something like this:

What you’ll see in your terminal:

krishna@MacBook ~ %

This tells you your username, your computer name, and your current location in the file system (the ~ symbol means your home folder). The % is where you type.

The only commands you need to know:

• cd — Change directory. This is how you navigate to different folders. cd Desktop moves you into your Desktop folder. cd .. moves you up one level.
• ls — List files. Type ls to see what files and folders are in your current location.
• pwd — Print working directory. Shows you exactly where you are in the file system.

That is genuinely it. Those three commands plus the ability to type Claude Code instructions in plain English are all the terminal knowledge you will ever need for this playbook. Everything else — every technical command, every program installation, every file operation — Claude Code handles for you.

Terminal, IDE, or Desktop: Choosing Your Interface#

Claude Code can run in three environments that matter for this playbook, and the choice matters more than you might think.

The terminal is where Claude Code was born, where it gets features first, and where it remains most powerful. Every new capability — agent teams, delegate mode, advanced permission controls, scripting and automation hooks — lands on the terminal before it reaches any other interface. This is not going to change in the foreseeable future. The terminal is Claude Code’s native habitat.

IDEs like VS Code and Antigravity support the Claude Code extension and provide a much better graphical experience. You get a visual file explorer, intuitive dropdown menus for selecting skills and plugins, inline code diffs, and sidebar tabs for managing multiple sessions. If you are already comfortable in an IDE, this feels more natural than a bare terminal. The tradeoff: some features are terminal-only, and the extension sometimes lags a release or two behind the terminal version.

The desktop app is the newest door in, and the friendliest. Download the Claude desktop app from claude.ai/download, sign in, and open the Code tab — that is Claude Code with a graphical interface, no terminal required. It runs the same engine as the CLI and shares all your configuration (CLAUDE.md files, MCP servers, skills, settings), so nothing you set up in one is lost in the other. The feature that matters most for this book’s audience is visual diff review: Claude proposes a change, you see exactly what will change in each file, and you click Accept or Reject. You also get a sidebar for parallel sessions, an integrated terminal and file editor, and a live preview pane for web projects. One Windows note: the desktop app needs Git installed for local sessions (most Macs include it already). And if you want zero installation at all, a browser version of Claude Code exists at claude.ai/code, running sessions in the cloud.

My recommendation: Learn on the terminal first. It teaches you the mental model of how Claude Code actually works — the working directory, the permission system, the tool-use flow — without a GUI abstracting those concepts away. The desktop app is a genuinely good on-ramp if the terminal is what has kept you from starting at all — but treat it as the training wheels, not the bicycle. Once you are comfortable, you can move to an IDE or the desktop app and appreciate the visual conveniences without being confused by what is happening underneath.

The best middle ground for most people in this playbook’s audience is Warp — a modern terminal application that adds autocomplete, clickable suggestions, AI-powered command search, and a generally friendlier interface without sacrificing any of the terminal’s feature completeness. Warp feels like an IDE for your terminal. I use it for all my daily work, and I recommend it as your starting point.

There is no single right answer here. Some people start on the terminal and never leave. Some move to the desktop app for the visual comfort. Some toggle between environments depending on the task. The important thing is knowing that the terminal is always the most complete option, and any other interface is a convenience layer on top of it.

Installing Claude Code#

Claude Code requires two things: the Claude Code binary installed on your computer, and an Anthropic account with a paid plan. Installation is one command, and the native installer handles everything — no Node.js, no package manager setup.

Step 1: Install Claude Code using the native installer (recommended)

The native installer is the official recommended path. It auto-updates in the background, has no dependencies, and works across macOS, Linux, and Windows.

In your terminal (Mac / Linux / WSL):

curl -fsSL https://claude.ai/install.sh | bash

In PowerShell (Windows):

irm https://claude.ai/install.ps1 | iex

That is it for the install. No Node.js, no npm, no Homebrew.

Alternative: Homebrew cask (macOS only). If you prefer to manage Claude Code through Homebrew alongside your other tools, there is now an official cask:

In your terminal:

brew install --cask claude-code

The tradeoff: Homebrew-installed Claude Code does not auto-update in the background. You will need to run brew upgrade --cask claude-code periodically.

Step 2: Launch Claude Code

Navigate to any folder where you want to work, and type:

In your terminal:

claude

That is it. Claude Code launches and presents you with a text input where you can start giving instructions.

The first time you run it, Claude Code will ask you to authenticate with your Anthropic account. Follow the prompts — it will open a browser window where you log in and authorize access.

Step 3: Verify It Works

Once Claude Code is running, type a simple instruction:

As a Claude prompt:

What files are in this folder?

Claude will read your current directory and list its contents. If that works, you are ready to go.

The First Run: What the Interface Looks Like#

When Claude Code launches, you see a clean text interface. At the top, it shows your current model (Claude’s version), and at the bottom is a text input area where you type instructions. Between them is the conversation — your instructions and Claude’s responses, including any actions it takes.

Key elements of the interface:

The input area: This is where you type. You can write short commands (“list my files”) or long, detailed instructions (multiple paragraphs describing a complex task). Press Enter to send.

Tool use indicators: When Claude Code takes an action — reading a file, running a command, searching the web — you see a brief indicator showing what tool it is using. This is how you know it is actually doing something, not just thinking.

Permission prompts: Claude Code asks for your permission before taking certain actions. The first few times you use it, you will see prompts like “Allow Claude to read this file?” or “Allow Claude to run this command?” You can approve individually or set up blanket permissions (covered in Chapter 2).

The status bar: At the bottom of the screen, you see status information — which mode you are in, your model, and other context.

The interface is structurally minimal. There are no buttons, no menus, no sidebars. It is a conversation between you and an agent that can take action. Everything happens through text.

The Working Directory: Why It Matters#

This is one of the most important concepts for non-technical Claude Code users, and it is the source of most early frustration. Let me explain it clearly.

When you open Claude Code, it runs “inside” whatever folder you are currently in. This folder is called the working directory. It is the context for everything Claude does. When you say “read the PDF in this folder,” Claude looks in the working directory. When you say “save this file,” Claude saves it to the working directory. When you say “analyze the data,” Claude looks for data files in the working directory.

**

Why this matters in practice: If you open Claude Code from your home folder (~) and ask it to “read the invoice PDFs,” but your invoices are in ~/Desktop/Invoices/, Claude will not find them. You need to either:

1. Navigate to the right folder before launching Claude Code:

In your terminal:

cd ~/Desktop/Invoices
claude

1. Or give Claude the full file path in your instruction:

As a Claude prompt:

Read the PDF files in /Users/yourname/Desktop/Invoices/

My recommendation: Always navigate to the project folder first, then launch Claude Code. This is what I call “working directory discipline,” and it is the single habit that will save you the most confusion as a new user.

For one-off tasks (downloading a video, converting a file), I typically open Claude Code from my Desktop or Downloads folder. For ongoing projects (a website, a research report, a content series), each project gets its own dedicated folder, and I always launch Claude Code from inside that folder.

In your terminal:

cd ~/Desktop/My-Research-Project
claude

This simple habit ensures Claude always knows where to find your files and where to save its outputs.

Changed your mind mid-session? Use /cd. You no longer have to quit and relaunch when you realize you are in the wrong folder. Type /cd with a path, and the session moves there — from that point on, Claude treats the new folder as its working directory, and if that folder has its own CLAUDE.md memory file (covered in Chapter 3), Claude reads it on arrival. Your conversation carries over intact.

In Claude Code:

/cd ~/Desktop/Invoices

One caveat for Warp users: Warp’s side-panel file manager follows your terminal’s folder, not Claude’s. After a /cd, the panel keeps showing the old folder even though Claude has genuinely moved. The panel and Claude are two different programs, each with its own idea of “the current folder.” Trust the /cd, not the sidebar — and if you want confirmation, ask Claude “which folder are you working in?”

Running Terminal Commands Without Leaving Claude#

Here is a trick many people miss for months. Inside Claude Code, start a line with an exclamation mark and it runs as a plain terminal command instead of an instruction to Claude.

In Claude Code:

! ls

That runs ls (list files) directly, right in the conversation. Two things make this better than switching to a separate terminal window. The output lands in the conversation, so Claude can see it. And Claude responds to it — run a command that fails, and Claude explains what went wrong without you having to copy-paste the error and ask.

You will not use this much on day one. But the first time a setup guide says “run this command,” you now know you can run it without leaving Claude — and get an instant explanation of whatever comes back.

How Claude Code Sees Your File System#

Claude Code has access to your computer’s file system — it can read files, create files, delete files, and navigate between folders. But it does not automatically know what is on your computer. It discovers your files when you tell it to look, or when it needs to find something to complete a task.

Think of it this way: Claude Code is like a new assistant who has been given keys to your office but has not explored it yet. They can open any drawer or filing cabinet, but they will not know what is inside until they look. Your job is to point them in the right direction.

Practical implications:

• Always give file paths when referencing specific files. Instead of “analyze the spreadsheet,” say “analyze the spreadsheet at /Users/yourname/Desktop/Q4-data.xlsx.”
• Claude can read most file types: PDFs, spreadsheets (CSV, Excel), images (JPEG, PNG), text files, Word documents, and more.
• Claude can create any file type: It can save text files, create images through Python scripts, generate PDFs, write spreadsheets, and produce HTML files that function as web pages.
• It respects your file system: Claude Code will not wander through your computer reading random files. It reads what it needs for the current task and nothing more.

You now have everything you need to install Claude Code, launch it, give it instructions, and understand how it interacts with your files. In the next chapter, we build out the power stack — the plugins, MCPs, and settings that transform Claude Code from a capable tool into an extraordinary one.