When Should You Fix the Prompt?

Take a breath — this chapter is written to be read like a conversation, not a textbook, so it's easy to follow.

Let's Think About It for a Second

Think of a prompt as medicine — don't take it for every fever. Vague wording, no audience, no format, no example — those get fixed by a better prompt. Want the exact date from a school handbook? Pretty wording alone won't get you there — that's RAG. Need it to save a file or send an email? That's an agent. Ask it to write code and never read it, and vibe coding breaks down. Take the wrong medicine and your stomach hurts.

Connect It to Everyday Life

What a good prompt is good at: summarizing, pulling out examples, generating practice questions, changing tone, producing a checklist. What not to trust it for: "this prompt will get 2026 news right," "this prompt will know my grade from memory." In your first week, save only 5 prompts. Don't chase framework names, token counts, or jailbreaks yet — that's like dumping in chili because the soup needs more salt.

Vague wording → rewrite the prompt
Needs your notes → use RAG
Needs a tool or action → use an agent

Let's Try It Together

text

Fuzzy wording     → rewrite the prompt
Needs your notes  → use RAG, then a prompt
Needs a tool      → use an agent
Needs working app → write or vibe-code it

You should see

You can tell which of prompt / RAG / agent a problem actually needs.

Try It in 5 Minutes

Think of 5 wrong answers you've gotten. For each, decide: rewrite the prompt, RAG, agent, or code.

A Quick Heads-Up

A longer prompt isn't automatically more correct. Sometimes it's just more confused.