This is the short version. The basics, your first real project, and where to go when you want more. You do not need to be a programmer. You need a clear first hour.
Five minutes to feel at home. Do these in order and the rest gets easy.
Open your terminal, type claude, and press Enter. When it is ready, type a real sentence. Try what can you help me with? You send a message by pressing Enter. That is the entire interface.
Claude works inside whatever folder you start it from. Before you run claude, move into the folder you want to work on. On Mac or Windows you can also just ask Claude to help you make a new folder. It will walk you through it.
Press Esc to stop Claude mid-task if it heads the wrong way. Type /help to see everything it can do. Type /clear to wipe the slate clean and start a fresh task. Those three carry you a long way.
That is fine, and Anthropic wrote a guide for exactly you. It opens a terminal step by step and gets you running.
Do not start with the big important thing. Start with something small you can finish today. Momentum is the goal.
A one-page website that says hello. A script that renames the screenshots on your desktop. A clean spreadsheet from a messy one. Small and real beats big and vague every time.
Tell Claude what you want to end up with, then let it figure out how. For example:
Make me a simple webpage that lists my three favorite books, with a clean modern look. Then show me how to open it.Claude writes the files, shows you the changes, and asks before it saves anything. You are always in control.
You do not have to get the perfect ask on the first try. React like you would with a person. Make the title bigger. That is not what I meant, I wanted a list. Undo that. Correcting as you go is how the good stuff happens.
Ask Claude to make a CLAUDE.md file in your project. It is a plain note Claude reads every time it starts, so it remembers how you like things. You build it up over time and it pays off fast.
"Fix the bug" is weak. "The contact form lets people submit it empty, stop that" is strong. The more precise you are, the less you fix later.
For anything bigger, start with "before you change anything, look around and tell me your plan." Approve the plan, then say go.
When you switch to something unrelated, type /clear first. A clean slate gives you sharper answers than a long, cluttered chat.
Claude knows its own manual. Stuck on what it can do? Just ask, in the chat: "how do I save my work with git?" or "what are skills?"
When you are ready for more, these are the real ones, straight from the source. Bookmark them.
Last thing. You are going to get stuck, and getting stuck is not a sign you are doing it wrong. It is the work. Everyone who is good at this got there by pushing through the same walls you are about to hit.
Pick one small thing. Finish it today. The rest builds from there.