Workflow

The 3-message rule — how to talk to AI without losing control of your project

Sending AI a giant list of changes is the fastest way to break everything. This one rule stops that from ever happening again.


Simple explanation

When you send AI six things to fix at once, four work and two break something — and you have no idea which change caused the problem. The 3-message rule fixes this by keeping every AI session to one ask, one check, and one confirm. When something breaks, you know exactly what caused it. You fix one thing, not six.


What to do

Follow this pattern for every single AI session: Message 1 — One ask Ask AI to do exactly one thing. Not two. Not "and also." One. Example: "Change the button color to black." Message 2 — One check Before you send anything else, look at what it did. Does it look right? Did anything break? Take 30 seconds to check. Message 3 — One confirm If it looks good, say "that looks correct." Then move to the next thing. The rule inside the rule: do a GitHub commit after every change that works. Think of it as pressing Save in a video game — you can always go back to that exact moment. The best non-developer builders are not the fastest. They are the most methodical. Slow is smooth. Smooth is fast.


Copy-paste prompt

[ONE specific task only — e.g. "Change the button color to black."] Please make only this one change. Do not fix, improve, or adjust anything else. Once done, tell me exactly what you changed so I can check it before we move on.


Course note

The 3-message rule is one of the core workflow habits covered in the course. Combined with GitHub commits after every working change, it is the single biggest thing that separates builders who make steady progress from those who keep starting over.

Key takeaway

One ask. One check. One confirm. Every single time.

Start here

Start the free 5-day challenge

Next step

Join the AI course waitlist

Resource

Get the free prompt pack

Was this helpful?