S-Tier Prompt Writing

Welcome to the part of the course where we fix what breaks.

You'll write a good prompt and still get a bad answer sometimes. It happens. These next four lessons are the four most common ways an answer goes wrong, and the exact fix for each. First up, the most common one of all.

You ask a simple question. You get back a wall.

Three paragraphs where one sentence would have done it. It restates your question before answering. It adds caveats you didn't ask for. It explains things you already know. Then it wraps up with a little summary of what it just said. The actual answer you wanted is in there, somewhere, buried under a pile of words like a key dropped in tall grass.

This is rambling, and it's the number one thing you'll need to fix. So let's fix it.

It rambles because it thinks length is a favor

Here's what's going on in there.

The AI has it in its head that more is more helpful. That a longer answer is a better answer. That if it leaves anything out, it's failing you. So it pads. It covers every angle, repeats itself to be safe, and wraps the one useful sentence in three paragraphs of insulation.

It's the same instinct from a few lessons back: the AI is allergic to empty space. Give it room and it fills it, whether or not there's anything worth putting there.

But length isn't a favor. It's a tax. Every extra word is a word you have to read to get to the point. A long answer doesn't feel generous when you're the one digging through it. It feels like work.

The fix: put it on a budget

The single most powerful thing you can do is give it a limit.

That's it. That's the whole fix, most of the time. A word budget forces the AI to do the one thing it won't do on its own: choose. It can't fit everything into fifty words, so it has to decide what actually matters and cut the rest. You've made it prioritize, just by closing the door on padding.

"But won't I lose something?"

This is the worry that stops people from setting limits. If I cap it at two sentences, won't it leave out something I needed?

Almost never. Here's why.

Cutting the length doesn't cut the answer. It cuts the padding. The restated question, the throat-clearing intro, the caveats, the recap, the third example you didn't need. Those are the first things to go, because they were never load-bearing. What's left is the part you actually came for, now standing on its own where you can finally see it.

And if it really did trim something you wanted? You're in a conversation. You just say "add the part about X." You lose nothing by starting tight and asking for more. You lose time by starting bloated and digging for less.

Two more ways to squeeze it

A budget does most of the work. Two more moves for the rest.

Make it lead with the answer. Sometimes you don't even mind the length, you just hate hunting for the point. So move the point to the front.

Now even if it goes long, the thing you needed is the first thing you read.

Name the fluff out loud. The AI has a few signature padding moves, and you can ban them by name.

And if it already rambled, cut it in half

Maybe you didn't set a limit and now you're staring at the wall. Easy. Don't rewrite anything. Just say:

Then, if it's still too long:

Each pass keeps the meaning and sheds the fat. Two or three rounds and you'll have squeezed a paragraph down to the one line that was hiding inside it the whole time.