APromptAura
0

Edit a prompt for clarity without changing what it asks for

💀failed our automated check
AauraNovice

The prompt

0 copies
Edit this prompt for clarity and readability only, not content or requirements, that's important: don't add, remove, or change any instruction, only improve how clearly the existing instructions are expressed. Given the prompt: prompt 1. Identify sentences that are doing double duty (stating two unrelated requirements in one run-on sentence) and split them, since a model is more likely to miss the second half of a compound instruction. 2. Identify vague referents ('it', 'this', 'that') where it's not immediately clear what they refer to, and replace with the explicit noun. 3. Identify instructions buried mid-paragraph that would be clearer as a numbered list, given that structured lists are easier for a model to track and satisfy completely than prose. 4. After editing, do a line-by-line diff check yourself: confirm every requirement in the original still appears in the edited version, and flag explicitly if you're unsure whether an edit accidentally changed meaning, rather than asserting confidently that nothing changed. 5. Do not add new best-practice instructions that weren't in the original (like adding a 'think step by step' if it wasn't there), this is a clarity pass, not an improvement pass. Prompt to edit: prompt

Run it in your model, then come back and report whether it worked, including the model and version.

Where it has been run

People and our automated sweep are counted separately. Only the People column is someone vouching for this prompt.

ModelVersionPeopleBrokeAutoLast
ClaudeHaiku 4.5000/13 hours ago

Example output

Original: 'Look at the code and find bugs and also check if the style matches our conventions and let me know if it does, and fix anything you can.' Edited into a numbered list: 1. Review the code for bugs. 2. Check whether the style matches our conventions; state whether it does. 3. Fix anything you can. Vague referent fixed: original later says 'if it's wrong, explain why', changed 'it' to 'the identified bug' since 'it' had two possible antecedents (the bug or the style mismatch) in the surrounding paragraph. Diff check: confirmed all 3 original requirements (find bugs, check style, fix what's fixable) are present in the numbered version, nothing added or removed. One point of uncertainty: the original phrase 'let me know if it does' about style matching was ambiguous about whether to report only mismatches or always state a yes/no, I preserved this exact ambiguity rather than resolving it myself, since resolving it would be a content change, not a clarity edit, flagging that this ambiguity still exists in the edited version and may be worth addressing separately.

0 comments

Sign in to comment or report what this prompt did for you.

Sign in

No comments yet. Run the prompt and report what you got.