#vibe-coding
21 articles
When the Doom Loop Hits
Something that worked yesterday stopped working. You try to fix it. It gets worse. You try harder. It gets worse. This is the doom loop. Here is how to escape it.
Your First Screen
The first prompt that turns text into a working thing you can see in a browser. One screen. Fifteen minutes. A moment you will remember.
Knowing When to Stop
Finished-and-ugly beats half-done-and-pretty. The hardest skill in vibe coding is recognising when v1 is done, and putting the rest on the v2 list.
The Constraints Interview
Your idea is not limited by what you can imagine. It is limited by what you can finish. Find the real shape of what is possible.
Cut Half of It
Your brief is too big. You do not see it yet. This lesson is the one where Claude plays the adversary and argues the case for a smaller, braver version of your project.
The One-Paragraph Brief
One paragraph that explains what you are building, to a friend, in plain language. No jargon, no hedging, no features list. The paragraph is the project.
The Three Buckets
Before you build anything, figure out which kind of thing you are actually making. There are three. The one you say yes to changes everything.
Does It Look Good?
The eighty-twenty of design for people who did not train as designers. Four rules that will make almost any vibe-coded thing look considered, without needing to learn typography from scratch.
The Phone Check
Open your site on your actual phone. Most things will be fine. The few things that break are the difference between shipping and shipping proudly.
Real Content Beats Lorem Ipsum
Placeholder text is the last thing hiding the gap between a real site and a draft. Write the real words. The design will tell you whether it works.
From Brief to CLAUDE.md
Your brief is one paragraph. Your CLAUDE.md is the whole project's memory. This lesson turns the first into the second.
One Sentence, One Screen, One Flow
Before you build anything, describe v1 in the smallest possible shape. One sentence. One screen. One flow. Anything bigger is not v1.
Put It Online with Vercel
Your project is on your laptop. One command puts it on a server anyone in the world can reach. Here is exactly how.
The Final Touch
Your site is live on your domain. Now the last details that make it feel like a real thing — favicon, share preview, and the one test that matters.
Name It and Buy the Domain
The first step of going live: pick a name, buy a domain, and avoid the three traps that catch everyone on their first try.
Point Your Domain at Your Site
The moment the URL becomes yours. Two paths — a simple one and a magic one where Claude Code handles the DNS for you.
Start Here: The Vibe Coding Path
New to vibe coding? This is your roadmap — every article in the code track, in the order that makes the most sense. Start at the top, work your way down.
The Vibe Coder's Survival Guide: What to Do When It Breaks
AI builds the first 80% brilliantly. Then something breaks and you don't know why. Here's the non-developer's guide to debugging, recovering, and knowing when to ask for help.
The Vibe Coder's Guide to the Galaxy
Every technical term you'll stumble across while vibe coding, explained in plain language with zero condescension. Don't panic — just bookmark this.
What Happens After You Build It: Maintaining Your Vibe-Coded Projects
You built a site. It works. Now what? How to update it, fix things that break, keep it secure, and know when you need a human developer.
What Is Vibe Coding (And Why It Works)
You describe the vibe. The AI writes the code. It sounds like cheating. It is not. It is a new way of making things — and it is changing who gets to build.