How to write a prompt an AI coding tool can actually use
4 min read
The single biggest gap between people who get remarkable things out of AI coding tools and people who come away frustrated has almost nothing to do with technical skill. It has to do with how they brief the tool.
The instinct to fight is treating the AI like a search box, where you type three keywords and hope. It isn't a search box. It's a fast, literal, slightly over-eager contractor who will do exactly what you ask, including the parts you didn't mean. Your job is to brief it well.
Specificity is most of the game
"Make me a website" will get you a website. It will be the bland average of every website, because you gave it nothing to aim at. "Make me a one-page site for my dog-walking business, friendly in tone, with my three service packages listed and a button to email me" gives it a target, and the result lands far closer to what was in your head.
The detail you'd give a person you'd hired is roughly the detail the AI wants. Imagine a designer you brought in for the afternoon. You wouldn't say "make a logo." You'd say what the business does, who it's for, the feeling you want, and a few examples of styles you like. Use that same shape with the AI.
Context is the other half
The more the AI knows about your situation, the better it performs, and the easy error is assuming it knows things it can't. It hasn't seen your other files unless you've pointed it at them. It doesn't know your preferences until you state them. It can't read the half-formed idea in your head.
Tell it what a new collaborator would need on their first day. Why you're building this. Who it's for. What matters to you. What you've already tried.
And because AI coding tools can see your files, showing beats describing. If you have an example, a document, an old version of the thing, point the AI at it and say "make it more like this." A concrete example carries more information than any description, the same way handing a contractor a photo beats describing the kitchen you have in mind.
The shape of a good first prompt
Three pieces, in order. What it is. What you want it to do. What good looks like. That's the whole template.
"I'm a freelance interior designer in Austin. I want a one-page personal site with a short intro, a gallery section, my three services, and a contact button that opens an email to me. Keep the style warm and minimal."
Notice what's in there. The role. The target. The structure. The feel. None of it is technical. All of it is the kind of thing you'd say to a person hired to do the work. That is the whole craft.
When it gets it wrong
It will. The good news is that correcting it in plain language costs far less than restarting. "Move the contact button up to the top." "The green is too dark, lighten it." "Don't add a navigation bar, this is one page." Round by round, the generic first draft turns into the thing in your head, and you didn't have to learn a new language to make it happen. That correction-and-refinement is the loop every tool runs on.
This is the skill. Not technical knowledge. Communication. You probably already have most of it, from briefing designers, talking to contractors, or onboarding new hires. You're using it on a machine now. The machine is faster.
The steps, in order
Brief an AI coding tool the way you would brief a designer or contractor: role, context, target, and feel.
State who you are and what you're building
Open the prompt with your role and the goal of the project.
List the specific features
Name each feature the result should include, in order, as a clear list inside the sentence.
Describe the feel or style
Say what tone, color palette, or mood the result should hit.
Point at examples
If you have an existing file, image, or document that resembles the target, point the AI at it and ask it to match.
Review and correct in plain language
Read each diff, say plainly what's wrong, and let the AI iterate.
Iterate until it's right
Repeat the cycle until the result matches what was in your head, then save a checkpoint.
Frequently asked questions
What's the best prompt for an AI coding tool?
The same shape a designer brief takes: role, target, structure, feel. Specifying who you are, what you want built, the features it should include, and the tone or style. Specificity beats clever phrasing every time.
Why does my AI coding tool keep making mistakes?
Usually because the prompt assumed context the AI couldn't see. Tell it what you've already tried, point it at your files, and describe the goal the way you would for a new collaborator on their first day.
Should I tell the AI my level of experience?
Yes, especially if you want simpler explanations. Saying "I'm not a developer; keep explanations plain" adjusts how it talks back. Stating your level of expertise is a small prompt move with a big payoff in clarity.