Remember your first week with ChatGPT? You probably typed something like "help me with my business" and got a generic essay about entrepreneurship. Completely useless.

Fast forward to now, and you can get ChatGPT to write specific emails, create detailed strategies, and solve actual problems. The tool didn't get better - you learned how to talk to it.

I recently chatted to a student who was struggling with Lovable the same way. Three hours of "make it look more professional" and "fix the design issues." Each time, Lovable made changes. Just not the ones he actually wanted.

The problem wasn't Lovable. It was the same communication mistakes we all made with ChatGPT in the early days.

Just like you learned to wrangle ChatGPT with better prompts, examples, and specific requests, you need to learn the language that gets results from Lovable. The difference is that instead of getting better text, you get better software.

Most people treat AI development tools like search engines - throw in vague requests and hope for the best. But Lovable isn't Google. It's your tech co-founder. And cofounders need clear briefs, not wishful thinking.

Let’s get started

Your First Lovable Prompt

Before we dive into communication best practices, let's get you actually building. First, use this prompt in ChatGPT (or wherever you’ve been doing your prep work) to create your Lovable starter prompt:

You are helping me create a clear, specific prompt to start building my MVP in Lovable.

My validated business idea: [Insert your Week 3 idea and target audience]

My main user problem: [What specific problem does this solve?]

