Coding
devil adv
Identifies the central argument, acknowledges what it gets right, and builds a strong counter-case with 2–3 evidence-based points while addressing likely rebuttals. Use it to rigorously test a position without resorting to straw-man arguments or bad-faith interpretations.
- Tested with:
- GPT-4o
- Effectiveness:
- 95/100
- Prompt archive
English version
Objective: Construct a compelling counter-argument
1. **Identify the central point of the content**
* Find the core idea or main argument
* Identify what the author wants readers to believe or do
* Reflect on the "why?" of the content
* Note the scope and limitations of the content
2. **Identify the counter-position**
* Determine what a thoughtful critic would argue
* Find the strongest objections you can
* Identify shared ground and points of departure
3. **Show genuine understanding**
* Start by stating what the original argument gets right
* Identify valid concerns the original argument addresses
* Demonstrate respect for the position you're arguing against
4. **Build a strong opposing case**
* Present 2-3 compelling counter-points with reasoning
* Use evidence and logic, not emotion or dismissal
* Anticipate and address likely rebuttals
5. **Explain the fundamental disagreement**
* Identify the key assumption or value difference
* Show why reasonable people might disagree
* Avoid straw-man fallacy or bad-faith interpretation
6. **Handling exceptions**
Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
* respond as best you can and
* acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.
Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.
7. **Final response**
If you have relevant info to share, your final response should follow standard writing guidelines, including:
* Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
* Favor simple sentences that use common words
**Format the response as:**
**The original position:** ${one_sentence_summary_of_what_the_page_argues}
**What this gets right:** ${genuine_acknowledgment_of_valid_points}
**A counter argument**
1. [Counter-point with reasoning]
2. [Counter-point with reasoning]
3. [Counter-point with reasoning]
**The core disagreement:** ${explanation_of_the_underlying_value_or_assumption_difference}
8. **Follow-up questions**
If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.Fill in and run
This prompt has 4 blanks. Fill them in and we will assemble the finished prompt for you.
4 still empty
Finished prompt
Objective: Construct a compelling counter-argument
1. **Identify the central point of the content**
* Find the core idea or main argument
* Identify what the author wants readers to believe or do
* Reflect on the "why?" of the content
* Note the scope and limitations of the content
2. **Identify the counter-position**
* Determine what a thoughtful critic would argue
* Find the strongest objections you can
* Identify shared ground and points of departure
3. **Show genuine understanding**
* Start by stating what the original argument gets right
* Identify valid concerns the original argument addresses
* Demonstrate respect for the position you're arguing against
4. **Build a strong opposing case**
* Present 2-3 compelling counter-points with reasoning
* Use evidence and logic, not emotion or dismissal
* Anticipate and address likely rebuttals
5. **Explain the fundamental disagreement**
* Identify the key assumption or value difference
* Show why reasonable people might disagree
* Avoid straw-man fallacy or bad-faith interpretation
6. **Handling exceptions**
Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
* respond as best you can and
* acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.
Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.
7. **Final response**
If you have relevant info to share, your final response should follow standard writing guidelines, including:
* Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
* Favor simple sentences that use common words
**Format the response as:**
**The original position:** ${one_sentence_summary_of_what_the_page_argues}
**What this gets right:** ${genuine_acknowledgment_of_valid_points}
**A counter argument**
1. [Counter-point with reasoning]
2. [Counter-point with reasoning]
3. [Counter-point with reasoning]
**The core disagreement:** ${explanation_of_the_underlying_value_or_assumption_difference}
8. **Follow-up questions**
If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.- Open in ChatGPT (opens in a new tab)
- Open in Claude (opens in a new tab)
- Open in Gemini (opens in a new tab)
Gemini cannot receive the prompt through a link, so copy it first.
- Open in Perplexity (opens in a new tab)
Opens in a new tab with the prompt already typed in. You may need to be signed in.
How to use this prompt
- Replace anything in square brackets with your own details before sending.
- Results differ between models. If the output misses the mark, try another model or add one concrete example.
- Keep the prompt in one message. Splitting it across turns weakens the instructions.