Wrap-up
You shipped an AI-built career website on Google Cloud. In about three hours you went from a blank project to a public URL — using the same toolchain professional teams ship with.
Pulse check — what stuck?
Ten random questions drawn from a pool covering the theory block. Answer each one before submitting — pulling something from memory beats re-reading it, every time. Three minutes here will outlast the rest of the recap.
What you built
- A complete site spec — produced by a 10-minute Gemini Gem interview, with regional research baked into the Gem so its output is two production-ready prompts: one for Stitch (design) and one for Antigravity (build).
- A visual design generated and refined in Stitch from that design prompt.
- A working career site coded agentically in Antigravity, including a
persona.jsondata file and the Stitch design as a copy-paste reference the agent matched against. - A live deployment on Cloud Run, sitting behind a public HTTPS URL.
- A real, professional development workflow: spec-first prompting, agent-driven scaffolding, small commits, iterative prompts.
Next steps — the honest version
What you have right now is a blueprint, not a portfolio. The site is real, the URL works, the pipeline is reusable. But four hours of demo can't replace the months of practice that produce something exceptional. The version that actually gets you hired is the one you build at home, deliberately, after today.
The moves that turn this workshop into a career, in priority order:
- Rebuild it from scratch this week. Use today's site as a reference, not the destination. Re-run the Gem with sharper answers about your real target market. Redesign in Stitch with intent. Ask Antigravity for a more specific scaffold. Polish the copy until you'd send it to your top three target companies. The blueprint is reusable; the polish is yours alone — and that's the part recruiters actually evaluate.
- Run the same loop on something real this week. A bug at work, a side-project feature, a small refactor. Today taught you a method; the only way it sticks is by using it on something where the cost of failure is yours.
- Add the URL to LinkedIn, GitHub, and your CV — once it's worth sharing. A draft you'd hesitate to send is worse than no link. The polished version goes in the bio. Don't ship the demo.
- Join the AI-native Discord. Free, ongoing, full of people who just shipped what you shipped. Drop your URL when it's ready, ask questions when you hit a roadblock, share what you build next. The cheapest way to keep momentum after today.
- Explore the resources page. Curated links to Google products, frameworks, and codelabs that go further than what we covered today.
Keep going with codelabs
Right now is the highest-leverage moment to learn more — your Google Cloud project is configured, credits are live, and you have momentum. Google publishes free, hands-on tutorials called codelabs that fit cleanly into a focused hour. Three to consider next:
- Getting Started with Google Antigravity — deepen your fluency with the IDE you used today.
- Getting Started with Google MCP Servers — extend a coding agent with custom tools your
persona.jsoncan serve. - Building AI Agents with ADK: The Foundation — the natural next step from a chatbot to a real agent.
The full curated list with commentary lives on the resources page.
Five minutes of feedback
Before you close the tab — fill in the workshop feedback form. Five minutes, mostly tap-to-answer, one short text field. Honest answers (especially the "what didn't work" and "one thing you'd change" parts) directly shape the next run of this workshop.
What happens next
Most of what you saw today will fade unless you re-touch it. The same study spread across a week beats the same study done all at once, by a wide margin — spacing wins almost every time.
Three short retrieval prompts, scheduled across the next month. Each one takes under a minute. The point isn't to look anything up — it's to try to remember, even badly. Trying counts.
+ 24 hours — tomorrow, same time as the workshop
Without scrolling: what's the difference between a billing account and a project, and which one do credits live on? Peek at step 1 only after you've tried.
+ 7 days — one week out
Sketch the build-brief prompt shape from step 4 §6 on paper, from memory, in 60 seconds. If you can reproduce it — its inputs (the design reference, the brief), outputs (named files, a launch checklist), scope (the section list), constraints (plain HTML/CSS), and verification (refresh localhost) — the pattern is yours.
+ 30 days — one month out
Did you ship a second site using the Gem → Stitch → Antigravity → Cloud Run pipeline? If yes, the workshop landed. If no — what's stopping you? (The honest answer is usually "I haven't tried" — fixing that is one evening.)
The cheapest way to actually do this: open the email below in your client and use scheduled-send for tomorrow morning, +7 days, and +30 days. Three drafts, three minutes.
Open three retrieval drafts in my email
Resources
Glossary
Short definitions for every term used in the workshop.
Resources
Google products, frameworks, slides, and further reading.
About the trainer
Who ran today's workshop and how to stay in touch.
What you saw today doesn't make you the top 5% of engineers. Four hours can't replace months of practice. What it does do is show you the toolchain — Antigravity, Gemini, Stitch, Cloud Run — and the workflow most working developers in this market still haven't touched. That's a real advantage, but only if you actually use it.
Run an agent on something real every week — even something small. Stay current — pick one channel (YouTube, newsletter, podcast) and check it weekly. Build in public — post the repos, write what worked. The market in 2026 is brutal; the engineers who do the reps are the ones still working in 2027.
If you don't keep going, today was wasted time. If you do, you'll be in the 5% that actually shipped — which is what gets you hired.
If you haven't yet — drop your deployed URL into the workshop channel and click on a couple of your neighbours' sites. Today's pipeline produces about thirty live URLs in this room; that's its own small graduating class.