.png){kind=small}
Prompt Foundations Checkpoint: Rewrite a Bad Prompt
Take a failing prompt from your history and rebuild it using specificity, role, format, example.
What You Will Learn
- Identify a failing prompt from your own history.
- Apply specificity, role, format, and example to rebuild it.
- Document before/after with results.
- Build a personal prompt-quality checklist.
- Reflect on which technique helped most.
Why This Matters
Reading about prompting is passive. Rewriting a prompt you actually struggled with is active practice that cements the techniques.
Concept Explained
Take a real prompt from your history that produced bad output. Decompose why it failed. Rebuild it using techniques from BE-15 through BE-21. Document before/after.
How It Works
Find the bad prompt in your conversation history. Identify the failure mode. Apply fixes: specificity, role, format, example, context. Run both prompts and compare.
Step-by-Step Tutorial
1. Find a bad prompt
Open your Gemini conversation history. Find a prompt that produced disappointing output.2. Diagnose
Why did it fail? Vague, wrong role, no example, wrong format, wrong context?3. Rebuild
Apply the relevant fix.4. Compare
Run both prompts. Compare output quality.5. Document
Write a 3-sentence summary: original prompt, fix applied, result improvement.Real-World Example
A developer's prompt fix this evolved to: Act as senior TS engineer. Fix the TypeError when input is null. Don't use try/catch. Use Result type. Output as unified diff. Quality improved from generic to a clean diff.
Example Prompts / Commands / Code
BEFORE:
"fix this bug"
AFTER:
"Act as a senior TypeScript engineer. Fix the TypeError when
input is null. Don't use try/catch. Use Result type. Output
as unified diff.
Example fix pattern:
Before: function f(x) { return x.y; }
After: function f(x) { if (!x) throw new Error('x required'); return x.y; }"
Common Mistakes
- Picking a prompt that was actually fine.
- Applying all techniques at once.
- Not running both prompts to compare.
Best Practices
- Pick a real prompt you struggled with.
- Apply one technique at a time.
- Run both prompts and compare.
- Document the before/after.
- Build a personal prompt checklist.
Troubleshooting
| Problem | How to Fix |
|---|---|
| Can't find a bad prompt | Try fix this or add tests from a week ago. |
| Improved prompt still bad | The task may need Pro model or a different surface. |
Practical Exercise
Your Turn
This IS the exercise. Find, diagnose, rebuild, document. Save the before/after.
Professional Challenge
Build a 5-item personal prompt checklist. Use it on your next 5 prompts.
Key Takeaways
- Rewriting a real bad prompt cements techniques.
- Diagnose before rebuilding.
- Apply one technique at a time.
- Run both prompts.
- Build a personal prompt checklist.
Frequently Asked Questions
Should I save these before/afters?
What if my prompt was actually OK?
Further Reading
Official References
Related lessons: BE-15, BE-16, BE-19
SEO Metadata
SEO title: Prompt Foundations Checkpoint: Rewrite a Bad Prompt
Meta description: Take a failing prompt from your history and rebuild it using specificity, role, format, example.
Primary keyword: gemini prompt rewrite
Secondary keywords: gemini bad prompt, gemini prompt improvement, gemini prompt checkpoint, gemini prompt optimization
Search intent: Informational
URL slug: /gemini-prompt-foundations-checkpoint
Categories: AI Tools, Google Gemini
Tags: Gemini, Beginner, Checkpoint, Prompting, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN Gemini lesson card for Prompt Foundations Checkpoint: Rewrite a Bad Prompt
Comments
Comments
Post a Comment