Core user action: [What's the one main thing users do in your app?]

Create a simple, specific prompt I can copy-paste into Lovable to start building. The prompt should:
- Focus on just the core functionality that solves the problem
- Skip user accounts, payments, or complex features for now  
- Be specific enough that Lovable knows exactly what to build
- Include a simple, clean design direction

Format it as a prompt I can directly copy into Lovable to get started.

This will give you a custom Lovable starter prompt based on your specific idea. Copy that output and paste it straight into Lovable to begin building.

Two things can happen now

Either Lovable absolutely nails it. Congratulations! Your initial idea was simple and focused enough for Lovable to understand exactly what it needed to do. This is why we did all the preparation work.

OR you'll get something that's 70% right and 30% "not quite what I wanted." This is also completely normal, especially if your idea is more complex.

If this happens, don't panic. Take a moment here. It's easy to get caught up with "it's not working" negativity. I've seen people immediately decide vibe coding is rubbish because it didn't nail their vision instantly. Don’t be that person.

Take a breath and appreciate that any amount of coding was completed using natural language based on an idea from your head. That's pretty magical.

Now let's get it properly working.

Why Vibe Coding Communication Differs

Vibe coding is about communication. But it’s subtly different to communicating with ChatGPT.

Here's the fundamental difference: ChatGPT gives you information. Vibe coding tools give you functioning software.

With ChatGPT, vague questions work fine. "Tell me about marketing strategies" gets you a helpful overview. You can get better results by being specific, but you'll be in the right ballpark even with a weak prompt.

Vibe coding is different because we're creating something from nothing. It's a more complex task requiring more complex interaction. Any lack of focus or clarity leads to obviously poor outputs.

Commands like "make my app look professional" give your AI development tool nothing actionable. What does "professional" mean? Clean and minimal? Corporate and formal? Modern and edgy?

Think of it like hiring a developer. You wouldn't say "build me a good website." That’s insufficient. You'd provide wireframes, examples of websites you like and specific requirements. AI development tools need the same clarity.

The more specific you are, the better your results - not because these tools are limited, but because precision eliminates guesswork. Remember that they can’t read our minds (yet!).

The Iteration Conversation

Thankfully, vibe coding tools excel at iterative development. We have a conversation with the tool and work to make our project better and better. Your first request creates the foundation. Subsequent prompts refine and improve. If the tool doesn't nail your build immediately, that's fine - we're going to have a conversation until we’re in a better place.

Good iteration pattern

Ideally you give short, specific tasks for Lovable to work on. For example

1. "Create a content creation form with title, description, and category fields"

2. "Add character count displays for each text field"

3. "Include a preview pane that updates as users type"

4. "Add save draft functionality with auto-save every 30 seconds"

Each step builds on the previous one. You test and check it’s working at each stage before adding complexity.

Bad iteration pattern

1. "Build a complete content management system with everything I need"

This creates overwhelming scope and unclear requirements. This is what most people do. And then are surprised when it doesn’t work!

Effective Communication Strategies

Here are some general best practices when working with a vibe coding tool. Obviously I don’t know the specific issues you are having but these guidelines will help you avoid a lot of issues.

Start with context, then get specific. Begin with your application's purpose: "For my content planning tool targeting small businesses..." Then specify the change you want.

Use progressive detail. Get the big building blocks down first, then focus on details. Don't worry about logos being too small until the core functionality works.

Reference existing elements. "Make the submit button match the styling of the navigation buttons" is clearer than describing style from scratch.

Specify user experience, not just features. Instead of "add a search function," say "add a search bar in the header that filters content as users type, showing results below." Then Lovable can work out the best way to get this done.

You’re reading week 4 from the special ‘10-week AI Summer Camp’ series. Join the conversation here.

Common Mistakes That Waste Hours

On the flipside here are some bad habits to avoid.

Mistake 1: Asking for "improvements" without specifying what needs improving. "Make this better" forces guessing. Try: "Increase the contrast between text and background for better readability." Specificity always wins.

Mistake 2: Mixing multiple requests in one prompt. "Fix the header, add a footer, and improve the colour scheme" creates confusion. Make one change at a time. Make sure it works. Then the next.

Mistake 3: Using emotional language instead of descriptive language. "This looks ugly" doesn't help. It’s tempting, especially when you keep hitting the same problem - but it won’t help you sort the issue. "The buttons are too small and the spacing feels cramped" gives actionable direction.

Mistake 4: Not providing examples when you have a vision. A command like "Make the dashboard similar to Notion's layout" is incredibly helpful because it gives Lovable something to work towards.

Mistake 5: Forgetting to test each change before requesting the next. Build incrementally, test, move on if working. Otherwise you can end up with a stack of errors and not know where the problems started. Very common.

For Non-Techies: Getting Technical Answers

Sometimes Lovable will spit out a whole bunch of technical details. When Lovable suggests "using React with TypeScript and Tailwind CSS," your eyes might glaze over. Fair enough.

It’s tempting to just say “ok yeah sounds good”. But that’s fully abdicating our knowledge to the AI. Instead we can use this as a chance to learn as well. This will make us a better builder moving forward.

Here's how to get answers without feeling stupid

Feel free to use AI outside your vibe coding tool as your technology advisor. Before development, chat with ChatGPT or Claude about your technical options. Hash out strategy there, then return to Lovable with clear instructions.

Always ask "what does this mean for my business?" Instead of purely trying to understand what a technology like TypeScript is, ask things like: "How does this choice affect my ability to add features later?" or "What does this mean for hosting costs?".

A powerful question (always!) is “what are my other options?” You can never ask this too often!

Example workflow

1. Get stuck on user onboarding design

2. Ask ChatGPT: "What are best practices for user sign ups?"

3. Review examples, talk it through with ChatGPT. Ask for different options, ask what they mean for your business. Make a decision. Ask ChatGPT to write up the instructions for Lovable.

4. Return to Lovable with the suggestions from ChatGPT: ie. "Add a 3-step user sign up flow with email verification, profile setup, and tutorial walkthrough following these best practices and these technologies"

What's Next

Tomorrow, we start scaffolding your application's foundation. You'll use today's communication strategies to build the basic structure that solves your core problem.

If you already have a working first version: amazing! If not we’ll work our way up to it.

We're starting simple: core functionality first, polish later. By the end of tomorrow's session, you'll have a working application that demonstrates your solution.

Keep Prompting,

Kyle