A language model does what you ask, not what you meant. Prompt engineering is the skill of closing that gap: writing requests with enough context, limits and detail that the model gives you something you can use.
Why vague prompts give generic results
A model like the ones behind ChatGPT or Claude writes its answer by predicting likely text, one piece at a time, from your request plus what it learnt in training. When your request leaves a decision open, the model still has to make it. It fills the gap with whatever is most typical, or with a confident guess.
Ask for 'a website' and every choice is open: the purpose, the pages, the colours, the framework, the copy. The model picks something for each one, and the result is a website. It just isn't yours. Nothing in the request said it should sell tuna, so it doesn't.
The model usually won't stop to ask, either. Chat models are tuned to answer straight away, so a vague request gets a fast, finished-looking reply rather than a list of questions. That is what makes vague prompts costly: the output looks complete, so the gaps are easy to miss. The model isn't a mind reader, and it won't tell you which parts it guessed.
The parts of a good prompt
The video named four things a good prompt adds. Each one removes a different kind of guessing.
Context
Context is what the model can't know unless you say it: who the work is for, what already exists, and why you want it. 'The site is for a freelance illustrator who wants more commissions' changes the copy, the layout and what goes at the top of the page. For code, it is the code you already have and the exact error you're seeing.
Constraints
Constraints narrow the range of acceptable answers: a dark theme, React, three sections, under 200 words, no extra libraries. Each one is a decision you've made so the model doesn't have to. Constraints are also how you rule out what has gone wrong before, such as 'no gradients' or 'keep the function's signature as it is'.
Examples
An example shows the model what good looks like faster than a description can. If you want commit messages in a particular style, paste two you like. If you want data pulled out of text into a fixed shape, show one input and the output you expect. Putting a few worked examples in the prompt is often called few-shot prompting, and the model follows their pattern.
Wondering how this was made? How we make these