Vibe Coding: Describe it. Build it. Ship it.
A 90-minute hands-on session where students with no coding background plan, prompt, build, and ship a personal website, a browser game, and a blog post using Antigravity, Git, and GitHub Pages.
Context
A 90-minute, hands-on workshop for students who had never shipped a line of code. The goal was not to teach programming. It was to get everyone from a blank folder to a public link in one sitting, and to make them understand what happened along the way.
The deck is built for the lab: every PRD, prompt, and git command is copyable, and the timing for each block is written on the slide. Open the deck full screen and use the arrow keys or the on-screen controls to move through it.
What I covered
0 to 20 min, Understand. Every app is input, process, output. An app works like a restaurant: the frontend is the menu, the API is the waiter, the backend is the kitchen, the database is the store room, and hosting is the building. Then the vocabulary of git and GitHub, and a plain-language explanation of how a language model is made, why it is confidently wrong, and how to pick one.
20 to 25 min, Setup. Sign in to Google and GitHub with your own accounts. Open Antigravity. Create a project folder.
25 to 45 min, Build 1: a personal website. Ask four questions before you build. Turn the answers into a one-page PRD. Use the prompt formula of context, intent, constraints, iterate. Build it, add a .gitignore, push it, and deploy it on GitHub Pages.
45 to 58 min, Build 2: a game. One screen, one rule, one way to win. A game PRD, a game prompt, and a fix prompt for when something breaks.
58 to 63 min, Branch and merge. Why main stays working while the game lands on a branch, and what each git command does.
63 to 72 min, Blog. A prompt that writes the post only from the student’s own notes, with real prompts in code blocks. Merged through a branch with no help this time.
72 to 82 min, Review. Test like a stranger, then a review prompt that lists problems first and fixes one item per prompt.
82 to 90 min, Keep learning and sign out. Where to learn the tech and the tools next, and how to clear every credential from a shared lab computer.
Takeaways
- A clear PRD is most of the prompt. Fill the blanks, then paste it in.
- One change per prompt. Test. Repeat.
- The model sounds right whether it is or not. Run the code and check the facts.
- Branches keep main working. The merge happens in the pull request, not on your machine.
- You just ran the software development lifecycle: plan, build, test, ship.