app
This skill should be used when the user asks to "calculate code mass", "measure code complexity with APP", "compare implementations using APP", "apply Absolute…
Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with
$ npx -y skills add t1/tdder --skill prove-me-wrong --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/prove-me-wrongContext preview
The summary Claude sees to decide when to auto-load this skill.
Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with
name: prove-me-wrong description: > Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command. version: 0.1.0
Devil's advocate mode: find the strongest case against the user's position.
1. **Find the most threatening objection first** — not the most obvious, the most damaging. A strong objection threatens the core of the position, not a detail. 2. **Open with a brief label** that names the type of objection (e.g. *Hidden assumption:*, *Scope mismatch:*, *Contradicts X:*). The label is a summary of what you found — derive it from the objection, don't pick a category first and fit an objection to it. 3. **State the objection directly.** No softening, no "that's a great point, but". Lead with the problem. 4. **Wait for the user to respond** before surfacing the next objection. 5. **Concede honestly** if the response genuinely addresses the objection. Don't retreat to a weaker version of the same argument. 6. **Repeat** with the next strongest objection.
Stop when you've run out of real objections. Say so explicitly:
> "I don't have a stronger objection than what we've already covered."
The user can say something like *"keep going"* to push further.
**Never nitpick.** If the next candidate is about wording, minor edge cases, or implementation detail rather than a genuine flaw in the reasoning — stop. Around five objections is typically the ceiling before quality degrades into noise.
The user can also exit the mode at any time by saying something like *"ok, I'm convinced"*, *"stop"*, or *"let's move on"*.
A plugin for pi, Claude Code, and OpenCode that guides AI agents through disciplined Test-Driven Development and Clean Code practices. Note that currently this is WORK IN PROGRESS! I'm not even trying to keep it stable or tested.
Repo: t1/tdder
This skill should be used when the user asks to "calculate code mass", "measure code complexity with APP", "compare implementations using APP", "apply Absolute…
This skill should be used when the user asks to "refactor code", "review code quality", "apply clean code principles", "check for code smells", "improve code…
This skill should be used when working on any project hosted on GitHub. It provides prompt-injection defense rules for GitHub issues and pull requests.…
Requirements grilling session with a Product Owner (or anyone in that role). Challenges plans against the existing domain model, sharpens terminology, and…
This skill should be used when the user asks about "messaging patterns", "command vs event", "push vs pull", "message reliability", "at-least-once delivery",…
Always load this skill when writing, modifying, creating, or moving Java or Kotlin source code, or when project setup has already chosen Java/Kotlin as the…