This repository is the practical workspace for a Google Antigravity workshop. It uses TripLens, a small post-trip travel insights app, as the demo application.
The product is intentionally simple: trips, spending categories, charts, forms, comparisons, mock API routes, local persistence, and focused tests. The point is not to teach travel finance. The point is to give attendees a realistic app surface where agentic development habits are visible.
The workshop teaches a practical AI-assisted development loop:
Context -> Plan -> Execute -> Inspect -> Verify -> AutomateYou will see how the same app behaves when an agent has weak context, better project rules, planning discipline, review support, runtime evidence from MCP, and finally automation with guardrails.
- Live attendees who need a clear path through the workshop without reading every file.
- Self-paced learners who want to reproduce the workshop after the event.
- Facilitators who need a stable public repo entrypoint while keeping deeper trainer notes private.
Install prerequisites:
- Git
- Node.js LTS with
npm - Google Antigravity CLI
- A modern browser for the local TripLens URL printed by
npm run dev
Install Antigravity CLI:
# macOS or Linux
curl -fsSL https://antigravity.google/cli/install.sh | bash# Windows PowerShell
irm https://antigravity.google/cli/install.ps1 | iexOpen a new terminal after installation and confirm:
agy --versionClone the workshop repo and run TripLens:
git clone https://github.com/asadkhalid305/antigravity-workshop.git
cd antigravity-workshop
npm install
npm run devOpen the local URL printed by the dev server. It will usually look like
http://localhost:<port>. Replace <port> with the port shown in your
terminal, for example http://localhost:8000.
Useful checks:
npm run lint
npm run buildFor broader local verification, this repo also has:
npm run typecheck
npm run test
npm run verifyOfficial Antigravity links:
- Following the workshop live or self-paced: open docs/workshop/guide.md.
- Exploring Antigravity CLI commands: open docs/workshop/cli-command-showcase.md.
- Checking what each branch is for: open docs/workshop/branch-flow.md.
The README gives the high-level map. The workshop guide gives the step-by-step commands, branch context, and prompts.
The branches are prepared exercise states, not normal product release history. Generated changes during the workshop are disposable; switch to the next checkpoint branch when the next concept begins.
| Branch | Learning Goal |
|---|---|
main |
Complete app and public documentation entrypoint |
00-unprepared-agent |
See how broad tasks behave when the agent has minimal project context |
01-agent-context |
Add project rules, workflows, and skills so the agent has shared operating context |
02-plan-before-editing |
Practice planning before edits and reduce scope before implementation |
03-inspect-and-verify |
Use a PR-review plugin and focused verification to inspect agent output |
04-external-context-mcp |
Use MCP for external context, especially live browser/runtime evidence |
05-automation-and-hooks |
Turn bounded repeatable work into scheduled automation with hook guardrails |
06-command-showcase |
Explore useful Antigravity CLI commands after the core workflow |
Switch branches with:
git switch 01-agent-contextReplace the branch name with the active exercise.
- Do not paste secrets, tokens, private company code, or private customer data into prompts.
- Inspect plans, diffs, tool requests, and verification output before approving important work.
- Treat checkpoint branches as recovery points. If an exercise goes off track, switch to the next prepared branch.
- Use dangerous auto-approval modes only as controlled demos, not as a normal development habit.
- If your output differs from another group, that is part of the workshop. The goal is to learn how context and verification change the workflow.