ABCsteps lesson path
AI-Assisted Code: Your First App
Use an AI coding assistant to build a small game while learning what the tool is doing, where it helps, and where human judgment still matters. Build one artifact, keep one review trail, and make the work easy to inspect later.
- Lesson
- 01
- Time
- 45 min
- Access
- public lesson
Learning objective
Understand the difference between asking AI for code and verifying a working application.
Lab outcome
Build and inspect a simple browser game.
Module milestone
Publish a small working app and its GitHub repository.
Lesson proof workflow
Read, build, then review the evidence.
- Step 1ReadStart with AI-assisted coding before touching tools.
- Step 2BuildBuild toward: Build and inspect a simple browser game.
- Step 3ReviewReview the evidence using Browser debugging.
Toolchain
AI-assisted coding starts with verification, not blind trust.
These are the practical surfaces used in this lesson. Learn the habit first, then connect it to the wider engineering ecosystem.
Use assistance as a draft generator, then inspect the result.
Read files, change code, and run the app from a real workspace.
Understand the language behind the first interactive project.
Proof of work
Leave one inspectable trail from this lesson.
The useful output is not a passive note. It is a small artifact another person can inspect: a working file, a command result, a commit, a screenshot, a README note, or a demo link.
Lesson lab: Build and inspect a simple browser game.
Tool and platform logos are ecosystem references only: no affiliation, endorsement, interview access, hiring promise, salary promise, or placement guarantee.
Build
Produce the artifact
Complete the lab and keep the result visible: Build and inspect a simple browser game.
Record
Save review evidence
Capture what changed, what broke, and how AI-assisted coding became clearer through the work.
Explain
Write the vocabulary
Use your own words for Human verification and Browser debugging; this is what makes the lesson inspectable later.
Skills companies recognize
Translate the lesson into inspectable work language.
This lesson turns one small lab into the language a learner can use in a README, demo note, or technical conversation. The point is not to collect logos; the point is to explain work clearly enough that another engineer can inspect it.
Where this skill appears
Product teams value AI-assisted speed only when the learner can verify the result.
Ecosystem references
Platform and company logos are ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
README line
Name the artifact
Lab proof: Build and inspect a simple browser game. Connect it to AI-assisted coding so the result reads like work, not a passive note.
Review line
Explain the stack
Use GitHub Copilot, VS Code, JavaScript to explain Human verification and what changed between the first attempt and the inspected result.
Conversation line
Answer with evidence
If a team asks about Browser debugging, use this proof line: Show the prompt, the generated change, the bug you found, and the final working browser demo.
Proof translation
Skill signal
AI-assisted coding is the market word. The lesson makes it visible through a small working artifact.
Proof artifact
The inspectable artifact is: Build and inspect a simple browser game.
Interview answer
Use Human verification and Browser debugging to explain what changed, what failed, and how you verified it.
Paid guidance
Read publicly. Upgrade when guidance will help you finish.
This lesson remains part of the public written syllabus. Paid help is online-only and human-led: video walkthroughs as they roll out, live class context, WhatsApp Q&A, and project review around the same work.
No account wall, automated checkout, or placement promise is introduced here. Enrollment stays human-led by WhatsApp or call, and the useful proof remains the learner's own artifact.
Public
Written lesson stays open
Read the prepare and review material for lesson 01 on the public site before buying anything.
Recorded
Recorded and live guidance clarify the work
Paid guidance can add founder-led video walkthroughs as they roll out and live online class context; the teaching explains the work, but does not replace the written lesson.
Human
Questions use real context
When stuck, useful guidance starts from the route, error, screenshot, repo fragment, and the lab artifact: Build and inspect a simple browser game.
Phase 1 · Briefing
Lesson briefing
Before You Study (5 mins)
Lesson focus: Modern AI coding tools can help you build a working application from a plain-language description. This lesson is the first one because it removes a single false belief that has stopped millions of capable people from learning to build software: "I can't code." You can. By the end of today, you will have a working browser game that you built by talking to an AI — and you will know what just happened.
What you should have ready:
- A computer with internet (Windows, macOS, or Linux all work)
- A Google account (Antigravity uses Google sign-in)
- A modern browser (Chrome, Edge, Firefox, or Safari)
- About 60 minutes — this is the longest lesson in Module A
- Patience to read what the AI generated, not just to run it
The Concept
Every app you have ever used — Instagram, WhatsApp, your bank's website, your Uber app, this very page you are reading — is code. Code is a set of written instructions that a computer follows. Different categories of code do different things: some draws what you see on screen (frontend), some stores and retrieves data (backend), some talks to other apps over the internet (APIs). All of it is just text in files, written in a specific programming language.
For most of computing's history, writing code was a manual craft. A developer would type each line by hand, debugging by reading the lines back to themselves, occasionally googling for help. The skills required to start — knowing where to type, what file to put it in, what command to run — were a wall that kept beginners out.
In 2023–2025, AI coding assistants crossed a threshold. They became good enough at understanding plain-language descriptions ("build me a snake game that runs in the browser") and generating working code that runs. They are not magic. Under the hood, they are large language models — like ChatGPT or Gemini — that have been trained on billions of lines of public code. When you describe what you want, the model predicts the code that has historically followed similar descriptions. The result is usually correct enough to run, often correct enough to ship, and almost never correct enough to deploy without reading.
The skill we are practicing today is AI-assisted code that you understand. The wrong way to use these tools is to type a description, watch the code appear, and ship it without reading. That produces fragile software the user cannot debug. The right way is what this entire course teaches: describe, read what was produced, modify, run, verify. The AI handles the boilerplate; you handle the architecture, the choices, and the verification.
Today's tool is Antigravity, Google's free AI coding platform. It runs in the browser, has a built-in AI agent that can write code for you, and gives you a real development environment for free. You will use it to build a working browser-based game in about 30 minutes of guided work.
The course will use AI assistance throughout — Antigravity in early lessons, command-line tools (Gemini CLI, Claude Code) in later ones. The principle stays the same: the AI is a pair, not an author. You stay responsible for what runs.
Quick Concepts
| Term | Simple Meaning |
|---|---|
| Code | Written instructions a computer follows, line by line |
| App | Any program you use — Instagram, a calculator, a game |
| AI Agent | An AI that can plan multi-step tasks, not just answer one question |
| IDE | The window where developers write code (Word, but for software) |
npm run dev | A command that starts a local development server on your computer |
What We Will Build
By the end of this lesson, you will have done these specific things:
- Signed in to Antigravity with your Google account at antigravity.google.com.
- Started a new project and asked the AI agent to build a Snake game in the browser using HTML, CSS, and JavaScript.
- Read every file the AI generated. There will be three or four —
index.html,style.css,game.js, possibly apackage.json. You will not understand every line yet; that's fine. You will know which file does which job. - Run the game with
npm run dev(or the equivalent button in Antigravity) and load it in a browser preview pane. - Played the game to confirm it works.
- Made one small change yourself — change a color, change the speed, change the snake's starting size — and verified the game still works.
The point of step 6 is the most important one. The first time you change someone else's code (the AI's, in this case) and it still runs, the wall between "user of software" and "person who builds software" comes down.
Think About
Before studying, consider:
- The last app that surprised you with how useful it was — what would it take to build a worse version of it yourself? (Probably less than you think.)
- If AI can write the boilerplate code for you, what becomes the valuable skill? (Hint: it is not typing speed.)
By the End
After this lesson, you'll:
- ✅ Have Antigravity installed and running with your Google account
- ✅ Understand that code is just instructions, written in text files
- ✅ Have built and played your first working application
- ✅ Have made your first deliberate code change
- ✅ Know what an IDE, an AI agent, and a development server are
Ready? Let's reveal the first secret. 🚀
Next lesson · 02
Set Up VS Code Like a Developer
Set up a professional editor, understand project files, and use AI assistance to modify an existing app deliberately.