Vibecoding · Tooling & stack
Tooling & stack
Which tools to build in and which tech stack to build on — the two choices that make or break a build.
Topics & techniques
Choosing tools & stack
Pick the right AI environment and a boring, popular stack the model actually knows.
4 cards →Comparison
Choose Your Vibecoding Tool: Cursor, Claude Code, Lovable, v0, Bolt, Replit
A practical guide to the main environments people vibecode in, and which fits which job. They fall into two broad camps: AI code editors and agents that work inside a real codebase (Cursor, Claude Code), and build-an-app platforms that generate and host a whole app from prompts (Lovable, v0, Bolt, Replit).
Best practice
Pick a Boring, Popular Stack
A deliberate choice to build on the most common, well-documented frameworks, languages, and databases — the 'boring' mainstream ones — rather than the newest or most niche. It's one of the highest-leverage decisions in a vibecoding project, and you make it in the first prompt.
Knowledge card
Use an AI IDE, Not Just a Chat Window
The choice to vibecode in an environment where the AI is connected to your actual files, a live preview, and your version history — an AI code editor or agent — rather than pasting code back and forth with a standalone chatbot.
Workflow
Wire Up the Tools the AI Needs: Git, Preview, Tests
The small setup that turns vibecoding from risky to safe: version control so every step is a checkpoint, a live preview so you can see what the AI built, and at least a few tests so changes that break things announce themselves. You do this once at the start and it protects the whole project.