AI Global Academy Join the waitlist

Courses / Basic / Section 0

Level 1 · Basic

Start here: setup and first steps

The student has every tool installed, has had a first working session with Claude Code, and has a project folder under version control.

  • 4lessons
  • 2.5 hof lessons
  • 1.8 hhomework
Start courseSee all lessons

Lessons

  1. 0.1

    What you will build and how the course works

    20 min + 25 home

    The student can describe the final product and the path to it.

    What the lesson covers
    Prerequisites
    None. No coding experience is assumed.
    Covers
    • A tour of the finished project: site, lead form, CRM, analytics dashboards, ad accounts.
    • The map of sections and the milestone after each one.
    • The lesson format, checkpoints (lesson-X.Y tags) and how to catch up from the reference repository.
    • What costs money: domain, ad budget, optional paid plans.
    Do along
    Write down the business or offer the site will be for (one sentence is enough; it is refined in 2.1).
    Done when
    The student has named their project and knows what each section adds to it.
    Homework
    Fill in a cost sheet for the paid items, put study hours in the calendar with a target date for the live site, and note what three websites in the student's own field ask visitors to do.

    Open lesson 0.1 →

  2. 0.2

    Install the toolbox

    45 min + 20 home

    A computer ready for the whole course.

    What the lesson covers
    Prerequisites
    A macOS or Windows computer on which you may install software; a Claude subscription or API billing that includes Claude Code; an email address for new accounts.
    Covers
    • What each tool is for: terminal, Node.js, Git, a code editor, Claude Code.
    • Installing each on macOS and Windows; checking versions.
    • Signing in to Claude Code and which subscription or billing option it uses.
    • Accounts to create now so nothing blocks later: GitHub, Vercel, Supabase, Google.
    Do along
    Install everything and run the version checks listed in the lesson.
    Done when
    node, git and claude each print a version in the terminal, and the student is signed in to Claude Code.
    Homework
    Write a dated setup card from the version checks, put the five accounts in a password manager with a sign-in list, and record which Google account and which Claude plan the project uses.

    Open lesson 0.2 →

  3. 0.3

    Your first session with Claude Code

    40 min + 30 home

    The student has made Claude create and change real files and understands what happened.

    What the lesson covers
    Prerequisites
    Lesson 0.2 — tools installed and Claude Code signed in.
    Covers
    • What Claude Code is: an agent that reads files, runs commands and edits code in a folder.
    • The session loop: you ask, it proposes actions, you approve, it reports.
    • Permission prompts and why to read them.
    • Useful commands: /help, /clear, interrupting, resuming a session.
    Do along
    In an empty folder, ask Claude to build a one-page "about me" HTML file, open it in the browser, then ask for two changes.
    Done when
    The page opens in a browser and reflects both requested changes.
    Homework
    In a separate folder, build a second one-file page from the student's own prompt and change it twice, keep a log of three permission prompts including one refusal, then leave the session and resume it.

    Open lesson 0.3 →

  4. 0.4

    Git and GitHub: your safety net

    45 min + 30 home

    Every later lesson can be undone and saved.

    What the lesson covers
    Prerequisites
    The folder and page from 0.3; the GitHub account from 0.2.
    Covers
    • Why version control matters most when an AI is editing your files.
    • Commit, history, diff, branch, tag — the five ideas needed for this course.
    • Letting Claude write commits; reviewing a diff before accepting it.
    • Pushing to a private GitHub repository; restoring a previous state.
    Do along
    Turn the folder from 0.3 into a repository, commit, break the page on purpose, restore it, push to GitHub, create the tag lesson-0.4.
    Done when
    The repository is visible on GitHub with at least two commits and one tag, and the student has restored a file once.
    Homework
    Repeat the change, review, commit and push rhythm alone on a small wording change (no tag), delete and restore the page once more, and write one line per commit describing the project's history.

    Open lesson 0.4 →