Stop Looking for the Magic Words
There's a feeling that if you just find the "perfect" prompt, the AI will hand you exactly what you need in one shot. It won't.
Working with AI is a collaboration, not a vending machine. Think of it like working with a highly talented but extremely literal intern. You don't just say "fix the business" and walk away. You give them the files they need, explain the goal, check their work, and point out the gaps.
The process is circular, not linear:
| Step | What you do | Next... |
|---|---|---|
| 1. ASK | Describe one specific goal you want to achieve. | → Check the result |
| 2. CHECK | Compare what you got to what you actually needed. | → Fix the gaps |
| 3. ADJUST | Say exactly what's wrong. If you know how to fix it, tell it. If you don't, ask it to come up with a plan. | → Back to Step 1 |
| ✅ DONE | When it's what you need. | Stop. |
Context is as important as the prompt. The AI can only work with what's in its context window, or "on the desk," so to speak. If you don't give it the right files, background info, or requirements, it's forced to guess.
The Three Steps
Step 1: Ask (One Goal at a Time)
Give the AI a clear, specific instruction for one goal at a time.
If you've already documented what you're trying to build, start by asking the AI to review all the documentation and formulate a plan. Take a beat — make sure it actually understands the project. Have it ask you questions until you're both satisfied it gets the full picture before it starts building.
Step 2: Check & Leverage the Machine
When the AI gives you a result, don't just assume it works. You don't have to do all the heavy lifting yourself — use the AI to QA its own work.
The "Visual Feedback" Shortcut
If you can't describe why a layout looks wrong, don't try. Take a screenshot, use a pen tool to circle the problem (the "Snipping Tool and MS Paint" move), and paste it back. An arrow to the thing that should change is faster than three paragraphs of text.
The "Second Opinion" Technique
Don't rely on just one intern. If your AI built a complex plan, copy it into a different AI's web interface. Give the second AI your docs and say: "Review this plan. QA and fix any bugs or issues you find. Note anything that stands out as a questionable choice or any 'low-hanging fruit' that might add value without adding too much complexity."
Step 3: Adjust (The "Feedback" Step)
The AI can't read your mind. Be specific. Acknowledge what it got right, then point out exactly what needs to change.
- Bad: "The header doesn't look right."
- Good: "The header structure is great, but the logo text should be larger by 20% and the background needs to be a darker grey."
When the Loop Gets Stuck
The "Brainstorm" Break
Sometimes the AI fixes one thing but breaks another. When that happens, stop asking for code. Step back and use the AI as a consultant instead of a builder. Try a prompt like this:
"Let's step back and think about this for a round or two. No code changes — just brainstorm with me. What is the root issue here? Can you look up the official documentation for the tool we're using and see if we're missing something?"
The "Save Point" Habit
When you hit a milestone, have the AI summarize exactly what was built and which files changed. This is your "Save Game" file. If the chat gets too long and the "desk" gets messy (degrading the context window), start a fresh chat and paste that summary to get back to a known-good state instantly.
Locking in the Wins
The best way to prevent the AI from "un-fixing" something you liked is to document it. Once you make a decision on a layout or a feature, add it to your project docs (BRD or Tech Spec). If the AI drifts later, you can point it back to that "Source of Truth" to anchor the project.
| Symptom | The Fix |
|---|---|
| AI keeps reverting your changes | The context window is full. Start a fresh chat. |
| Each fix creates a new problem | The approach is too complex. Ask: "Is there a simpler way?" |
| AI seems confused | Re-state your goal from scratch. Don't rely on earlier messages. |
| You're on round 10+ | Stop. You're gambling, not building. Re-read your requirements. |
The Actual Rule
AI is a power tool. It can build a house in a fraction of the time, but only if you know what a load-bearing wall looks like. Don't know what one looks like? That's fine, just ask it to help you learn.