How to Talk to AI Tools
You don't need to be a developer to get great results from AI coding tools. You just need to learn how to communicate clearly.
Think of it like giving instructions to a very eager, very literal assistant:
If you say "make the button blue," they'll make it blue. But they won't know which button, what shade of blue, or what happens when someone clicks it — unless you tell them.
The Difference Between a Bad Prompt and a Good One
Bad Prompt
make me a login page
This is too vague. The AI has to guess:
- What language or platform is this for?
- What should the login page look like?
- What happens after someone logs in?
- What if they enter the wrong password?
- Should there be a "forgot password" option?
The result will be generic and probably not what you wanted.
Good Prompt
Create a login page for my task management app.
What it should have:
- Email field and password field
- A "Log In" button
- A "Forgot Password?" link
- A "Create Account" link for new users
What should happen:
- After successful login, go to the dashboard
- If the email or password is wrong, show: "Invalid email or password"
- If someone tries to log in 5 times with wrong info, lock them out for 1 minute
Design:
- Clean and simple
- The app is called "TaskFlow" — show the name at the top
- Mobile-friendly (works on phones)
See the difference? The AI knows exactly what to build.
5 Simple Rules for Better Prompts
Rule 1: Be Specific About What You Want
| Vague | Specific |
|---|---|
| "Add a contact form" | "Add a contact form with name, email, subject, and message fields. After submission, send an email to hello@mycompany.com and show a 'Thanks for reaching out!' message." |
| "Make a dashboard" | "Make a dashboard that shows: total users this month, revenue this month, and a list of recent orders. Each metric should be in its own card." |
| "Add user accounts" | "Add user accounts with email/password login. Users should be able to sign up, log in, and reset their password. Only logged-in users can access the dashboard." |
Rule 2: Tell the AI About Your App
AI tools work better when they understand context. Before asking for a feature, give a quick summary:
Context about my app:
- It's a booking system for a small hair salon
- Customers can see available time slots and book appointments
- The salon owner can manage appointments and see their schedule
- Built with [platform you're using, e.g., React, Bubble, Webflow]
Rule 3: Describe What Should Happen When Things Go Wrong
This is one of the most important rules. AI tools tend to assume everything works perfectly. Tell them what to do when it doesn't:
Error handling:
- If the database is down, show "Something went wrong. Please try again."
- If a user enters an invalid email, show "Please enter a valid email address."
- If a payment fails, show "Payment failed. Please check your card details."
- Never show technical error messages to users
Rule 4: Break Big Requests Into Small Ones
Instead of asking for everything at once:
"Build me a complete e-commerce site"
Break it into pieces:
"Create a product listing page that shows products in a grid"
"Add a shopping cart that shows selected items and total price"
"Create a checkout page with name, address, and payment fields"
"Add an order confirmation page after successful payment"
Each small piece is easier for the AI to get right, and easier for you to check.
Rule 5: Iterate — Don't Expect Perfection on the First Try
The first result probably won't be perfect. That's normal. Instead of starting over, give feedback:
"That's close! A few changes:
1. Move the search bar to the top of the page
2. Make the product images bigger
3. Change the button color from blue to green
4. Add a 'Sort by price' dropdown"
Prompt Templates You Can Use
For a New Feature
Build [feature name] for my [app type] app.
What it should do:
- [requirement 1]
- [requirement 2]
- [requirement 3]
What should happen when something goes wrong:
- If [problem] → [what to show]
Design notes:
- [design preference]
- [design preference]
For Fixing Something
The [feature name] isn't working right.
Current problem:
[describe what's happening]
What should happen instead:
[describe what you want]
Here's what I've tried:
[optional: what you've already done]
For Adding to Existing Code
Add [new feature] to my existing app.
Context:
- My app is a [app type]
- It already has [existing features]
- Users can already [what they can do]
New feature:
[describe what to add]
Common Mistakes and How to Avoid Them
| Mistake | Why It's a Problem | Better Approach |
|---|---|---|
| Being too vague | AI guesses wrong, you waste time fixing | Write down exactly what you want |
| Forgetting error cases | App breaks silently when things go wrong | Always describe "what if" scenarios |
| Asking for everything at once | AI gets confused, results are messy | Break into small, clear tasks |
| Not providing context | AI builds something that doesn't fit your app | Give a quick summary of your app first |
| Accepting the first result | You miss better solutions | Ask for refinements and improvements |
The Bottom Line
The quality of what AI builds for you is limited by how clearly you describe what you want.
You don't need to know how to code. You just need to know how to communicate. The more specific and detailed you are, the better your results will be.
Level Up Your Prompts With a Spec
The best prompts come from clear specs. Download the AI Project Template to organize your requirements before you start prompting.
Download the Starter Template →