The working loop & good habits

You’ve gone from nothing to a live site, you understand your assistant, and you know how to get unstuck. This module ties it together: the simple rhythm you’ll repeat forever, and the handful of habits that make building feel sustainable instead of stressful. It’s the last of the core guide.

The loop you’ll repeat forever

Almost all building, for everyone, is the same small circle over and over:

1. Describe what you want next, in plain English.
2. Look at what the assistant did — in the browser, or by reading its summary.
3. Adjust — say what’s not right and ask for the change.
4. Save — every time something works, commit and push (Module 5).

That’s it. Big, impressive projects are just this loop run a few hundred times. You already know how to do every step.

Keep these habits close

Most of the trouble people run into is solved by a few things you already learned:

• When something breaks or confuses you, tell your assistant exactly what you see and ask it to explain and fix. That reflex — and a list of common hiccups — lives in Module 9. Errors are clues, not scoldings.
• When you want it to stay cheap and smooth, stay on Sonnet, keep one task per conversation, and glance at your usage now and then. The full picture is in Module 8.
• When a project gets bigger than one sitting, keep a PLAN.md in the project folder and have Claude work through it and tick items off. Then you can /clear, walk away, and pick up next week by saying “read PLAN.md and continue” — the project remembers itself so your conversation can stay short. More on this in Module 8.

Staying safe

A few simple habits keep you out of trouble:

• Read before you approve. When the assistant asks to run a command or change files, glance at the summary. For your own projects this is almost always fine — the habit is what matters.
• Keep learning repos private until you’re sure there’s nothing personal in them.
• Never paste passwords, card numbers, or secret keys into a project’s files or into a chat, and keep personal info out of your repos. If something needs a secret, ask the assistant for the safe way to handle it — see Module 5 for the .env and .gitignore habit.
• Be a little skeptical of “just paste this” advice from random websites. When in doubt, ask your assistant “is this safe to run, and what does it do?”

Starting your next project

Your first project, about-me, was built one careful step at a time. But now that you’ve done it once, every future project starts with the same little ritual — and it’s worth seeing it on its own, because this is the part you’ll repeat for the rest of your building life. Remember the rule from Module 3: one folder, one project. So a new idea always begins by making it a new folder.

First, open a fresh PowerShell

This is the bit people forget, so let’s be plain about it. PowerShell is the typing window — the dark terminal you met back in Module 2. To open a clean one: click the Start button (bottom-left of your screen), type PowerShell, and press Enter. A window opens with a blinking cursor, waiting for commands.

Why a fresh window from Start, rather than the terminal still sitting inside your last project’s VS Code? Because that old terminal is already inside your previous project’s folder — and reusing it is exactly how people accidentally build a new project inside an old one. Starting from a fresh PowerShell keeps you on clean ground. (And even if it opens somewhere unexpected, the very first command below puts you back where you belong — so you genuinely can’t get this wrong.)

Then, the four moves

PS> cd ~\Projects
PS> mkdir my-new-idea
PS> cd my-new-idea
PS> code .

Each line does one small thing, and the first line is the one that keeps you safe:

• cd ~\Projects — go to your Projects folder. The ~ means “my home folder,” so this always lands you in the same right place, no matter where the terminal happened to start. Run it every single time and you can never end up nested inside another project.
• mkdir my-new-idea — make the new folder for this idea (swap in your own name).
• cd my-new-idea — step inside the folder you just made.
• code . — open this folder in VS Code (the dot means “this folder”).

VS Code opens a fresh window with your new, empty project loaded — the file explorer on the left should look clean and empty, just like it did for about-me. From there it’s the rhythm you already know: open the built-in terminal (Terminal → New Terminal), which starts inside your new folder automatically, launch Claude with claude, describe what you want, and you’re back in the loop.

Where to go next

You have the whole loop now. To grow from here:

• Build something you actually want. Motivation beats curriculum every time. A tip jar page, a tracker for a hobby, a tiny tool for a friend.
• Ask the assistant to teach as it builds. “Explain each step like I’m new.” You’ll absorb a surprising amount just by reading along.
• Revisit the glossary and cheat sheet whenever a word or command slips your mind. That’s what they’re for.
• Curious about building little tools for yourself? There’s an optional Module 11 on pointing these same skills at small helpers that do chores on your own computer. Totally optional — for whenever you feel like it.

That’s the core guide — head to what’s next for a few good ways to keep going. (Or, if you’re curious, try the optional bonus module on building little tools first.)