Reads your codebase
It sees every file, understands the structure, and knows what already exists before writing anything new.
Vibe coding. Live build.
You don't need to be a developer to build a website. Today you'll learn to guide an AI agent that writes the code for you, then deploy it live.
Claude Code is an agent that lives in your terminal, reads your entire codebase, writes code, and runs commands, all while you stay in control. Think of it like pair programming with a very fast junior developer. You guide, it executes.
It sees every file, understands the structure, and knows what already exists before writing anything new.
Creates files, edits existing ones, builds components. From a single function to an entire page.
Installs dependencies, starts dev servers, runs builds, deploys. Anything you'd type in a terminal.
$ claude
Welcome back. What can I help you with?
> Create a hero section with a gradient background and a tagline
I'll create a hero section. Let me...
Write src/components/Hero.astro
Edit src/pages/index.astro
[Accept] [Reject] No syntax to learn. Describe what you want and Claude figures out how to build it.
Before changing anything, Claude shows you exactly which files it will create or edit. You approve or reject every change.
A file in your project that tells Claude about your codebase, your preferences, and how you want things done. The more context, the better the output.
Vibe coding isn't about writing code. It's about communicating clearly with an AI that writes code for you. Here's how to do it well.
Vague prompts like "make it look nice" produce a mess. Specific prompts like "add a hero section with a dark gradient background, white heading text, and a blue CTA button" produce a result.
Don't try to build everything in one prompt. Start with structure, then add styling, then polish. Small steps mean better results.
Don't just accept blindly. Scan the changes. You'll catch mistakes early and learn how the code works as you go.
If Claude starts going in circles or the output gets weird, start a fresh conversation. A clean context window fixes most problems.
Every time something works, commit it. Git commits are your save points. If things break, you can always go back.
We're going to build a personal website from scratch using Astro and MDX, deploy it live to the internet, all in under an hour.
When you hit "deploy", your code takes a journey through three stops. Understanding this pipeline is the difference between magic and confusion.
You write code (or Claude does). Files live in a folder on your machine. You preview at localhost:4321.
Your code gets stored in a repository: a shared folder in the cloud. Every change is tracked. You can always go back.
Cloudflare sees the new code, builds your site, and puts it on servers worldwide. Anyone with the URL can see it.
You only touch step one. Push your code and the rest happens automatically. That's the magic of continuous deployment. Every push becomes a live update.
Now I'll open the terminal and we'll build this from scratch, live. Watch how I talk to Claude Code, what prompts I use, and how I iterate when things don't come out right the first time.
~/my-site $ claude
Welcome back. What can I help you with?
> Let's build a personal website...
▊ We run hands-on workshops that get your team building with AI in a single session.