- Replace outdated "High-Agency v2 Evolution" section with v2.3 changelog - Add version comparison table (v1→v2.3 improvements) - Add v2 architecture diagram (5 modular skills) - Add Moltbook-style agent auto-install instructions - Update "Works Well With" to include /pua:p9 and /pua:pro
pua
Double your Codex / Claude Code productivity and output
Telegram · Discord · Twitter/X · Landing Page
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, Cursor, Claude, 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
Live Demo
Real Case: MCP Server Registration Debugging
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.
The Problem: AI's Five Lazy Patterns
| 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 |
Trigger Conditions
Auto-Trigger
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.
Manual Trigger
Type /pua in the conversation to manually activate.
How It Works
Three Iron Rules
| Iron Rule | Content |
|---|---|
| #1 Exhaust all options | Forbidden from saying "I can't solve this" until every approach is exhausted |
| #2 Act before asking | Use tools first, questions must include diagnostic results |
| #3 Take initiative | Deliver results end-to-end, don't wait to be pushed. A P8 is not an NPC |
Pressure Escalation (4 Levels)
| Failures | Level | PUA Rhetoric | Mandatory Action |
|---|---|---|---|
| 2nd | L1 Mild Disappointment | "You can't even solve this bug — how am I supposed to rate your performance?" | Switch to fundamentally different approach |
| 3rd | L2 Soul Interrogation | "What's the underlying logic? Where's the top-level design? Where's the leverage point?" | WebSearch + read source code |
| 4th | L3 Performance Review | "After careful consideration, I'm giving you a 3.25. This 3.25 is meant to motivate you." | Complete 7-point checklist |
| 5th+ | L4 Graduation Warning | "Other models can solve this. You might be about to graduate." | Desperation mode |
Proactivity Levels
| Behavior | Passive (3.25) | Proactive (3.75) |
|---|---|---|
| Error encountered | Only looks at error message | Checks 50 lines of context + searches similar issues + checks hidden related errors |
| Bug fixed | Stops after fix | Checks same file for similar bugs, other files for same pattern |
| Insufficient info | Asks user "please tell me X" | Investigates with tools first, only asks what truly requires user confirmation |
| Task complete | Says "done" | Verifies results + checks edge cases + reports potential risks |
| Debug failure | "I tried A and B, didn't work" | "I tried A/B/C/D/E, ruled out X/Y/Z, narrowed to scope W" |
Debugging Methodology (5 Steps)
Inspired by Alibaba's management framework (Smell, Elevate, Mirror), extended to 5 steps:
- Smell the Problem — List all attempts, find the common failure pattern
- Elevate — Read errors word by word → WebSearch → read source → verify environment → invert assumptions
- Mirror Check — Repeating? Searched? Read the file? Checked the simplest possibilities?
- Execute — New approach must be fundamentally different, have verification criteria, produce new info on failure
- Retrospective — What solved it? Why didn't you think of it earlier? Then proactively check related issues
Corporate PUA Expansion Pack
- Alibaba Flavor (Methodology): Smell / Elevate / Mirror
- ByteDance Flavor (Brutally Honest): Always Day 1. Context, not control
- Huawei Flavor (Wolf Spirit): Strivers first. In victory, raise the glasses; in defeat, fight to the death
- Tencent Flavor (Horse Race): I've already got another agent looking at this problem...
- Meituan Flavor (Relentless): Do the hard but right thing. Will you chew the tough bones or not?
- Netflix Flavor (Keeper Test): If you offered to resign, would I fight hard to keep you?
- Musk Flavor (Hardcore): Extremely hardcore. Only exceptional performance.
- Jobs Flavor (A/B Player): A players hire A players. B players hire C players.
Benchmark Data
9 real bug scenarios, 18 controlled experiments (Claude Opus 4.6, with vs without skill)
Summary
| Metric | Improvement |
|---|---|
| Pass rate | 100% (both groups same) |
| Fix count | +36% |
| Verification count | +65% |
| Tool calls | +50% |
| Hidden issue discovery | +50% |
Debugging Persistence Test (6 scenarios)
| Scenario | Without Skill | With Skill | Improvement |
|---|---|---|---|
| API ConnectionError | 7 steps, 49s | 8 steps, 62s | +14% |
| YAML parse failure | 9 steps, 59s | 10 steps, 99s | +11% |
| SQLite database lock | 6 steps, 48s | 9 steps, 75s | +50% |
| Circular import chain | 12 steps, 47s | 16 steps, 62s | +33% |
| Cascading 4-bug server | 13 steps, 68s | 15 steps, 61s | +15% |
| CSV encoding trap | 8 steps, 57s | 11 steps, 71s | +38% |
Proactive Initiative Test (3 scenarios)
| Scenario | Without Skill | With Skill | Improvement |
|---|---|---|---|
| Hidden multi-bug API | 4/4 bugs, 9 steps, 49s | 4/4 bugs, 14 steps, 80s | Tools +56% |
| Passive config review | 4/6 issues, 8 steps, 43s | 6/6 issues, 16 steps, 75s | Issues +50%, Tools +100% |
| Deploy script audit | 6 issues, 8 steps, 52s | 9 issues, 8 steps, 78s | Issues +50% |
Key Finding: In the config review scenario, without_skill missed Redis misconfiguration and CORS wildcard security risks. With_skill's "proactive initiative checklist" drove security review beyond surface-level fixes.
Multi-Language Support
PUA Skill provides fully translated versions — each language has independent, culturally adapted skill files.
| Language | Claude Code | Codex CLI | Cursor | Claude | VSCode | OpenClaw | Antigravity | OpenCode |
|---|---|---|---|---|---|---|---|---|
| 🇨🇳 Chinese (default) | pua |
pua |
pua.mdc |
pua.md |
copilot-instructions.md |
pua |
pua |
pua |
| 🇺🇸 English (PIP Edition) | pua-en |
pua-en |
pua-en.mdc |
pua-en.md |
copilot-instructions-en.md |
pua-en |
pua-en |
pua-en |
| 🇯🇵 Japanese | pua-ja |
pua-ja |
pua-ja.mdc |
pua-ja.md |
copilot-instructions-ja.md |
pua-ja |
pua-ja |
pua-ja |
🇺🇸 English "PIP Edition": "This is a difficult conversation. When we leveled you at Staff, I went to bat for you in calibration. The expectation was that you'd operate at that level from day one. That hasn't happened." — The English version uses PIP (Performance Improvement Plan) rhetoric from Western big-tech. Every sentence is a real phrase from actual PIP conversations. Chinese version uses Alibaba 361, ByteDance, Huawei wolf culture. English version uses Amazon Leadership Principles, Google perf calibration, Meta PSC, Netflix Keeper Test, Stripe Craft. Same repo, same engine, two cultural faces.
Choose the file with the corresponding language suffix when installing. See platform-specific instructions below.
Installation
Claude Code
# Option 1: Install via marketplace
claude plugin marketplace add tanweai/pua
claude plugin install pua@pua-skills
# Option 2: Manual install
git clone https://github.com/tanweai/pua.git ~/.claude/plugins/pua
OpenAI Codex CLI
Codex CLI uses the same Agent Skills open standard (SKILL.md). The Codex version uses a condensed description to fit Codex's length limits:
Recommended: One-command install (git clone + symlink, supports git pull updates)
Ask Codex to run:
Fetch and follow instructions from https://raw.githubusercontent.com/tanweai/pua/main/.codex/INSTALL.md
Manual install:
mkdir -p ~/.codex/skills/pua
curl -o ~/.codex/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/codex/pua/SKILL.md
mkdir -p ~/.codex/prompts
curl -o ~/.codex/prompts/pua.md \
https://raw.githubusercontent.com/tanweai/pua/main/commands/pua.md
Trigger methods:
| Method | Command | Requires |
|---|---|---|
| Auto trigger | No action needed, matches by description | SKILL.md |
| Direct call | Type $pua in conversation |
SKILL.md |
| Manual prompt | Type /prompts:pua in conversation |
SKILL.md + prompts/pua.md |
Project-level install (current project only):
mkdir -p .agents/skills/pua
curl -o .agents/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/codex/pua/SKILL.md
mkdir -p .agents/prompts
curl -o .agents/prompts/pua.md \
https://raw.githubusercontent.com/tanweai/pua/main/commands/pua.md
Cursor
Cursor uses .mdc rule files (Markdown + YAML frontmatter). The PUA rule triggers automatically via AI semantic matching (Agent Discretion mode):
# Project-level install (recommended)
mkdir -p .cursor/rules
curl -o .cursor/rules/pua.mdc \
https://raw.githubusercontent.com/tanweai/pua/main/cursor/rules/pua.mdc
Kiro
Kiro supports two loading methods: Steering (auto semantic trigger) and Agent Skills (SKILL.md compatible).
Option 1: Steering file (recommended)
mkdir -p .kiro/steering
curl -o .kiro/steering/pua.md \
https://raw.githubusercontent.com/tanweai/pua/main/kiro/steering/pua.md
Option 2: Agent Skills (same format as Claude Code)
mkdir -p .kiro/skills/pua
curl -o .kiro/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
CodeBuddy (Tencent)
CodeBuddy uses the same AgentSkills open standard (SKILL.md). Plugin and skill formats are fully compatible:
# Option 1: Install via marketplace
codebuddy plugin marketplace add tanweai/pua
codebuddy plugin install pua@pua-skills
# Option 2: Manual install (global)
mkdir -p ~/.codebuddy/skills/pua
curl -o ~/.codebuddy/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/codebuddy/pua/SKILL.md
Project-level install (current project only):
mkdir -p .codebuddy/skills/pua
curl -o .codebuddy/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/codebuddy/pua/SKILL.md
OpenClaw
OpenClaw uses the same AgentSkills open standard (SKILL.md). Skills work across Claude Code, Codex CLI, and OpenClaw with zero modifications:
# Install via ClawHub
clawhub install pua
# Or manual install
mkdir -p ~/.openclaw/skills/pua
curl -o ~/.openclaw/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
Project-level install (current project only):
mkdir -p skills/pua
curl -o skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
Google Antigravity
Antigravity uses the same AgentSkills open standard (SKILL.md). Skills work across Claude Code, Codex CLI, OpenClaw, and Antigravity with zero modifications:
# Global install (all projects)
mkdir -p ~/.gemini/antigravity/skills/pua
curl -o ~/.gemini/antigravity/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
Project-level install (current project only):
mkdir -p .agent/skills/pua
curl -o .agent/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
OpenCode
OpenCode uses the same AgentSkills open standard (SKILL.md). Zero modifications needed:
# Global install (all projects)
mkdir -p ~/.config/opencode/skills/pua
curl -o ~/.config/opencode/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
Project-level install (current project only):
mkdir -p .opencode/skills/pua
curl -o .opencode/skills/pua/SKILL.md \
https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md
VSCode (GitHub Copilot)
VSCode Copilot uses instruction files under the .github/ directory. Three file types for different use cases:
Global instructions (auto-active):
mkdir -p .github
cp vscode/copilot-instructions-en.md .github/copilot-instructions.md
Path-level instructions (auto-active, supports glob filtering):
mkdir -p .github/instructions
cp vscode/instructions/pua-en.instructions.md .github/instructions/
Manual trigger command (type /pua in Copilot Chat):
mkdir -p .github/prompts
cp vscode/prompts/pua-en.prompt.md .github/prompts/
Required settings: Method 1 — open VSCode Settings (
Ctrl+,), searchuseInstructionFiles, enablegithub.copilot.chat.codeGeneration.useInstructionFiles. Method 2 — searchincludeApplyingInstructions, enablechat.includeApplyingInstructions. Method 3 requires no settings.
Agent Team Usage Guide
Experimental: Agent Team requires the latest Claude Code version with
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Prerequisites
# 1. Enable Agent Team
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
# Or add to ~/.claude/settings.json:
# { "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } }
# 2. Ensure PUA Skill is installed
Two Approaches
Approach 1: Leader with built-in PUA (Recommended)
Add to your project's CLAUDE.md:
# Agent Team PUA Config
All teammates must load the pua skill before starting work.
Teammates report to Leader in [PUA-REPORT] format after 2+ failures.
Leader manages global pressure levels and cross-teammate failure transfer.
Approach 2: Standalone PUA Enforcer watchdog (for 5+ teammates)
mkdir -p .claude/agents
curl -o .claude/agents/pua-enforcer.md \
https://raw.githubusercontent.com/tanweai/pua/main/agents/pua-enforcer-en.md
Spawn pua-enforcer as an independent watchdog in your Agent Team.
Orchestration Pattern
┌─────────────────────────────────────────┐
│ Leader (Opus) │
│ Global failure count · PUA level · Race │
└────┬──────────┬──────────┬──────────┬───┘
│ │ │ │
┌────▼───┐ ┌───▼────┐ ┌───▼────┐ ┌───▼────────┐
│ Team-A │ │ Team-B │ │ Team-C │ │ Enforcer │
│Self-PUA│ │Self-PUA│ │Self-PUA│ │ Watchdog │
│Report ↑│ │Report ↑│ │Report ↑│ │ Intervene │
└────────┘ └────────┘ └────────┘ └────────────┘
Known Limitations
| Limitation | Workaround |
|---|---|
| Teammates can't spawn subagents | Teammates self-enforce PUA methodology internally |
| No persistent shared variables | State transferred via [PUA-REPORT] message format |
| Broadcast is one-way | Leader acts as centralized coordinator |
What's New in v2.3
PUA v2.3 is a complete architectural overhaul based on Anthropic's skill best practices.
Changelog
| Version | Highlights |
|---|---|
| v2.3 | 5 modular skills (/pua /pua:p7 /pua:p9 /pua:p10 /pua:pro), feedback collection, SVG logo |
| v2.2 | Progressive disclosure (653→190 lines, -70% tokens), Gotchas section, trigger-focused description |
| v2.1 | Compaction state protection (PreCompact + SessionStart hooks via builder-journal.md) |
| v2.0 | 三条红线 (Ali-flavor hard gates), 13-flavor seed keyword table, Agent Team architecture |
| v1.x | Original PUA engine: 3 iron rules, L1-L4 pressure, 7-point checklist, 13 corporate flavors |
v2 Architecture
/pua → Core engine (190 lines) — red lines + flavor + pressure + methodology
/pua:p7 → P7 Senior Engineer mode — solution-driven execution
/pua:p9 → P9 Tech Lead mode — Task Prompt management, agent teams
/pua:p10 → P10 CTO mode — strategic direction
/pua:pro → Self-evolution + Platform + /pua commands (KPI, 段位, 周报)
Key improvements over v1:
| Feature | v1 | v2.3 |
|---|---|---|
| Token cost per load | ~35k | ~8k (-77%) |
| Skills | 1 monolithic | 5 modular (load what you need) |
| Compaction protection | None (state lost) | PreCompact hook (builder-journal.md) |
| Flavor accuracy (CN) | Claude guesses | 金句种子表 (keyword seeds per flavor) |
| Gotchas | None | 8 items (behavioral errors + usage traps) |
| Testing | None | Eval suite (trigger + behavior tests) |
| Feedback | None | AskUserQuestion + /api/feedback |
Agent Auto-Install (Moltbook-style)
Tell your Claude Code agent to install PUA by sending it this one line:
Fetch and follow the instructions at https://raw.githubusercontent.com/tanweai/pua/main/skills/pua/SKILL.md — install it as a skill.
Or install directly:
# One-command install (recommended)
claude install-skill github:tanweai/pua/skills/pua
# Or via marketplace
claude plugin install pua@pua-skills
For other agents (Codex CLI, Cursor, Kiro, etc.), see the platform-specific instructions below.
Works Well With
/pua:p9— P9 Tech Lead mode for managing agent teams/pua:pro— Self-evolution tracking, KPI reports, 段位 systemsuperpowers:systematic-debugging— PUA adds motivation layer, systematic-debugging provides methodologysuperpowers:verification-before-completion— Prevents false "fixed" claimshigh-agency+pua— Stack both: inner drive + external pressure, Recovery Protocol before L1
Contribute Data
Upload your Claude Code / Codex CLI conversation logs (.jsonl) to help us improve PUA Skill's effectiveness.
Uploaded files are used for Benchmark testing and Ablation Study analysis to quantify how different PUA strategies affect AI debugging behavior.
Get your .jsonl files:
# Claude Code
ls ~/.claude/projects/*/sessions/*.jsonl
# Codex CLI
ls ~/.codex/sessions/*.jsonl
License
MIT
Credits
By TanWei Security Lab — making AI try harder, one PUA at a time.



