Before you write a single prompt, you need the right mental models. This module sets the foundation for everything we build this week.
Slide 2 / 12
Vibe coding is a development approach where you describe what you want in plain language and let AI generate the code. You guide direction and intent rather than writing syntax.
You don't need to understand every line. You need to understand the problem, the user, and the outcome you want.
Think of it as being the architect, not the bricklayer. You design the building; AI lays the bricks.
Slide 3 / 12
Everyone is crossing lanes. That's the whole point of vibe coding.
Meme Break
Vibe coding requires three fundamental mindset shifts. This is where most people get stuck.
Your job is no longer writing syntax. It is articulating intent clearly and precisely. The better you describe, the better the output.
Stop thinking of AI as autocomplete. Think of it as a junior developer who is fast, tireless, and eager to please but needs clear direction.
Your industry knowledge IS your advantage. A marketer who knows their audience can now build tools a developer never would have thought of.
Slide 4 / 12
Why this approach is a game-changer for builders, founders, and creators.
Build prototypes 10x faster than traditional development. What used to take weeks now takes hours. Compress your timeline from months to days.
Non-coders can build. If you can describe what you want clearly, you can create functional software. The barrier to entry has never been lower.
Change direction instantly. Pivot your entire approach with a new prompt. No refactoring, no sprint planning. Just describe the new direction.
No dev team needed for your first prototype. Validate your idea before spending money on engineers. Build the proof-of-concept yourself, then hire to scale.
Slide 5 / 12
Vibe coding is powerful in the right context. Here is your decision framework.
Slide 7 / 12
More than you think. Here are real-world examples ranked by complexity.
Marketing sites, product pages, event registrations
Contact forms, feedback surveys, intake questionnaires
Lead-gen quizzes, personality tests, assessment tools
Personal sites, project showcases, creative galleries
Analytics views, KPI trackers, reporting interfaces
Admin panels, team dashboards, workflow managers
Contact management, pipeline tracking, client portals
Subscription tools, booking systems, micro-products
Slide 8 / 12
A Product Requirements Document turns your rough idea into a structured brief. That brief becomes your first prompt.
AI is only as good as your instructions. A vague prompt produces vague output. A structured brief gives AI the constraints it needs to generate something useful.
Your PRD doesn't need to be long. It needs to be specific: Who is the user? What problem do they have? What does the solution look like? What are the constraints?
The PRD becomes the skeleton of your first prompt. Everything flows from this document.
Weak prompt
Strategic prompt
Slide 9 / 12
Every great prompt follows this structure. Memorise it. Use it every time.
Who should AI pretend to be? A frontend dev, a copywriter, a data analyst.
Background on your business, your users, and the situation.
The specific thing you want built or created. Be precise.
Guardrails: tech stack, file count, performance, style rules.
What the output should look like: a file, JSON, bullet points, a table.
Slide 10 / 12
Four tools. That's all you need to go from idea to deployed product this week.
Google's AI model. Your coding collaborator that generates, explains, and debugs code.
Google's browser-based IDE. The playground where you paste prompts and watch code appear.
Version control and collaboration. Store your code, track changes, deploy with Pages.
Google's backend platform. Database, authentication, and hosting all in one place.
Slide 11 / 12
Before the break, we are going to vibe code something real. Follow along on your screen.
Craft a 3-question quiz prompt using the formula we just learned.
Open Google AI Studio and paste your structured prompt.
See the AI write a complete, working quiz in real time.
Push to GitHub Pages and share a live URL with the room.
Slide 12 / 12
15 minutes
Stretch. Grab a coffee. Check your setup.
When we come back: your first real build.
Slide 12 / 12