BACK HOME
    FREE GUIDE

    Vibe coding
    without the chaos

    Four practices I use on every build — from scoping a PRD to shipping a production-ready tool. Written for non-technical operators.

    THE PROBLEM

    Vibe coding is more than just vibes

    Most non-technical people open a vibe coding platform, type a vague prompt, and get something that kind of works. Then it breaks on the second iteration. Then the design looks generic. Then they give up.

    The difference between builders who ship real tools and builders who stall out isn't coding skill — it's having a small set of practices before you ever type a prompt. Here are the four I use on every build.

    01

    Build your vibe coding team

    Why it matters: You wouldn't start a company with one tool. Don't start a build with one either. I use four — each with a clear job.

    How to do it

    Claude

    Thought partner. I use it for PRD drafts, MVP scoping, hackathon strategy, and debugging when Lovable gets stuck.

    Dribbble

    Design inspiration. I browse before every build to find a visual direction worth stealing.

    Chrome

    Dedicated workspace. Separate profile, bookmarks, and tabs per project. Lets me preview work without publishing.

    Lovable or Claude Code

    Where the actual building happens. I stay in Lovable AI Chat 95% of the time.

    02

    Always start with a PRD

    Why it matters: A PRD (Product Requirements Document) is a one-page spec of what you're building and why. It takes 15 minutes to write and saves you hours of debugging the wrong thing.

    How to do it — the 8 PRD components

    1. 1Vision / Problem statement
    2. 2Target users (ICP)
    3. 3User flows / Core flow
    4. 4Data inputs / Outputs
    5. 5Core MVP features
    6. 6Technical architecture
    7. 7Design system
    8. 8MVP success criteria

    Skip the blank page

    I built a PRD template you can copy, paste, and fill out in 15 minutes. It's the exact prompt I use for every build.

    03

    Use a design system

    Why it matters: Without a design system, every new feature you add looks like it came from a different app. With one, everything clicks — and your tool starts to look like a real product.

    How to do it

    Consistency across builds

    Every new feature matches your existing style.

    Faster iterations

    Say "use our design system" instead of "make it look better".

    Professional results

    It looks intentional, not auto-generated.

    Brand recognition

    Your tools look like YOUR tools, not everyone else's.

    Three design systems worth studying: Neo Brutalism (Gumroad), Liquid Glass (Apple), Material Design (Google). I also have a full design systems webinar in Resources.

    04

    Use a simple product roadmap

    Why it matters: Every build accumulates a wishlist. A roadmap forces you to ship the important stuff first instead of the fun stuff.

    How to do it

    • A simple spreadsheet is enough — it doesn't need to be Linear or Jira.

    • Works for anything: hackathons, side projects, real products.

    • Prioritize based on 3 things:

      1. 1Scale of impact
      2. 2Urgency
      3. 3Ease of implementation