Prompt Engineering
10%
Lesson 1 of 10

Why Prompts Fail

A weak prompt often fails because the instruction is underspecified — not because the model needs a “magic phrase.”

Weak prompt

Write a product description.

Better instruction

Write a 120-word product description for a lightweight trail-running shoe. Audience: recreational runners. Tone: confident, clear, not hype-heavy. End with three bullet-point benefits.

The model needs a job definition

A useful prompt usually defines four things: goal, context, constraints and output. You do not need all four every time, but missing the important ones forces the model to guess.

Goal

What should be accomplished?

Context

What does the model need to know?

Constraints

What limits or rules matter?

Output

What should the result look like?

Try it
Fill in the fields, then build a clearer instruction.

Common mistake: adding decoration instead of information

Calling the model “the world’s best expert” may change tone, but it does not replace missing task information. Add the details that actually constrain the job.

Key takeaway

Before adding more words, ask what information the model is currently forced to guess.

Next lesson

Define the Goal

Continue to the next lesson.

Continue →