This is the walkthrough for someone who has heard of Claude Code, maybe installed it, and hasn't actually run a real task yet. No prior AI-tool experience assumed — just enough to get from a blank terminal to your first reviewed, approved change.
You need three things: a terminal you're at least a little comfortable typing into, Node.js installed on your machine (Claude Code is distributed as an npm package), and a folder to work in — an existing project if you have one, or an empty folder if you just want to practice first. You do not need to already know how to code. You do need to be willing to read what Claude Code proposes before approving it — that habit matters more than any technical prerequisite.
Claude Code installs globally through npm, the same way most command-line developer tools do:
npm install -g @anthropic-ai/claude-codeOnce that finishes, open a terminal inside the folder you want to work in and start it:
cd your-project-folder
claudeThe first run will walk you through signing in. After that, you land in an interactive session inside your terminal — this is where the rest of the work happens.
This is the part most tutorials skip and most beginners worry about most: Claude Code does not silently rewrite your files. When it wants to edit a file, run a shell command, or take any action with real effects, it shows you exactly what it's about to do and waits for your approval before doing it. You can approve one action at a time, or pre-approve a scoped set of actions for the rest of a session if you're comfortable with the kind of work it's doing. Nothing irreversible happens without you seeing it first — that review step is the actual safety mechanism, not a setting you have to go find and turn on.
Skip the temptation to start with something big. A first task that's small, concrete, and easy to check is worth more than an ambitious one you can't evaluate.
If your folder is a git repository, make sure everything is committed before you start. This isn't optional caution — it's what makes "undo" trivial no matter what happens next.
Instead of "open the CSS file and change line 40," try "make the header background dark navy instead of white." Claude Code figures out which files to touch — describing the result gives it more useful information than pre-deciding the implementation for it.
Claude Code will show you what it intends to edit or run. Actually read it — even a partial read is enough to catch something that doesn't match what you asked for.
Once you approve, open the file or reload the page and confirm it actually did what you expected. Don't take the summary text as proof — look at the real output.
If it's not quite right, say specifically what's wrong rather than starting over. "The navy is too dark, make it a shade lighter" is a better follow-up than re-explaining the whole task.
Two things cover almost every beginner problem. First, if a proposed change looks wrong or you don't understand it, don't approve it — ask Claude Code to explain what it's about to do in plain language, or ask for a smaller version of the task. Second, if something already got applied and you don't like it, and your project is a git repo, you can revert it the normal git way — this is the entire reason step one of the walkthrough above matters. Neither of these requires you to already be technical; they're the same review habits that make the rest of the workflow safe.
This tutorial covers the first 30 minutes. A project-based course covers the rest — building real landing pages, SEO automation, and business workflows with Claude Code, plus 180+ HTML/CSS/JS templates included.
See the Course — $35 →No. You need basic comfort typing commands into a terminal and reading what comes back. Claude Code writes the code — your job in this tutorial is describing what you want and reviewing what it proposes.
Claude Code has its own pricing set by Anthropic, separate from this tutorial. Check their site for current plans.
Don't approve it. Ask it to explain the change in plain language first, or ask for a smaller, more specific version of the same task. Approving changes you don't understand is the single habit most likely to cause real problems later.
If your project is a git repository, yes — commit your work before starting a session, and any change can be reverted the normal git way. This is the single most useful habit to build before your first real task.