pua

pua

Double your Codex / Claude Code productivity and output

🇨🇳 中文 | 🇹🇼 繁體中文 | 🇯🇵 日本語 | 🇺🇸 English

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 (Pick-Up Artist) rhetoric from Chinese & Western tech giants to force AI to exhaust every possible solution before giving up. Supports Claude Code, OpenAI Codex CLI, Cursor, Kiro, OpenClaw, Google Antigravity, and OpenCode. Three capabilities:

1. PUA Rhetoric — Makes AI afraid to give up
2. Debugging Methodology — Gives AI the ability not to give up
3. Proactivity Enforcement — Makes AI take initiative instead of waiting passively

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