Chapter 2 · Be specific#

The big idea#

Specific means the answer can be right or wrong. “Make it better” cannot be wrong, so it is never useful. “Cut it to two sentences and keep the price” can be checked. Replace every vague word (good, short, nice, professional, some) with something you could measure or point at.

Everyday example: Ordering at a restaurant: “something to eat” gets you whatever is easiest for the kitchen. “A medium cheese pizza, no olives, thin crust” gets dinner. The waiter is not smarter in the second case; you were more specific.

In plain words

Before sending, underline every adjective in your prompt. Replace each with a number, an example or a named audience.

A picture#

Be specific A vague ask gets a generic answer; a specific ask gets a usable one. Be specific Before Tell me about Python After Explain Python lists to a beginner in under 120 words, with one example Topic + audience + length + example Same model, same question. Only the prompt changed.
A vague ask gets a generic answer; a specific ask gets a usable one.

Before and after#

Replies below are typical examples to show the difference. Your model will word things differently, so run the prompts yourself.

Example 1 · Summaries#

Before

Summarise this article.

Typical reply

The article discusses several aspects of remote work, including its advantages and disadvantages, and concludes that the future of work will likely involve a balance. It touches on productivity, culture and technology... (a loose paragraph)

After

Summarise the article below in exactly 3 bullet points for a busy manager. Each bullet must start with a verb and be under 20 words.

Typical reply

- Compare remote and office output before changing policy.
- Budget for tools that keep teams talking across time zones.
- Pilot a two-days-in-office plan for one quarter, then review.

Prompt checker (code/promptcheck.py, columns T C A F L E D):

before   1/7  [Y . . . . . .]  missing: context, audience, format, limits, example, delimiters
after    5/7  [Y Y Y Y Y . .]  missing: example, delimiters

Why it works. “Summarise” has no length, no reader and no shape. Three bullets, a manager and a word limit turn a vague digest into something you can paste straight into a briefing.

Example 2 · Feedback#

Before

Make my code better.

Typical reply

Your code is good but could be improved. Consider adding comments, using better variable names, handling edge cases and following PEP 8. (nothing you can act on)

After

Review this Python function for readability. Give me at most 3 changes, each as a one-line reason followed by the corrected line. Do not change what the function returns.

Typical reply

1. Rename `x` to `prices`: the name says what the list holds.
   `def total(prices):`
2. Use `sum` instead of a loop: shorter and clearer.
   `return sum(prices)`
3. Add a type hint so callers know the input.
   `def total(prices: list[float]) -> float:`

Prompt checker (code/promptcheck.py, columns T C A F L E D):

before   0/7  [. . . . . . .]  missing: task, context, audience, format, limits, example, delimiters
after    3/7  [Y Y . . Y . .]  missing: audience, format, example, delimiters

Why it works. “Better” could mean faster, shorter, safer or prettier. Naming the goal (readability), the number of changes (3), the shape and the constraint (same return value) leaves one clear job.

A quick swap table#

Vague

Specific

short

under 80 words

professional tone

formal, no slang, no exclamation marks

some ideas

exactly 5 ideas

for beginners

for someone who knows variables but not functions

make it better

fix grammar only, keep my wording

recent

published in the last 12 months

Rules of thumb#

  • Use numbers where you can: counts, word limits, dates.

  • Name the reader: “a nervous first-time buyer” beats “the user”.

  • Say what must not change, not only what should.

Common mistakes#

  • Using adjectives as instructions (“engaging”, “punchy”) with no example of what you mean.

  • Asking for “a few” or “some” and then being unhappy with the number.

  • Stuffing in detail that does not matter. Specific is about the relevant details, not more details.

Try it yourself#

  1. Make this specific: “Write a good product description.”

  2. Replace the vague words in: “Give me some quick tips to learn faster.”

  3. Why is “under 100 words” better than “short”?

Answers

  1. For example: “Write a product description for a steel water bottle for hikers. 60 words, 2 short paragraphs, mention it keeps drinks cold for 24 hours, no exclamation marks.”

  2. “Give me 5 study tips for a student preparing for a maths exam in two weeks. One sentence each, each tip doable in 10 minutes.”

  3. You can count it, the model can follow it and you can check it. “Short” means different things to different people.

Next

Specific wording helps, but the model also needs the facts of your situation. Next: give context.