25 copy-ready examples — each showing a weak prompt and its improved version with a change log.
No API key needed to browse · Works with ChatGPT, Claude, Gemini
CodingCode Review
Before — vague prompt
Review my code.
After — improved version
Act as a senior software engineer performing a pull-request review. Review the code below for: (1) correctness — are there bugs or off-by-one errors? (2) performance — any O(n²) loops that could be replaced with a hash map? (3) readability — variable names, function length, comments. For each issue, quote the affected line and suggest the corrected version. Severity: Critical / Major / Minor.
Added expert role (senior engineer doing a PR review)
Enumerated three specific dimensions to check
Required severity tagging so output is actionable
CodingExplain Code
Before — vague prompt
Explain this code to me.
After — improved version
Explain the following Python code to a junior developer who knows basic syntax but has never used async/await. Structure your explanation: (1) what the overall function does in one sentence, (2) walk through each block line-by-line in plain English, (3) explain any Python-specific idioms (e.g. list comprehensions, context managers). Avoid jargon.
Defined the audience (junior dev, knows basic syntax)
Specified the structure so output is predictable
"Avoid jargon" prevents condescending or unhelpful definitions
CodingWrite Unit Tests
Before — vague prompt
Write tests for this function.
After — improved version
Write pytest unit tests for the Python function below. Cover: (1) the happy path with typical inputs, (2) edge cases — empty input, None, and maximum value, (3) at least one test that confirms the correct exception is raised on invalid input. Use descriptive test names (test_returns_sorted_list_for_valid_input). No mocking unless strictly necessary.
Specified the test framework (pytest)
Listed three test categories: happy path, edge cases, exception handling
Provided naming convention to make tests self-documenting
CodingSQL Query
Before — vague prompt
Write a SQL query to get sales data.
After — improved version
Write a PostgreSQL query that: (1) joins the `orders` table with `customers` on customer_id, (2) filters to orders from 2025 where status = 'completed', (3) groups by customer country, (4) returns: country, total_orders (count), total_revenue (sum of order_value), avg_order_value. Order by total_revenue DESC. Include a comment above each major clause.
Specified the database engine (PostgreSQL) — syntax varies
Named the exact tables and join key
Defined every output column so no ambiguity in what "sales data" means
CodingRefactor Code
Before — vague prompt
Refactor this code to be cleaner.
After — improved version
Refactor the following JavaScript code to: (1) replace callback-based async patterns with async/await, (2) extract repeated logic into named helper functions, (3) replace magic numbers with named constants at the top of the file. Do NOT change the external API or function signatures. Return only the refactored code — no explanation unless you changed something non-obvious.
Listed specific refactoring goals rather than vague "cleaner"
"Do NOT change external API" prevents accidental breaking changes
"Return only code" avoids a wall of commentary that buries the result
WritingBlog Post
Before — vague prompt
Write a blog post about remote work.
After — improved version
Write a 700-word blog post for a B2B SaaS audience on the topic: "3 Remote Work Policies That Actually Reduce Burnout." Tone: practical and direct — no fluff. Structure: intro (problem statement, 2 sentences), three sections (one policy each, with a concrete example), conclusion with a single CTA to download a free policy template. Subheadings should be action-oriented (e.g. "Set a Hard No-Meeting Day, Not a Soft Preference").
Specified word count, audience, and tone
Required a concrete example per section so content is useful, not vague
Made subheadings action-oriented — a formula, not a guess
WritingEmail
Before — vague prompt
Write a follow-up email after a sales call.
After — improved version
Write a post-sales-call follow-up email (150 words max). Context: I spoke with Sarah (Head of Engineering at Acme Corp) about our API monitoring tool. She mentioned two pain points: slow incident alert times and missing Slack integration. Tone: warm but professional — no pushy closing. Structure: (1) one sentence re-stating the value for her specific pain points, (2) two bullet points recapping what we agreed on, (3) clear next step with a proposed date.
Included context about the recipient and their pain points
Set a word limit (150) to keep it scannable
Specified three structural elements so the draft is ready to send
WritingLinkedIn Post
Before — vague prompt
Write a LinkedIn post about my product launch.
After — improved version
Write a LinkedIn post (200–250 words) announcing the launch of [Product Name], a [one-line description]. Hook: open with a counterintuitive insight or a concrete result (not "I'm excited to announce"). Body: 3 short paragraphs — the problem it solves, how it works, one customer result or data point. End with a question that invites comments. Use line breaks after every 2 sentences for mobile readability. No hashtags in the body; add 3 relevant hashtags at the end only.
Banned "I'm excited to announce" — the most overused LinkedIn opener
Required mobile-friendly formatting (line breaks)
Separated hashtags from body — algorithm still sees them, but they don't clutter the post
WritingProduct Description
Before — vague prompt
Write a product description.
After — improved version
Write a 100-word e-commerce product description for a stainless-steel insulated water bottle (32 oz, keeps cold 24h / hot 12h, BPA-free, dishwasher safe, available in 5 colors). Target audience: fitness enthusiasts aged 25–40. Tone: energetic but not hypey. Lead with the biggest benefit in the first sentence. Include one social-proof cue ("join 100,000+ athletes"). End with a CTA: "Pick your color."
Gave exact product specs so no invention is required
Defined audience and tone precisely
Required social proof and CTA — the two highest-converting elements
WritingEditing / Proofreading
Before — vague prompt
Edit this text.
After — improved version
Proofread and edit the following text. Correct: (1) grammar and spelling errors, (2) passive voice — rewrite in active voice where possible, (3) sentences over 25 words — split them. Do NOT change the meaning, tone, or key terms. Return the edited text only, followed by a bullet list of every change you made and why.
Listed three specific editing dimensions instead of vague "edit"
"Do NOT change meaning" protects the author's intent
Requiring a change log makes the model accountable for each edit
Data & AnalysisSpreadsheet Analysis
Before — vague prompt
Analyze my spreadsheet data.
After — improved version
Analyze the following CSV data (monthly website traffic for Q1–Q4 2024). Return a JSON object with: { "peak_month": string, "lowest_month": string, "avg_monthly_sessions": number, "month_over_month_growth_pct": [array of numbers], "anomalies": [months where growth deviated > 2 standard deviations], "executive_summary": string (2 sentences max) }. Do not include the raw data in your response.
Defined exact JSON output schema — machine-parseable, not a prose summary
Added statistical anomaly detection with a concrete threshold
"Do not include raw data" prevents the model re-printing the input
Data & AnalysisCompetitive Analysis
Before — vague prompt
Do a competitive analysis for my product.
After — improved version
Perform a competitive analysis comparing [Product A] vs [Product B] vs [Product C] across these dimensions: (1) pricing — tiers and entry cost, (2) core features — what each does well, (3) target customer segment, (4) key weaknesses. Format as a markdown table with columns: Dimension | Product A | Product B | Product C. After the table, add a 3-bullet "strategic takeaway" section. Use only publicly available information.
Required table format — directly scannable, copy-pasteable into a deck
Listed the four comparison dimensions up front
"Strategic takeaway" section forces synthesis, not just description
Data & AnalysisSurvey Results
Before — vague prompt
Summarize these survey results.
After — improved version
Analyze the following NPS survey responses (open-text comments). Group the feedback into 5–7 themes. For each theme: (1) theme name (3 words max), (2) representative quote from the data, (3) frequency (roughly how many responses mention it), (4) sentiment (Positive / Negative / Mixed). Sort by frequency, descending. Do not invent themes not present in the data.
Asked for thematic grouping, not random summarization
Required a representative quote — keeps analysis grounded in actual data
"Do not invent themes" prevents hallucination of non-existent patterns
Data & AnalysisFinancial Summary
Before — vague prompt
Summarize this financial report.
After — improved version
Read the following Q3 earnings report. Extract and return: (1) revenue YoY growth %, (2) gross margin %, (3) operating income, (4) the single biggest risk factor management disclosed, (5) guidance for Q4 (if mentioned). Format as a structured list. Use exact numbers from the document — do not round or estimate. Flag any metric that is missing from the source as [NOT DISCLOSED].
Listed exactly five specific metrics to extract
"Use exact numbers" prevents hallucinated figures
"[NOT DISCLOSED]" flag ensures missing data is explicit, not silently omitted
MarketingAd Copy
Before — vague prompt
Write a Facebook ad for my app.
After — improved version
Write three Facebook ad variants for [App Name], a time-tracking app for freelancers. Each variant should have: headline (6 words max), primary text (50 words max), and CTA button label. Variant A: pain-point hook ("How many unpaid hours did you log last week?"). Variant B: social-proof hook ("47,000 freelancers cut invoice disputes by 80%"). Variant C: feature hook (lead with the standout feature). Keep all copy under a 6th-grade reading level.
Asked for three variants with different hook types — improves A/B testing
Defined exact character limits for each element
Reading level constraint ensures copy converts on mobile
MarketingSEO Meta Tags
Before — vague prompt
Write meta tags for my page.
After — improved version
Write SEO meta tags for a landing page about [topic]. Provide: (1) title tag (50–60 characters, include primary keyword near the front), (2) meta description (140–155 characters, include primary keyword, end with a soft CTA), (3) OG title (can differ from title tag, optimized for social shares), (4) OG description (max 200 characters). Primary keyword: [keyword]. Do not use passive voice.
Specified exact character counts (50–60 title, 140–155 description)
Required OG variants separately — social titles and SEO titles have different jobs
"No passive voice" prevents weak meta descriptions like "information can be found"
MarketingCold Outreach Email
Before — vague prompt
Write a cold email to a potential customer.
After — improved version
Write a cold outreach email (under 100 words) to a VP of Engineering at a mid-size SaaS company. Context: I'm offering an API monitoring tool that cuts incident response time from 45min to under 5min. Open with one sentence showing I researched them (use placeholder [PERSONALIZATION]). State the value in one concrete sentence. Single CTA: a 15-minute call. No buzzwords (no "synergy", "leverage", "game-changing"). No closing paragraph that restates everything.
Strict word limit forces clarity
Required a personalization placeholder — signals the right approach without hallucinating details
Banned specific buzzwords that kill cold email reply rates
MarketingPress Release
Before — vague prompt
Write a press release for our product launch.
After — improved version
Write a press release for the launch of [Product Name]. Format: inverted pyramid — most important info first. Include: (1) headline (15 words max, includes the company name and "launches"), (2) dateline (City, Date), (3) lead paragraph — who, what, when, where, why in 3 sentences, (4) one executive quote (realistic, not hypey), (5) boilerplate About [Company] paragraph (3 sentences). No exclamation marks. Target reading level: journalist.
Inverted pyramid structure is the standard press release format journalists expect
Executive quote guideline ("realistic, not hypey") prevents "we're thrilled to announce"
Audience = journalist means dense, specific, no fluff
Customer SupportRefund Request Reply
Before — vague prompt
Write a reply to a refund request.
After — improved version
Write a customer support reply to a refund request. Tone: empathetic and professional — not robotic or defensive. Structure: (1) acknowledge the frustration in one sentence (do not use "I understand your frustration" — it's clichéd), (2) state the resolution clearly (approved / partial / declined with reason), (3) if declined, offer one alternative (store credit, exchange, or escalation path), (4) close warmly. Max 120 words. First person ("I" not "we") to feel personal.
Banned "I understand your frustration" — research shows it increases anger
"First person" instruction makes the reply feel human, not corporate
Word limit prevents over-explanation that buries the resolution
Customer SupportFAQ Article
Before — vague prompt
Write a FAQ page for my product.
After — improved version
Write 8 FAQ entries for [Product Name], a project management app for agencies. Each entry: question (how the customer actually phrases it — use informal language), answer (max 60 words, no jargon, step-by-step if it's a process). Cover: account setup, billing, team permissions, integrations, and data export. Sort from most-asked (basic setup) to least-asked (advanced config). Format as a definition list (Q: / A:).
"How the customer actually phrases it" yields searchable, natural questions
Ordering from most-asked to least-asked matches how customers scan FAQs
60-word limit keeps each answer focused — longer answers get skipped
Customer SupportEscalation Script
Before — vague prompt
Write a script for handling angry customers.
After — improved version
Write a customer support escalation script for call-center agents handling an angry customer whose order was delayed 3+ weeks. Script structure: (1) opening that acknowledges delay without making excuses (5–10 words), (2) three de-escalation moves (empathy, ownership, action), (3) specific remedies to offer in order: expedited shipping > discount code > refund, (4) closing that confirms resolution and next contact date. Include stage directions in [brackets]. Avoid: "I understand," "unfortunately," "there's nothing I can do."
Stage directions in brackets make the script usable without additional coaching
Escalation ladder (shipping > discount > refund) is business-appropriate
Banned phrases are the ones that most reliably escalate anger
EducationLesson Plan
Before — vague prompt
Write a lesson plan for teaching fractions.
After — improved version
Write a 45-minute lesson plan for teaching equivalent fractions to 4th graders (age 9–10). Learning objective: students can identify and create two equivalent fractions for any simple fraction. Include: (1) warm-up activity (5 min, visual — use fraction strips), (2) direct instruction (10 min — concrete-representational-abstract sequence), (3) guided practice (15 min — partner activity with manipulatives), (4) independent practice (10 min — 6 problems), (5) exit ticket (5 min — 2 problems that assess the objective). Note any common misconceptions to watch for.
CRA (Concrete-Representational-Abstract) is the evidence-based sequence for math instruction
Exit ticket tied to the exact learning objective — not general "check understanding"
Misconceptions note prevents the teacher from being blindsided
EducationQuiz Questions
Before — vague prompt
Write quiz questions about World War II.
After — improved version
Write 10 multiple-choice quiz questions about the causes of World War II, suitable for a 10th-grade history class. Each question must: have exactly four options (A–D), have one unambiguous correct answer, include at least one plausible distractor (common misconception, not obviously wrong). Cover: Treaty of Versailles, rise of nationalism, appeasement policy, and economic factors. Avoid trick questions. After each question, add the correct answer and a one-sentence explanation in [brackets].
Specific topic coverage prevents generic "random WWII facts" questions
Plausible distractors requirement produces questions that actually test understanding
Answer + explanation in brackets lets the teacher reuse without extra prep
EducationExplain a Concept
Before — vague prompt
Explain supply and demand to me.
After — improved version
Explain the economic concept of supply and demand to a 16-year-old who has never studied economics. Use one real-world example they'd relate to (concert ticket prices, not commodity markets). Structure: (1) define demand in one sentence with the example, (2) define supply in one sentence with the same example, (3) explain equilibrium — what happens when supply and demand match, (4) explain what happens when they don't. Total: under 200 words. No graphs — words only.
Anchoring to a relatable example (concert tickets) improves retention by 40%
"No graphs" makes the explanation self-contained and shareable as text
Structural breakdown prevents a rambling wall of economics theory
EducationRubric
Before — vague prompt
Make a grading rubric.
After — improved version
Create a 4-level grading rubric (Excellent / Proficient / Developing / Beginning) for a 5th-grade persuasive essay assignment. Assess these four dimensions: claim clarity, use of evidence, counterargument acknowledgment, and grammar/mechanics. For each level in each dimension, write 1–2 sentences describing what the work looks like at that level. Use observable, specific language (no "good," "adequate," or "poor"). Format as a table: rows = dimensions, columns = levels.
Observable language ("no 'good' or 'adequate'") makes the rubric reliably gradable
Table format is directly pasteable into Google Docs or a PDF
Four dimensions cover the core persuasive essay competencies without over-rubricating
Improve Any Prompt Instantly
Paste your own prompt and get a tailored improvement — powered by Claude, BYO API key, completely free.