N0 BEFORE YOU START · MOONKEY LAB

The tools
of the operator.

Before you build anything, get to know your toolbox. This is Level 0: what you'll use, why it matters and what each thing is for. You don't have to install anything yet — just understand the map.

If you're coming from AI chat on a website, this is the leap: an operator doesn't consume AI, they operate it from their own machine with real access to their files. These eight tools are how.

YOUR TOOLBOX
01

Terminal

WHAT IT IS

The command line: a text screen where you give direct orders to your computer.

WHY

It's the most direct and powerful way to control your machine. No menus, no clicks — text that runs.

WHAT FOR

Navigating folders, installing tools, launching Claude Code and running your work.

02

VS Code

WHAT IT IS

A code editor: the window where you see and edit your project's files.

WHY

If Claude Code is your hands, VS Code is your eyes. It's where you verify what gets built.

WHAT FOR

Reading, editing and reviewing the code and files before signing off on them.

03

Claude Code

WHAT IT IS

The AI operator inside your machine. It's not a web chat: it has access to your files, your git and your terminal.

WHY

It turns AI from a consumer tool into a real working system that builds with you.

WHAT FOR

Building, debugging, refactoring and documenting projects — with you in charge, not the machine on its own.

04

Git

WHAT IT IS

Version control: it saves snapshots (commits) of your project over time.

WHY

It lets you experiment without fear. If something breaks, you go back to an earlier stable point.

WHAT FOR

Versioning your work, reverting mistakes and seeing exactly what changed and when.

05

GitHub

WHAT IT IS

The remote home of your Git repositories: your code saved in the cloud.

WHY

Backup, collaboration and the trigger for automatic deploys. Your work stops living only on your laptop.

WHAT FOR

Saving your work, sharing it and publishing your project with a simple git push.

06

CLAUDE.md

WHAT IT IS

A text file that gives Claude persistent memory of your project.

WHY

Without it, every session starts from scratch. With it, the AI already knows your stack, your rules and your limits.

WHAT FOR

Making Claude work precisely from the very first message, not generically or inventing conventions.

07

Prompts · Arsenal

WHAT IT IS

The instructions you give the AI: the working language between you and the machine.

WHY

A good prompt is the difference between a usable result and a mediocre one. It's trained, not improvised.

WHAT FOR

Asking for work with a role, structure and intent — and getting real deliverables, not vague answers.

08

Deploy · Cloudflare Pages

WHAT IT IS

Publishing your project to a real URL, automatically, every time you do git push.

WHY

A project no one can see doesn't exist. The deploy turns your work into something real and shareable.

WHAT FOR

Turning every change you push, in seconds, into a live website.

HOW THEY FIT

No tool works alone. Together they're a system.

You operate from the Terminal and verify in VS Code. Claude Code builds with the context from your CLAUDE.md and the prompts you give it. Git versions every step, GitHub saves it in the cloud, and the deploy turns it into a real website. Learning to operate AI is learning to move these pieces as one.

Terminal+ Claude Code+ VS Code Git / GitHub CLAUDE.md + prompts deploy
NOW FOR REAL

You now know the map. In Level 1 you install and use each tool for real, step by step, until your environment is up and running and your first project is live.