Section 1 was about the thing you are talking to. Section 2 is about the room you are both standing in. Every AI coding tool works by reading and writing files in folders on a computer, running commands in a terminal, and leaving a trail you can inspect afterwards. If those three things are vague, every later lesson has to stop and explain the room before it can make its point.

Two of the six sections here are the ones worth your attention if you read nothing else. Version control is what makes an assistant's mistakes reversible, and reading a diff is how you find out what it actually did rather than what it said it did.

  1. Files, folders and paths. The filesystem is what every tool actually operates on, and most "it cannot find the file" errors are path errors.
  2. The editor and the terminal. What each window is for, how to open the second one, and the four commands worth learning first.
  3. Version control, plainly. Commits as save points, and how to get back to one.
  4. Reading a diff. The verification skill that still works when the change is 300 lines long.
  5. Running it on your own machine. Dependencies, install, the dev server, and the five errors everyone hits.
  6. GitHub and what it is for. A second copy, a browsable history, and the place your deploys pull from.