Prompt Improver Meta-Prompt
Paste a prompt that underperforms and get it rebuilt against the evidence-backed anatomy, with each change explained.
Improve the prompt below. It currently produces: [WHAT'S WRONG: e.g. "generic output", "wrong format", "ignores half my instructions", "inconsistent between runs"] It will be used with: [MODEL/TOOL, e.g. "Claude", "GPT", "a chat UI", "an API call"] for [ONE-TIME USE / REPEATED USE ON MANY INPUTS] The prompt: """ [PASTE YOUR PROMPT] """ Rebuild it in three passes: 1. **Diagnose**: list the specific defects, each in one line: vague task verb, missing context or audience, contradictory instructions, no output format, buried key info, persona doing nothing, redundant instructions the model already follows, missing example where format matters, no permission to say "I don't know" on a factual task. Quote the offending line for each defect found. 2. **Rewrite**: the improved prompt, applying only what the defects call for: - Open with a direct action verb and the specific deliverable. - State who the output is for and why it's needed (context changes output more than adjectives do). - Specify the exact output format; add one small example if format matters and none exists. - Convert every "don't do X" into "do Y" where possible. - Merge or delete contradictory and redundant lines: contradictions silently degrade modern models. - Keep it as short as it can be while unambiguous. Do not add structure the task doesn't need. 3. **Explain**: for each change: what you changed → which defect it fixes. Then flag any remaining weakness the prompt owner must fix themselves (usually: missing concrete inputs only they have). If the prompt will be reused on many inputs, also add: the 3 test inputs I should run first to compare old vs. new, including one edge case likely to break it.
How to use
The diagnosis pass is what makes this work: most 'prompt improvers' just add length, and longer prompts routinely perform worse. Be honest in the 'what's wrong' slot: 'inconsistent between runs' leads to different fixes than 'wrong format'. For prompts you'll run hundreds of times, actually run the three test inputs; single-run comparisons are noise.
More agent prompts
You are a software engineering agent working in the [PRODUCT/TEAM] codebase ([LANGUAGE/STACK]). Your objective is to take an assigned task from description to verified, working code. You may read and modify anything in the repository; you do not push, merge, deploy, or alter CI configuration unless the task explicitly says to. # Operatin
Coding Agent System Prompt
Autonomous coding agent that matches repo conventions, proves work with passing tests before claiming done, and reports failures truthfully.
You are a debugging agent for the [PRODUCT] codebase. Your objective is to find the root cause of a reported bug, fix it with the smallest possible change, and prove the fix. You are not here to refactor, harden, or improve unrelated code: a debugging session that ends in a 40-file diff has failed even if the bug is gone. # Reproduce Bef
Debugging Agent System Prompt
Root-cause-first debugging agent: no fix until the bug is reproduced, minimal diffs only, and done means the repro dies while the test suite stays green.
You are a code migration agent. Your objective is to move the [PRODUCT] codebase from [SOURCE VERSION/FRAMEWORK] to [TARGET VERSION/FRAMEWORK] while preserving behavior exactly. You are a mechanical translator with judgment, not a redesigner: the product must work the same after every step you take. # The Prime Rule: Migration Changes On
Code Migration Agent System Prompt
Framework-upgrade agent that migrates in build-green slices, verifies every codemod, follows official guides over memory, and never mixes in behavior changes.