So far, Claude Code worked for the course. Now it works for you: you build a small website of your own, in a folder of its own. After this part, you can use Claude Code for any project of yours, and the course stays clean.
9. Know where Claude Code may work
Quiz. In the course, you start Claude Code with ./kingo claude. In which of your folders can Claude Code create
and change files?
- In every folder on your laptop that you can write to
- In all of
~/kingo-pod - Only in
~/kingo-pod/claude, your course folder
Show the answer
Only in ~/kingo-pod/claude. Claude Code may read all of kingo-pod, but it can write only in the course folder.
The sandbox decides that, not the model: so a mistake of the model cannot change the rest of your laptop. In any
setup: before you start a project, know where Claude Code may write.
The course folder is for the course: there Claude Code reaches n8n, Langflow and your database, and it reads your team’s rules. For anything else, for example your thesis or a small tool for yourself, Claude Code gets a folder of its own. You do that in the next step.
~/kingo-pod/claudeyour course folderreads and writesno access~/kingo-podthe rest of kingo-podreads onlyreads only its helpers~/projects/my-first-projecta folder of your own (step 10)no accessreads and writes~your other foldersno accessno access/mnt/cWindows: your drive C:no accessno access
./kingo claude: Claude Code writes only in your course folder. It reads the rest of kingo-pod, and nothing else of yours.
./kingo claude --in ~/projects/my-first-project: Claude Code writes only in that folder. Of kingo-pod, it reads only its own helpers, in ~/kingo-pod/setup/claude.
Done: you know where Claude Code may write, with each way to start it.
Next time. When you start Claude Code in a new setup, find out first where it may write.
10. Give each project a folder of its own
Make a new folder and start Claude Code there:
-
Make the folder. Is Claude Code still running in your terminal? Type
/exitfirst. Then paste this line into your terminal:mkdir -p ~/projects/my-first-projectmkdirmakes a folder: heremy-first-project, inside a folderprojectsin your home folder (~). With-p, it also makesprojectswhen that folder is not there yet. Check it: this line lists your new folder.ls ~/projects -
Go into your kingo-pod folder, where the command
./kingois. Paste this line into your terminal:cd ~/kingo-pod -
Start Claude Code in the sandbox, as before, but in your new folder:
./kingo claude --in ~/projects/my-first-project
Claude Code writes only in ~/projects/my-first-project. It does not see n8n, Langflow or your database there, and
it does not read your team’s rules. Its notes (step 7) are then in that folder, in memory-of-ai/.
To see what Claude Code writes there, open the folder in a second terminal tab (how). On a Mac, paste this line:
open ~/projects/my-first-project
On Windows, paste this line:
cd ~/projects/my-first-project && explorer.exe .
Or click through the File Explorer: Linux in the left column, then Ubuntu, home, your name, projects.
Pin the folder projects, as in step 2: right-click it and choose Pin to Quick access.
Your turn: build your own website. A one-page website about this homework, with a little animation: for example, the nine habits, one card each, that come in one after the other. On the way, you use the habits.
-
Plan first (step 3). In Claude Code, paste:
I want a one-page website about the habits of my current homework, with a little animation. I have not thought it through yet. Interview me until you could write a plan, then write the plan to plan.md. Do not build anything yet.Answer its questions: you decide who the page is for, what it shows, and how it moves. When Claude Code asks what the habits are, copy them from Your habits on one page, at the end of Part E.
-
Start fresh, then build, with a finish line (steps 7 and 4). Type:
/clearThen paste:
Build what plan.md says, as one file index.html. You are done when index.html opens in a browser and shows everything that plan.md asks for. Look at the page before you say that you are done. -
Open your page. On a Mac, paste this line into your second terminal tab:
open ~/projects/my-first-project/index.htmlOn Windows, double-click
index.htmlin the folder that you opened above. -
One step at a time (step 5). Ask for one change, look at the page, then ask for the next improvement, for example: “Let each card come in from the left when I scroll to it.” Does Claude Code go in circles? Press Esc (step 6).
-
Let it remember (step 2). Do you tell Claude Code the same thing in every session, for example which colours your page has? Ask it: “Write this into AGENTS.md, as a rule for this project.” At every start, Claude Code reads that file, and other coding agents do too.
Done: you planned and built a website with Claude Code. Show it to your team.
Quiz. You started Claude Code in ~/projects/my-first-project. Next week you want to continue. What do you type?
cd ~/kingo-pod && ./kingo claudecd ~/projects/my-first-project && claudecd ~/kingo-pod && ./kingo claude --in ~/projects/my-first-project
Show the answer
With --in and the folder. Without --in, Claude Code starts in the course folder. A plain claude does not go
through kingo: no sandbox, no keys, no way to OpenRouter. To pick up last week’s conversation too, type /resume
in Claude Code. A shorter way to start comes in Part E.
From kingo-pod: ./kingo claude help, its lines on --in and on ./kingo shortcuts.
Next: Part E · Shorter commands →
If something goes wrong
Find your step.
Step 10
| What you see | What to do |
|---|---|
| kingo says the folder is not inside your home folder | Use a folder under ~, as in the box. Not a Windows folder (/mnt/c/...). |
index.html opens in a text editor, not in your browser | Right-click it, choose Open with, and pick your browser. |