Vibe Coding at 50

Your Prompt Is the Product

·
Advice

When I started, my prompts looked like this:

"Make it look nicer."

"Add a dashboard."

"Fix the login."

And I would sit back like a king who had spoken, waiting for magic. What I got back was almost always disappointing, and I blamed the AI. It took me an embarrassingly long time to realize the AI wasn't the problem. My prompts were the problem.

In vibe coding, the prompt is not a request. The prompt is the product. The clearer your prompt, the closer what you get back will be to what you actually wanted. A vague prompt is a vague app.

Here's the same three prompts, rewritten after I got better:

"Update the header so the logo is on the left, three nav links (Home, About, Contact) are on the right, and the whole thing has a thin bottom border. Keep the current colors."

"Add a dashboard page at /dashboard that shows the logged-in user's name at the top, a list of their most recent five orders in a table, and a big button that links to the order creation page."

"The login page accepts my email but rejects my password even though I know it's right. Check the auth flow and tell me where it's failing before you change anything."

See the difference? The second version of each is boring. It's specific. It's a little bit longer. It leaves way less room for the AI to guess. And it gets me what I actually wanted about 80% of the time instead of 20%.

Three rules I follow now:

  1. Describe the thing, not the vibe. "Make it feel more premium" is a vibe. "Increase spacing, use a serif for the headline, drop the drop shadow" describes the thing. The AI can build the thing. It cannot build the vibe.

  2. Say what shouldn't change. More than half of my early frustration was the AI helpfully changing things I liked while fixing the thing I didn't. Now I say "keep the existing color scheme" or "don't touch the footer." Boring. Effective.

  3. Ask before you tell, when you're unsure. If I don't know what I want, I don't pretend I do. I ask: "What are three ways we could structure the settings page?" The AI is genuinely great at this and it stops me from asking for something I'll regret.

The biggest shift, honestly, is treating prompting like writing. You wouldn't send a business email that just said "make it better." You'd write what you meant. Prompts are the same. They're just business emails to a very fast, very literal, occasionally overconfident colleague.

One trick that changed everything for me: I dictate prompts into my phone now, in full sentences, like I'm explaining what I want to a smart friend who wasn't in the room for the last conversation. Then I paste that in. The AI does dramatically better with a full paragraph of context than with a two-word command.

What I'd tell someone in my shoes: stop trying to be efficient. Long, specific, boring prompts get you where you're trying to go faster than short, vague ones. Every minute you spend writing a better prompt saves you an hour of undoing a bad one.