The anatomy of a good prompt, and three myths to flatline

A good prompt is not a secret phrase, choom. It is just a clear request with the right pieces bolted on: a goal, some context, the output format you want, a few constraints, and maybe an example. Stack those five parts and you will pull far better answers than any clever wording. No netrunner mystique required.

The nice thing is none of this is technical. If you can write a clear note to a sharp choom on your crew, you can write a good prompt. Let us crack the rig open.

What are the five parts of a good prompt?

Think of a prompt as a small stack of chrome. Each layer adds clarity.

1. The goal

Say what you want in one plain sentence. “Summarise this report for my manager in five bullet points.” That is the spine of the whole rig. Go vague here and no amount of chrome later will save it, choom.

2. The context

This is the part people skip, and it is the most important. Paste the actual report. Include the messy notes, the email thread, the audience, the deadline. The model cannot jack into your wetware, so the more real material you hand it, the better the answer. Starve it of context and it flatlines.

3. The output format

Tell it the shape: a table, three bullets, a short paragraph, a 280-character post. If you do not say, you get the default and then burn a turn, and eddies, reshaping it.

4. The constraints

These are your guardrails, your ICE. “Keep it under 100 words.” “No jargon.” “British spelling.” “Friendly but not gushing.” Constraints are how you steer the tone and length without a back-and-forth, choom.

5. An example or two

If you have a sample you like, show it. One or two examples teach the model your style faster than any description, faster than any ripperdoc could chrome it in. This is the single biggest quality jump for tricky requests.

Which three myths should you flatline?

A few habits hang around from the early days, choom. Time to delta them.

Myth one: longer prompts are better. Length is not the goal, clarity is. A tight five-line prompt with real context flatlines a rambling page of instructions. Padding just buries the signal, a gonk move.

Myth two: there is one perfect prompt. There is not, choom. Good results come from a first attempt plus a quick refine. Treating prompting as a one-shot puzzle sets you up to be frustrated. I unpack that mindset in prompting is editing, not incantation, choom.

Myth three: you have to sound technical. You do not need keywords, role-play, or fake authority. Plain language works. In fact, the old “you are a world-class expert” routine adds almost nothing on capable models, pure netrunner cosplay, which I covered in stop role-playing your prompts.

Put it together

Next time you open a chatbot, write your goal, paste the real context, name the format you want, add a couple of constraints, and drop in an example if you have one. That is the whole anatomy, choom. No incantations, no costume, no netrunner mystique, just a clear request the model can actually act on. Preem.