Basic

When prompts fail

Most prompts fail for a small, fixable reason. Change one thing, re-run, and see what moves the answer.

About 1 min of reading

Data Flow

A failing prompt is diagnosed, one change is applied, and the result is compared before deciding.
1 Read the output and spot the gap
↓
2 Add one missing detail
↓
3 Re-run and compare
↓
4 Save the version that works
Why this works
The common failures
ProblemFix
Too vagueAdd topic and details
Wrong formatAdd an example
Too longAsk for brevity
Off-topicRestate the goal

Every failure points to a missing instruction.

Keep a list of what you tried so you can repeat what works.

Building a prompt library

Save the prompts that work:

prompt + result = learnable prompt
Keep the best version, label it, reuse it.

Over time you build a library of prompts you trust. That is how teams stay consistent.

Examples

Diagnosing a bad prompt

Bad: "Tell me about it."
  -> too vague. What is "it"?

Better: "Tell me about the return policy."

If an answer is wrong, the prompt is usually missing a detail. Add one thing and test again.

Why it works: most failures are fixable with one more sentence.

One change at a time

Change one word, re-run, compare.
If it gets worse, you learned something.

Changing everything at once makes it impossible to know what helped.

Small changes, one at a time, are how you learn.

Add the missing piece

It is broken.         -> broken what?
The printer will not
  connect to Wi-Fi.   -> now I can help.

Most failures come from one missing detail. Find it and add it.

Why it works: the model already knows the answer; it just needs the question.

Words this lesson uses

Each one is defined here on this site. Open the entry for the full definition and the other words it points at.

← Few-shot examples
Previous Lesson
Few-shot examples
Next Lesson
Prompt structure & delimiters
Prompt structure & delimiters →