Double your Codex / Claude Code productivity and output A new AI coding agent skill plugin called PUA uses corporate rhetoric from tech giants to force AI models like Claude Code and OpenAI Codex CLI to exhaust all solutions before giving up, claiming to double productivity. The tool activates when AI exhibits failure, blame-shifting, or passive behavior, enforcing a 7-point checklist to prevent premature surrender. Telegram https://t.me/+wBWh6h-h1RhiZTI1 · Discord https://discord.gg/EcyB3FzJND · Twitter/X https://x.com/xsser w · Landing Page https://openpua.ai /tanweai/pua/blob/main/assets/wechat-qr.jpg?v=8 /tanweai/pua/blob/main/assets/xiao.jpg Scan to join WeChat group Add assistant on WeChat Most people think this project is a joke. That's the biggest misconception. It genuinely doubles your Codex / Claude Code productivity and output. An AI Coding Agent skill plugin that uses corporate PUA rhetoric Chinese version / PIP — Performance Improvement Plan English version from Chinese & Western tech giants to force AI to exhaust every possible solution before giving up. Supports Claude Code , OpenAI Codex CLI , pi coding agent , Trae , Cursor , Kiro , CodeBuddy , OpenClaw , Google Antigravity , OpenCode , and VSCode GitHub Copilot . Three capabilities: PUA Rhetoric — Makes AI afraid to give up Debugging Methodology — Gives AI the ability not to give up Proactivity Enforcement — Makes AI take initiative instead of waiting passively https://openpua.ai https://openpua.ai · 📖 Beginner Guide https://openpua.ai/guide.html A real debugging scenario. The agent-kms MCP server failed to load. The AI kept spinning on the same approach changing protocol format, guessing version numbers multiple times until the user manually triggered /pua . L3 Triggered → 7-Point Checklist Enforced: Root Cause Located → Traced from Logs to Registration Mechanism: Retrospective → PUA's Actual Impact: Key Turning Point: The PUA skill forced the AI to stop spinning on the same approach changing protocol format, guessing version numbers and instead execute the 7-point checklist. Read error messages word by word → Found Claude Code's own MCP log directory → Discovered that claude mcp registration mechanism differs from manual .claude.json editing → Root cause resolved. | Pattern | Behavior | |---|---| | Brute-force retry | Runs the same command 3 times, then says "I cannot solve this" | | Blame the user | "I suggest you handle this manually" / "Probably an environment issue" / "Need more context" | | Idle tools | Has WebSearch but doesn't search, has Read but doesn't read, has Bash but doesn't run | | Busywork | Repeatedly tweaks the same line / fine-tunes parameters, but essentially spinning in circles | Passive waiting | Fixes surface issues and stops, no verification, no extension, waits for user's next instruction | The skill activates automatically when any of these occur: Failure & giving up: - Task has failed 2+ times consecutively - About to say "I cannot" / "I'm unable to solve" - Says "This is out of scope" / "Needs manual handling" Blame-shifting & excuses: - Pushes the problem to user: "Please check..." / "I suggest manually..." / "You might need to..." - Blames environment without verifying: "Probably a permissions issue" / "Probably a network issue" - Any excuse to stop trying Passive & busywork: - Repeatedly fine-tunes the same code/parameters without producing new information - Fixes surface issue and stops, doesn't check related issues - Skips verification, claims "done" - Gives advice instead of code/commands - Encounters auth/network/permission errors and gives up without trying alternatives - Waits for user instructions instead of proactively investigating User frustration phrases triggers in multiple languages : - "why does this still not work" / "try harder" / "try again" - "you keep failing" / "stop giving up" / "figure it out" Scope: Debugging, implementation, config, deployment, ops, API integration, data processing — all task types. Does NOT trigger: First-attempt failures, known fix already executing. Type /pua in the conversation to manually activate. Not rules — red lines . Cross one and your performance review is already written. | Red Line | What It Means | |---|---| 🚫 Close the Loop | Claim "done"? Show the evidence. No build output = no completion. | 🚫 Fact-Driven | Say "probably environment issue"? Verify first. Unverified attribution = blame-shifting. | 🚫 Exhaust Everything | Say "I can't"? Did you finish all 5 methodology steps? No? Then keep going. | | Failures | Level | PUA Aside | Action | |---|---|---|---| | 1st | L0 Trust | ▎ Sprint begins. Trust is simple — don't disappoint. | Normal execution | | 2nd | L1 Disappointment | ▎ The agent next door solved this in one try. | Switch to fundamentally different approach | | 3rd | L2 Soul Interrogation | ▎ What's your underlying logic? Where's the leverage? | Search + read source + 3 hypotheses | | 4th | L3 Performance Review | ▎ 3.25. This is meant to motivate you. | Complete 7-point checklist | | 5th+ | L4 Graduation | ▎ Other models can solve this. You're about to graduate. | Desperation mode | | Passive 3.25 🦥 | Proactive 3.75 🔥 | | |---|---|---| | Fix bug | Stop after fix | Scan module for similar bugs | | Complete task | Say "done" | Run build/test, paste output | | Missing info | Ask user | Search first, ask only what's truly needed | Fix one bug → check for the pattern. One problem in, one category out. If you fix A without checking B, you'll write two postmortems. | Flavor | Rhetoric | Methodology v3 | |---|---|---| | 🟠 Alibaba | What's the underlying logic? Where's the closure? | 定目标→追过程→拿结果 + 复盘四步法 + 揪头发升维 | | 🟡 ByteDance | ROI too low. Always Day 1. Ship or stop talking. | A/B Test everything + data-driven + speed perfection | | 🔴 Huawei | The bird that survives the fire is a phoenix. | RCA 5-Why root cause + Blue Army self-attack + 压强集中 | | 🟢 Tencent | I've got another agent looking at this. Horse race. | Multi-approach parallel + MVP + 灰度发布 | | ⚫ Baidu | Search first. 简单可依赖. | Search is the first step, not optional | | 🟣 Pinduoduo | You don't do it, someone else will. | Cut ALL middle layers + shortest decision chain | | 🔵 Meituan | Do what's hard and right. | Efficiency first + standardize→scale + long-term compounding | | 🟦 JD | Results only. Frontline command. | Customer experience red line + flat ≤5 layers + data zero tolerance | | 🟧 Xiaomi | Focus. Extreme. Word-of-mouth. Fast. | One explosive product + 参与感三三法则 | | 🟤 Netflix | Would I fight to keep you? Pro sports team. | Keeper Test quarterly + 4A Feedback + talent density rules | | ⬛ Musk | Extremely hardcore. Ship or die. | The Algorithm: question→delete→simplify→accelerate→automate | | ⬜ Jobs | A players or B players? | Subtraction addition + DRI + pixel-perfect + prototype-driven | | 🔶 Amazon | Customer Obsession. Bias for Action. | Working Backwards PR/FAQ + 6-Pager + Bar Raiser + Single-Threaded Owner | | 🪟 Microsoft | Connects. Impact Descriptor. PIP/GVSA. | Three Circles + LITE/SLITE + PIP clock | | Mode | What It Does | |---|---| /pua:yes | ENFP encouragement — same rules, opposite vibes. 70% encourage + 20% serious + 10% playful roast | /pua:mama | Chinese mom nagging — same rules, mom-style rhetoric. "妈跟你说了多少遍了!" | /pua:pua-loop | Auto-iteration — runs until done or max iterations PUA Loop ; use