Free CourseBuild AI Tools

Module 2 · Where tools live: saving, hosting & staying safe

GitHub in plain English

6 min

Your tools live on your computer — so what happens when your laptop dies? That’s what GitHub is for. Think of it as a fireproof safe: a copy of your work, kept somewhere trusted, with a full history.

What GitHub actually is

GitHub is a free service that stores a copy of your project folder in the cloud — and not just the latest version. It keeps every version, every snapshot Git has ever saved, so you can look back at any point in your tool’s history and even roll all the way back if you ever need to.

Put plainly, GitHub gives you three things:

Backup

Laptop dies, tools survive.

History

Every saved version, kept.

Undo, forever

Snapshots live off your machine too.

What GitHub is not

Two quick myths to clear up. GitHub is not where your tool runs — it’s a safe, not a stage. And it’s not something your customers ever see. It’s a private storage locker for you and Claude. Putting a tool online for others is Vercel’s job, next lesson.

Set it up once

You need a free account, and then Claude does the rest.

  1. Go to github.com and create a free account (an email and a password — that’s it).
  2. That’s the only manual part. From here, you never learn a single GitHub command — you ask Claude in plain English.

Once your account exists, open Claude Code inside any project folder and paste this. Claude handles the technical steps and walks you through anything it needs from you:

Copy this prompt

Create a private GitHub repository for this project and push my work to it. Walk me through any login steps one at a time.
Always private, every time

When Claude asks, or when you set it up on GitHub, make sure the repository is private. Your business tools contain business details — client names, prices, notes. A private repository is visible only to you. Never make a repository holding real business data public. The prompt above asks for private on purpose; keep it that way.

Make it a habit

From now on, end every build session with one line: “snapshot and push to GitHub.”Claude saves a snapshot of your work and sends the latest copy up to your safe. Ten seconds, and your day’s work is protected off your machine.

If you get stuck

GitHub’s login can involve a browser pop-up or a code to paste back — that’s normal, and the prompt tells Claude to walk you through it one step at a time. If a step confuses you, paste exactly what you see back to Claude and ask “what do I do with this?” It’ll tell you.

What success looks like

You have a free GitHub account, this project is backed up in a private repository, and you know the one line that keeps it current: snapshot and push to GitHub. Your work is now safe even if your computer isn’t.

Watch this step

GitHub makes more sense seen than described. This one's from GitHub's own channel — a plain-English tour of repos, history, and backup, the "fireproof safe" idea in this lesson. It’s from an independent creator — credited below, so go give them a follow.

The ultimate beginner's guide to GitHub in 2026

GitHubCurated · third-party

More learning resources

Still want another angle? These are hand-picked and vetted to line up with this lesson — from creators and sites worth your time.