Common Prompting Pitfalls and How to Avoid Them
Learn the most frequent mistakes beginners make when writing prompts and the simple fixes that turn vague requests into reliable results.
Common Prompting Pitfalls and How to Avoid Them is a free Prompt Engineering & LLM Optimization for Developers lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Prompt Engineering & LLM Optimization for Developers learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Even Good Models Need Good Prompts
Even a capable LLM fails on a fuzzy prompt. Most disappointing results trace back to a few avoidable mistakes - here they are, each with a fix.
Pitfall: Being Too Vague
"Write something about marketing" gives the model no anchor. Always specify the topic, audience, length, and format, as the good example shows.
Bad: Write something about marketing.
Good: Write a 150-word intro for small business owners
explaining email marketing basics, friendly tone.Pitfall: Asking Many Things at Once
Cramming five unrelated asks into one prompt yields shallow answers to each. Break the work into focused steps or separate prompts.
Pitfall: No Output Format
If you need structured output, say so. Without guidance the model invents its own format, which is painful to parse - spell out the schema, like below.
Return the answer as a JSON array of
{ name, price } objects, no extra text.Pitfall: Negative-Only Instructions
Telling the model only what not to do leaves a vacuum. Pair each prohibition with a positive instruction, as the better example shows.
Weak: Do not be too technical.
Better: Explain it as you would to a 10-year-old,
avoiding technical jargon.Pitfall: Ambiguous Pronouns
Words like "it" or "that" confuse the model when context is long. Restate the actual subject explicitly so there's no ambiguity.
Pitfall: Ignoring Examples
When you want a specific style, show an example instead of describing it. One demonstration usually beats a paragraph of rules, as below.
Example output:
- Title: Crisp and benefit-driven
- Body: Two short sentences
Now write three more in that style.Pitfall: Overstuffing Context
Dumping huge irrelevant text dilutes attention and burns tokens. Include only what the task needs, and put the key instruction near the end.
Pitfall: Trusting Without Verifying
LLMs state wrong facts confidently. For anything factual, ask for reasoning or sources - and verify critical claims yourself.
Pitfall: Not Iterating
The first prompt is rarely the best. Treat prompting as a loop: read the output, spot what's off, and refine one variable at a time.
A Quick Checklist
A quick checklist: Is the task specific? Did I state audience, length, and format? Did I show an example? Is context trimmed? Will I verify the facts?
Quick Check
Test your understanding of prompting pitfalls.
Recap
Recap: weak results come from vagueness, multitasking prompts, missing formats, negative-only instructions, and not iterating. Be specific, show examples, trim, verify, refine.
Frequently asked questions
Is the “Common Prompting Pitfalls and How to Avoid Them” lesson free?
Yes — the full text of “Common Prompting Pitfalls and How to Avoid Them” is free to read here on the web, and the Prompt Engineering & LLM Optimization for Developers course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Prompt Engineering & LLM Optimization for Developers course, upgrade to CoddyKit PRO.
What will I learn in “Common Prompting Pitfalls and How to Avoid Them”?
Learn the most frequent mistakes beginners make when writing prompts and the simple fixes that turn vague requests into reliable results. You practise Prompt Engineering & LLM Optimization for Developers with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Prompt Engineering & LLM Optimization for Developers?
No prior experience is required. Prompt Engineering & LLM Optimization for Developers on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Common Prompting Pitfalls and How to Avoid Them” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Prompt Engineering & LLM Optimization for Developers lesson?
Yes. Every Prompt Engineering & LLM Optimization for Developers lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Introduction to LLMs & Prompting
- Basic Prompt Structures
- Zero-shot & Few-shot Prompting
- Common Prompting Pitfalls and How to Avoid Them