How to Use Claude Code: A Step-by-Step Tutorial

from install to a daily workflow, without the jargon

So you've heard what Claude Code is — Anthropic's AI coding agent — and you want to actually use it.

Good news: the learning curve is shorter than it looks. This tutorial takes you from install to a productive daily workflow.

Step 1: Install and sign in

Open a terminal and install the CLI:

npm install -g @anthropic-ai/claude-code

Then move into any project folder and run claude. First launch walks you through logging in with your Claude account.

Prefer clicking to typing? Install the official VS Code extension instead — same agent, sidebar UI. Both paths are covered in the official Claude Code quickstart.

Step 2: Your first session

Don't start by asking for code. Start by asking for understanding.

Try: “What does this project do? Walk me through the structure.”

Claude Code will explore the files and explain the codebase back to you. Two things just happened: you verified it reads your project correctly, and it built context for the next request.

Step 3: Give it a real task

Pick something small and annoying. A known bug. A missing test. A TODO that has survived three sprints.

Describe the outcome, not the implementation: “The login page redirects to / after logout instead of /login — fix it.”

Watch it work: it locates the code, proposes edits, runs what needs running, and shows you the diff.

Your job is the review. Read the diff like a pull request. Approve, or tell it what's wrong in plain English and let it iterate.

Step 4: Set up CLAUDE.md

Create a file named CLAUDE.md in your project root.

Write down what a new hire would need: how to run tests, which package manager you use, naming conventions, files to never touch.

Claude Code reads it automatically every session. One file, permanent memory, dramatically more consistent output.

Daily workflows that stick

The bug-report loop. Paste the stack trace, let it hunt. Agents excel at multi-file cause-hunting.

Test-first tasks. Ask for a failing test that captures the bug, then ask it to make the test pass. The test becomes the agent's target.

The refactor sweep. Renames, API migrations, dead-code removal — batch the tedious stuff into one session.

PR review assistant. Before requesting human review, ask Claude Code to critique the branch. It catches the embarrassing stuff early.

Five beginner mistakes to avoid

1. Giant vague prompts. “Make the app better” produces confusion at scale. Scope down.

2. Skipping the diff review. Fast is not the same as right. Always read.

3. One endless session. Stale context breeds wrong assumptions. Start fresh per task.

4. No CLAUDE.md. You'll repeat the same instructions forever. Write them once.

5. Trusting without verifying. End tasks with “run the tests” — let the agent prove its work.

Next: see how it compares with the competition in Claude Code vs GitHub Copilot — or read the full explainer if you skipped it.

Claude Code Buster is an independent, unofficial parody game. It is not affiliated with, endorsed by, or sponsored by Anthropic, OpenAI, GitHub, Microsoft, Google, Meta or xAI. All trademarks belong to their respective owners and are used descriptively.