Free course: Getting started with Claude Code
A free course from the MemberPress.ai Academy: give Claude Code a small job on your project, read every change it makes, and know when to step in.
You run a membership, and somewhere on your list there’s a small fix to your site’s code that keeps waiting for a free afternoon. Claude Code can take that kind of job: you give it a task, and it reads and edits the files in your project. But most people install it, point it at their biggest project, ask it to clean things up, and get back hundreds of changed lines they can’t judge.
Claude Code: Getting Started is a free course in the MemberPress.ai Academy for doing it carefully. It’s open to everyone and set at an intermediate level: eight lessons, 2 hours 10 minutes in all.
Who it’s for
Someone already comfortable with Claude who wants to try Claude Code on a real project. You’ll work in the terminal, the window where you type commands, and the first lesson walks you through installing Claude Code there and signing in.
What you’ll be able to do
By the end, Claude Code is installed and answering in your terminal. You know how to give it a small, clear job and how to read the diff, the list of every line that changed, shown in red and green. You know when to step in and when to let it run. And you’ve taken one small, real fix all the way to a merged pull request, the request that adds a change to your project’s code.
Lessons worth starting with
- Reading the diff. That’s the video on this page. Claude’s summary is what it meant to do. The diff is what it actually did. This lesson gives you a thirty-second scan before you read line by line: look for new imports (code a file now depends on that you never chose), deleted lines, especially a deleted “if” check, and any function whose inputs changed. Watch lesson 3.
- First task: let it edit a file. Pick something small and easy to undo. The test: can you read every change in under two minutes? Anything touching logins, payments or your database waits for later.
- When to interrupt, when to let it run. A run has gone wrong when Claude opens files that have nothing to do with the job, when its plan grows bigger than what you asked for, or when the same test fails three times while it tries something different each time. Then press Escape and say what you see.
- Tests as the safety rail. Tests are small checks that tell you straight away when a change breaks something. Run them before Claude starts and again after it finishes.
Start with one small fix
Pick one small fix. Then open Claude Code: Getting Started and start with lesson 1, or jump straight to Reading the diff and learn the habit the whole course is built on: reading every change before you keep it. The course is free, and the time you get back is yours to spend on your members.
Get your membership to its first paying member.
Connect your site and tell Opal what you sell. She sets up your Join and Checkout pages and tells you what’s left before anyone can pay, like connecting your own Stripe or PayPal. Your password never leaves your site.
Connect your site→