The word is "Code." The skill isn't.

A confession first

I avoided Claude Code like the plague. Not for a week — for months. The name did all the work: Code meant programmers, terminals, green text on black screens, a world with its own priesthood. I assumed I'd open it, be asked something I couldn't answer, and feel stupid. So I stayed in the chat window, where it was safe.

Then I tried it. And the thing I discovered — the thing this whole guide exists to tell you — is that the name describes what the tool writes, not what you need to know. Claude writes the code. You write sentences. I have since turned out professional, multi-page websites, cross-linked and search-engine ready, every project neatly versioned on GitHub, and I still could not write a line of JavaScript if you paid me.

What it actually is

You already know Claude the talker: you ask, it answers, and everything it makes lives inside the chat. Claude Code is Claude the doer. Give it a goal and it plans the work, creates real files, writes and runs the technical parts, checks its own results, and shows you what it made. It works in the place your project actually lives — a folder of files — instead of in a conversation that evaporates.

The comparison I give friends: chat-Claude is a brilliant consultant who hands you advice you then have to act on. Claude Code is a contractor who shows up with tools. You describe the kitchen you want; you don't operate the saw. Your job is the brief, the taste, and the final say — and it will ask before doing anything consequential.

What a session feels like

A session is one working conversation attached to one project. The rhythm, once you've seen it, is almost boring:

1. You describe the outcome

   In plain English. "I want a simple website for my consulting practice — warm, professional, three pages." That's a complete, legitimate instruction.

2. It plans and asks

   Claude proposes an approach, asks clarifying questions when the brief is thin, and requests permission before consequential steps. You answer like a person, not a programmer.

3. It builds while you watch

   Files appear. Progress notes scroll by. You can read along or just wait — minutes, not seconds, because it's doing real multi-step work.

4. You react, it revises

   "The heading feels too loud." "Make the whole thing calmer." "The About page should come first." Reacting to what you see is the actual skill, and you already have it.

Where it lives

Claude Code comes in several doors. The famous one — the terminal — is the last one you need. Non-coders should walk in through the web.

What "no coding skills" honestly means

Let me be precise, because you deserve the honest version, not the hype version. You will never need to write code. You will, over your first few projects, pick up maybe two dozen words of vocabulary — repository, commit, deploy — the way you picked up "CC" and "attachment" when email arrived. That's the whole tax. The glossary pays it for you, one plain-English sentence per term.

What you supply instead is the part machines are worst at: knowing what the thing is for, who it serves, what feels right, and when it's done. Every hour I've spent with Claude Code has been spent on those questions — direction and judgment — not syntax.

One warning in fairness: "no coding" does not mean "no attention." Claude Code is powerful, and power tools reward a routine. That's what Habits & Guardrails is for. Read it before your first big project.