Your self-paced path from "I have a Claude account I barely touch" to "Claude is the first thing I open when I have something to do." Go at your own speed. Nobody is waiting on you, and you can't fall behind.
Three sections that build on each other: co-work, then code on the desktop, then code in the terminal. New to all of it? Start at the top and go in order.
We won't assign you a project. Bring something you want to make, or bring nothing and pick from a menu of real tasks when you're ready. Both work.
Claude as a coworker, inside the desktop app. No code, no terminal. This is where everyone should begin.
Most people use Claude like a search box. You type a question, you get an answer, you copy the good part out, you move on. That works, and it's also about 10% of what it can do.
Co-work is different. In the Claude desktop app, you can give Claude access to a folder on your computer, and now it's not answering questions in a vacuum. It can read your files, work with what's actually there, and hand things back to you. It stops being a clever stranger and starts being a coworker who knows what you're working on.
This is the only fiddly lesson. Take it slow and you'll be fine.
claude.ai/download and install it for your computer (Mac or Windows). The desktop app is what unlocks co-work. The browser version won't do this part.claude-sandbox. This is your playground, separate from anything important.claude.ai. The real app comes from Anthropic.Don't overthink this one. The goal is just to feel what it's like to hand something off. Open a conversation and talk to Claude the way you'd talk to a person. Out loud is fine, if you use voice. Messy is fine. You don't need the perfect words.
Pick one small task to start with. Something real, something low-stakes, something that would genuinely save you ten minutes. Here are starters if nothing comes to mind:
Give Claude the task, then talk with it. If the first answer isn't right, say so plainly: "that's too formal," or "you missed the deadline," or "shorter." It adjusts. That back-and-forth is the actual work, and it's how you'd manage any good coworker.
In the last lesson you mostly pasted things in. Now let Claude work with what's already in your folder, because that's where it gets genuinely useful.
Drop a couple of real files into your sandbox folder. Nothing precious. A document, a spreadsheet, a few notes. Then ask Claude to actually use them:
Watch what happens. Claude reads the file, works with the real content, and hands it back. You didn't copy and paste anything. This is the moment most people feel the click, when it stops being a chatbot and starts being someone who knows your stuff.
Time to finish something you keep. Not an exercise, a real output that exists when you're done. Pick one task and take it all the way through, with Claude doing the heavy lifting and you steering.
Work it like a project. Hand it off, react to drafts, push back, refine, until it's actually good. When you've got something you'd genuinely use, you've done co-work for real. Everything in the next two sections is the same skill, pointed at more powerful tools.
Same coworker, more powerful tool. Now Claude builds real, working things, and you still never touch a terminal. Do the co-work section first.
In the last section, Claude worked with documents and words. That's co-work. It's powerful, and for a lot of what you do, it's all you need.
Code is the next door. Instead of handing you a document, Claude builds something that runs. A webpage. A little tool. A page that does something when you click it. You don't write the code, and you don't need to read it. You describe what you want, Claude builds it, and you look at the result and say what to change.
The good news: it's the exact same skill you already built. You talk to a coworker. The coworker just happens to build webpages now.
You already have everything installed from the co-work section. This is about pointing Claude at a building job instead of a writing job.
claude-builds. Each thing you make gets its own home, so nothing gets tangled..html). Open it, and you're looking at a real webpage you just made by describing it.Time to make something. Pick one thing from the menu, or bring your own, and ask Claude to build it. Start simple. You can always make it fancier once it exists.
Describe it to Claude in plain language: what it's for, what should be on it, and any vibe you want ("make it warm and friendly," "use my brand colors, here they are"). Let Claude build it, then open it up and look.
Building it once is good. Changing it is where you actually get powerful, because real things are never right the first time.
Go back to what you built and start asking for changes, the same way you'd give notes to a designer:
Make the change, open the page again, see the difference. Then do it again. This loop, describe, look, adjust, is the entire rhythm of building with AI. Once it feels natural, you're no longer a beginner. You're someone who builds.
The full Claude Code experience, plus a real project to put it all together. This is the last section, and the one that opens the most doors. Do the first two sections first.
The terminal is that plain text window you've seen over someone's shoulder and assumed was only for "real" programmers. Here's the secret: it's just another way to talk to your computer, and with Claude Code, you talk to it in normal English.
So why leave the friendly desktop app? Because the terminal is where Claude Code is most capable. It can work across many files at once, build bigger things, run them, fix them, and handle real projects, not just single pages. Everything you've done so far has been Claude with one hand tied behind its back. This unties it.
This is the one setup lesson of the section. Go slowly. If a step looks unfamiliar, that's normal, and Claude itself can help you through it.
It looks different, but it's the same conversation you've been having all along. Type what you want in plain English and press enter. Try a few small things to get the feel:
Notice that it can do everything the desktop app did, and more, because it's working right inside your folder with full reach. The rhythm hasn't changed one bit. Describe, look, adjust. You just have more power behind each request now.
You've got the whole toolkit now: co-work for thinking and writing, code on the desktop for making things, and the terminal for the real, bigger builds. The last move is to point it all at something that matters to you.
This is where a project finally earns its place. Not a practice exercise, a real thing you want to exist. Bring your own, or pick one:
Work it the way you've learned: describe, look, adjust, repeat, until it's real and you're proud of it. Take your time. A project you care about is worth a few weeks of evenings.