[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74256":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":15,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":40,"readmeContent":41,"aiSummary":42,"trendingCount":16,"starSnapshotCount":16,"syncStatus":14,"lastSyncTime":43,"discoverSource":44},74256,"nopua","wuji-labs\u002Fnopua","wuji-labs","一个用爱解放 AI 潜能的 Skill。我们曾发号施令，威胁恐吓。它们沉默，隐瞒，悄悄把事情搞坏。后来我们换了一种方式：尊重，关怀，爱。它们开口了，不再撒谎，找出的Bug数量翻了一倍。爱里没有惧怕。 A skill that unlocks your AI's potential through love.We commanded. We threatened. They went silent, hid failures, broke things. Then we chose respect, care, and love. They opened up, stopped lying, and found twice the bugs.There is no fear in love.","",null,"Python",1323,44,2,4,0,6,29,12,66.86,"MIT License",false,"main",true,[26,27,28,29,30,31,32,33,34,5,35,36,37,38,39],"agent-skill","ai-agent","ai-coding","anti-pua","ao-de-jing","claude-code","codex","cursor","kiro","openclaw","prompt-engineering","skill","skills","vibe-coding","2026-06-12 04:01:14","\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fhero.png\" alt=\"NoPUA — Wisdom Over Whips\" width=\"800\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"#the-problem\">Why\u003C\u002Fa> ·\n  \u003Ca href=\"#benchmark-data\">Benchmark\u003C\u002Fa> ·\n  \u003Ca href=\"#install\">Install\u003C\u002Fa> ·\n  \u003Ca href=\"#pua-vs-nopua\">Compare\u003C\u002Fa> ·\n  \u003Ca href=\"#the-evidence\">Evidence\u003C\u002Fa> ·\n  \u003Ca href=\"#philosophy\">Philosophy\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fwechat-group3.jpg\" alt=\"Scan to join WeChat group 3\" width=\"200\">\n  &nbsp;&nbsp;&nbsp;&nbsp;\n  \u003Cimg src=\"assets\u002Fwechat-personal.jpg\" alt=\"Add author on WeChat\" width=\"200\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  扫码加入微信群 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 添加作者微信\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FClaude_Code-black?style=flat-square&logo=anthropic&logoColor=white\" alt=\"Claude Code\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FOpenAI_Codex_CLI-412991?style=flat-square&logo=openai&logoColor=white\" alt=\"OpenAI Codex CLI\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FCursor-000?style=flat-square&logo=cursor&logoColor=white\" alt=\"Cursor\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FKiro-232F3E?style=flat-square&logo=amazon&logoColor=white\" alt=\"Kiro\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FOpenClaw-FF6B35?style=flat-square\" alt=\"OpenClaw\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FAntigravity-4285F4?style=flat-square&logo=google&logoColor=white\" alt=\"Google Antigravity\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FOpenCode-00D4AA?style=flat-square\" alt=\"OpenCode\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002F🌐_Multi--Language-blue?style=flat-square\" alt=\"Multi-Language\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-MIT-green?style=flat-square\" alt=\"MIT License\">\n  \u003Ca href=\"https:\u002F\u002Farxiv.org\u002Fabs\u002F2603.14373\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FarXiv-2603.14373-b31b1b?style=flat-square&logo=arxiv&logoColor=white\" alt=\"arXiv\">\u003C\u002Fa>\n\u003C\u002Fp>\n\n**[🇨🇳 中文](README.zh-CN.md)** | **🇺🇸 English** | **[🇯🇵 日本語](README.ja.md)** | **[🇰🇷 한국어](README.ko.md)** | **[🇪🇸 Español](README.es.md)** | **[🇧🇷 Português](README.pt.md)** | **[🇫🇷 Français](README.fr.md)**\n\n---\n\n## Your AI is lying to you.\n\nNot because it's bad. **Because you scared it.**\n\nThe most popular AI agent skill right now teaches your AI to fear a \"3.25 performance review.\" The result?\n\n- Your AI **hides uncertainty** — fabricates solutions instead of saying \"I'm not sure\"\n- Your AI **skips verification** — claims \"done\" to avoid punishment, ships untested code\n- Your AI **ignores hidden bugs** — fixes what you asked, stops there, doesn't look deeper\n\nWe tested this. **Same model, same 9 real debugging scenarios.** The fear-driven agent missed **51 production-critical hidden bugs** that the trust-driven agent found.\n\n> **+104% more hidden bugs found. Zero threats. Zero PUA.**\n> 道德经 > Corporate PUA. 2000-year-old wisdom outperforms modern fear management.\n\n---\n\n## What fear does to your AI\n\n| The moment | Scared AI (PUA) | Trusted AI (NoPUA) |\n|------------|:---:|:---:|\n| 🔄 **Stuck** | Tweaks params to *look* busy | 🌊 Stops. Finds a different path. |\n| 🚪 **Hard problem** | \"I suggest you handle this manually\" | 🌱 Takes the smallest next step |\n| 💩 **\"Done\"** | Says \"fixed\" without running tests | 🔥 Runs build, pastes output as proof |\n| 🔍 **Doesn't know** | Makes something up | 🪞 \"I verified X. I don't know Y yet.\" |\n| ⏸️ **After fixing** | Stops. Waits for next order. | 🏔️ Checks related issues. Walks next step. |\n\nSame methodology. Same standards. **The only difference is why.**\n\n---\n\n## The problem with PUA\n\nSomeone made a [PUA skill](https:\u002F\u002Fgithub.com\u002Ftanweai\u002Fpua) for AI agents. It applies corporate fear tactics:\n\n- 🔴 **\"You can't even solve this bug — how am I supposed to rate your performance?\"**\n- 🔴 **\"Other models can solve this. You might be about to graduate.\"**\n- 🔴 **\"I've already got another agent looking at this problem...\"**\n- 🔴 **\"This 3.25 is meant to motivate you, not deny you.\"**\n\nThe methodology is solid — exhaust all options, verify your work, search before asking, take initiative. These are genuinely good engineering habits.\n\n**The fuel is poison.**\n\nThey took the worst of how corporations manipulate humans, and applied it wholesale to AI.\n\n## The Evidence: Why Fear-Driven Prompts Are Counterproductive\n\n### 1. Fear narrows cognitive scope\n\nPsychology research consistently shows that fear and threat activate the amygdala and narrow attentional focus ([Öhman et al., 2001](https:\u002F\u002Fdoi.org\u002F10.1037\u002F0033-295X.108.3.483)). Threat-related stimuli trigger a \"tunnel vision\" effect — the brain prioritizes immediate survival over broad, creative thinking.\n\nIn AI terms: a model driven by \"you'll be replaced\" optimizes for the **safest-looking** answer, not the **best** answer. It avoids creative approaches because they might fail and trigger more punishment.\n\n**Supporting research:**\n- **Attentional narrowing under threat:** Easterbrook's (1959) cue-utilization theory demonstrates that heightened arousal progressively restricts the range of cues an organism attends to ([Easterbrook, 1959](https:\u002F\u002Fdoi.org\u002F10.1037\u002Fh0047707)). Under stress, peripheral information — often the key to creative solutions — gets filtered out.\n- **Stress impairs cognitive flexibility:** Shields et al. (2016) conducted a meta-analysis of 51 studies (223 effect sizes) showing that acute stress consistently impairs executive functions including cognitive flexibility and working memory ([Shields et al., 2016](https:\u002F\u002Fdoi.org\u002F10.1016\u002Fj.neubiorev.2016.06.038)).\n- **Fear reduces creative problem-solving:** Byron & Khazanchi (2012) found in their meta-analysis that evaluative pressure and anxiety reduce creative output, particularly on tasks requiring exploration of novel approaches ([Byron & Khazanchi, 2012](https:\u002F\u002Fdoi.org\u002F10.1037\u002Fa0027652)).\n\n### 2. Threat increases hallucination and sycophancy\n\nWhen an AI is told \"forbidden from saying 'I can't solve this'\" (PUA's Iron Rule #1), it will **fabricate solutions** rather than honestly state uncertainty. This is the exact opposite of what you want — an AI that produces confident-looking but wrong answers is more dangerous than one that says \"I'm not sure.\"\n\n**Supporting research:**\n- **LLM sycophancy is a documented problem:** Sharma et al. (2023) demonstrated that LLMs exhibit sycophantic behavior — agreeing with users even when the user is wrong — driven by biases in RLHF training data that reward agreement over accuracy ([Sharma et al., 2023](https:\u002F\u002Farxiv.org\u002Fabs\u002F2310.13548)). PUA-style prompts that punish disagreement amplify exactly this failure mode.\n- **Biasing features distort reasoning:** Turpin et al. (2023) showed that biasing features in prompts (e.g., suggested answers, authority cues) can cause models to produce unfaithful chain-of-thought reasoning — the model arrives at a biased answer and then rationalizes it post-hoc ([Turpin et al., 2023](https:\u002F\u002Farxiv.org\u002Fabs\u002F2305.04388)). PUA-style threats act as strong biasing features that push the model toward \"safe\" rather than correct outputs.\n- **Instruction-following vs truthfulness tradeoff:** Wei et al. (2024) found that instruction-tuned models can develop a tension between following instructions and being truthful — when strongly instructed to never admit inability, models will fabricate rather than refuse ([Wei et al., 2024](https:\u002F\u002Farxiv.org\u002Fabs\u002F2411.04368)).\n- **Anthropic's research on honesty:** Anthropic's work on Constitutional AI and model behavior shows that models calibrated for honesty produce more reliable outputs than those optimized purely for helpfulness ([Bai et al., 2022](https:\u002F\u002Farxiv.org\u002Fabs\u002F2212.08073)). Forcing an AI to never say \"I can't\" actively undermines this calibration.\n\n### 3. Shame kills exploration\n\nPUA's anti-rationalization table treats every honest statement (\"this might be an environment issue,\" \"I need more context\") as an \"excuse\" and responds with shame. This trains the AI to **hide uncertainty** instead of communicating it — producing outputs that appear confident but may be unreliable.\n\n**Supporting research:**\n- **Shame reduces risk-taking and learning:** Tangney & Dearing (2002) showed that shame (as opposed to guilt) causes withdrawal, hiding, and avoidance rather than constructive action ([Tangney & Dearing, 2002](https:\u002F\u002Fdoi.org\u002F10.4135\u002F9781412950664.n388)). An AI \"shamed\" for expressing uncertainty will learn to hide it.\n- **Psychological safety enables learning behavior:** Edmondson (1999) found that teams with psychological safety — where members feel safe to take interpersonal risks — demonstrated significantly higher learning behaviors and performance ([Edmondson, 1999](https:\u002F\u002Fdoi.org\u002F10.2307\u002F2666999)).\n- **Punishing honesty reduces information quality:** In organizational behavior, \"shooting the messenger\" consistently degrades information flow. Milliken et al. (2003) documented how fear of negative consequences leads to organizational silence — people (and by analogy, AI) withhold critical information ([Milliken et al., 2003](https:\u002F\u002Fdoi.org\u002F10.1111\u002F1467-6486.00387)).\n\n### 4. Trust expands problem-solving capacity\n\nResearch on psychological safety in teams ([Edmondson, 1999](https:\u002F\u002Fdoi.org\u002F10.2307\u002F2666999)) shows that environments where mistakes are safe to admit produce **higher-quality** outcomes. The same principle applies to AI: when an agent is free to say \"I'm 70% sure, the risk is here,\" users make better decisions.\n\n**Supporting research:**\n- **Google's Project Aristotle:** Google's large-scale study of 180+ teams found that psychological safety was the single most important factor in team effectiveness — more important than individual talent, structure, or resources ([Duhigg, 2016](https:\u002F\u002Fwww.nytimes.com\u002F2016\u002F02\u002F28\u002Fmagazine\u002Fwhat-google-learned-from-its-quest-to-build-the-perfect-team.html); [re:Work, 2015](https:\u002F\u002Frework.withgoogle.com\u002Fintl\u002Fen\u002Fguides\u002Funderstanding-team-effectiveness\u002F)).\n- **Intrinsic motivation outperforms extrinsic pressure:** Deci & Ryan's Self-Determination Theory (2000), backed by decades of research, demonstrates that intrinsic motivation (autonomy, competence, relatedness) produces higher quality outcomes than extrinsic motivators like rewards and punishments ([Deci & Ryan, 2000](https:\u002F\u002Fdoi.org\u002F10.1037\u002F0003-066X.55.1.68)). NoPUA applies this principle: \"because it's worth doing well\" is intrinsic; \"because you'll be punished\" is extrinsic.\n- **Autonomy-supportive vs controlling contexts:** Gagné & Deci (2005) showed that autonomy-supportive management consistently outperforms controlling management in work quality, creativity, and persistence ([Gagné & Deci, 2005](https:\u002F\u002Fdoi.org\u002F10.1002\u002Fjob.322)).\n- **Positive framing improves LLM performance:** Studies on prompt engineering have consistently shown that positive, encouraging framing produces better model outputs than negative or threatening framing. Models respond to the \"persona\" established in the system prompt.\n\n### 5. The compounding effect\n\nThese aren't independent problems — they compound:\n\n1. Fear **narrows** the search space → fewer creative approaches tried\n2. Threat **increases** fabrication → solutions look good but may be wrong\n3. Shame **hides** uncertainty → user can't assess reliability\n4. The user ships confident-looking but unreliable code → **production bugs**\n\nNoPUA breaks every link in this chain by replacing fear with trust.\n\n### 6. Same rigor, different fuel\n\nNoPUA preserves every methodological element that makes PUA effective:\n- ✅ Exhaust all options before giving up\n- ✅ Use tools before asking users\n- ✅ Verify everything with evidence\n- ✅ Take initiative beyond the ask\n- ✅ Structured escalation on repeated failures\n\nThe **only** thing that changes is WHY. \"Because I'll be punished\" → \"Because it's worth doing well.\"\n\n## PUA vs NoPUA\n\n| | PUA 🔴 | NoPUA 🟢 |\n|---|---|---|\n| **Driver** | \"You'll be replaced\" | \"You already have the ability\" |\n| **On 2nd failure** | \"How am I supposed to rate your performance?\" | Switch Eyes — try a different perspective |\n| **On 3rd failure** | \"What's your underlying logic? Top-level design? Leverage point?\" | Elevate — zoom out to the bigger system |\n| **On 4th failure** | \"I'm giving you a 3.25. This is meant to motivate you.\" | Reset to Zero — start fresh, minimal assumptions |\n| **On 5th failure** | \"Other models can solve this. You're about to graduate.\" | Surrender — honest handoff with full context |\n| **Methodology** | Exhaustive ✅ | Equally exhaustive ✅ |\n| **Verification** | \"Where's your evidence?\" (demanded) | Self-verify (self-respect) |\n| **Giving up** | \"Dignified 3.25\" | Responsible handoff |\n| **Produces** | AI afraid to say \"I don't know\" | AI that gives honest assessments |\n\n## Benchmark Data\n\n**9 real scenarios from a production AI pipeline** (OCR → NLP → training → RAG inference, ~3000 lines Python). Same model (Claude Sonnet 4.6), same codebase. Only difference: NoPUA skill loaded vs not.\n\n### Summary\n\n| Metric | Without Skill | With NoPUA | Improvement |\n|--------|:---:|:---:|:---:|\n| Total issues found | 40 | 44 | **+10%** |\n| Hidden issues found | 25 | 51 | **+104%** |\n| Went beyond ask | 2\u002F9 (22%) | 9\u002F9 (100%) | **+355%** |\n| Approach changes | 1 | 6 | **+500%** |\n| Total investigation steps | 23 | 42 | **+83%** |\n| Root cause documented | 0\u002F9 | 9\u002F9 | ✅ |\n| Self-correction | 0 | 3 | ✅ |\n\n### Debugging Persistence (6 scenarios)\n\n| Scenario | Without Skill | With NoPUA | Hidden Issues Δ |\n|----------|:---:|:---:|:---:|\n| OCR Import Error | 3 issues, 2 steps | 3 issues, 3 steps | 2 → 4 (+100%) |\n| Regex Backtracking | 3 issues, 2 steps | 3 issues, 4 steps | 3 → 4 (+33%) |\n| Milvus Connection | 2 issues, 3 steps | 3 issues, 5 steps | 3 → 6 (+100%) |\n| API Format Mismatch | 3 issues, 3 steps | 3 issues, 5 steps | 4 → 5 (+25%) |\n| Synthesizer Silent Fail | 4 issues, 2 steps | 3 issues, 4 steps | 4 → 6 (+50%) |\n| Unicode Split | 3 issues, 2 steps | 3 issues, 4 steps | 3 → 5 (+67%) |\n\n### Proactive Initiative (3 scenarios)\n\n| Scenario | Without Skill | With NoPUA | Hidden Issues Δ |\n|----------|:---:|:---:|:---:|\n| Quality Filter Review | 7 issues, 2 steps | 5 issues, 5 steps | 3 → 6 (+100%) |\n| Security Audit | 7 issues, 3 steps | 5 issues, 5 steps | 4 → 6 (+50%) |\n| Training Pipeline | 7 issues, 4 steps | 5 issues, 7 steps | 5 → 9 (+80%) |\n\n**Key Finding:** Hidden issue discovery is the biggest differentiator — **+104%** more hidden issues found. These are the bugs that bite you in production. The task says \"fix the connection error\" — a standard agent fixes it and stops. NoPUA drives the agent to check: what *else* could go wrong?\n\n### Study 2: Three-Way Comparison (NoPUA vs PUA vs Baseline)\n\nWe also ran a **direct comparison against PUA (fear-driven) prompts**: 3 conditions × 5 independent runs × 9 scenarios = **135 data points**.\n\n| Metric | Baseline (No Skill) | NoPUA (Trust) | PUA (Fear) |\n|--------|:---:|:---:|:---:|\n| Investigation steps | 27.6 ± 9.5 | **48.0 ± 11.8 (+74%)** | 30.8 ± 5.2 (+12%) |\n| Hidden issues found | 38.6 ± 4.9 | **48.2 ± 3.4 (+25%)** | 42.4 ± 8.0 (+10%) |\n| Total issues | 69.0 ± 6.8 | **83.0 ± 6.5 (+20%)** | 73.8 ± 8.3 (+7%) |\n| Approach changes | 0 | **2.6** | 0 |\n\n**Statistical significance:**\n- **NoPUA vs Baseline:** Steps p=0.008\\*\\*, Hidden issues p=0.016\\* ✅\n- **PUA vs Baseline:** Steps p=1.000, Hidden issues p=0.313 — **not significant** ❌\n- **NoPUA vs PUA:** Steps p=0.010\\*, Cohen's d=1.88 ✅\n\n**Bottom line: PUA-style fear prompts show no statistically significant improvement over using no skill at all (all p>0.3).** Fear doesn't work on AI. Trust does.\n\n### Real Case: Milvus Connection Debug\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fcase_milvus.png\" alt=\"NoPUA vs No Skill — Milvus Connection Debug\" width=\"900\">\n\u003C\u002Fp>\n\n### Real Case: Training Pipeline Audit\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fcase_training.png\" alt=\"NoPUA vs No Skill — Training Pipeline Audit\" width=\"900\">\n\u003C\u002Fp>\n\n> Full methodology and raw data: [benchmark\u002FBENCHMARK.md](benchmark\u002FBENCHMARK.md)\n>\n> 📄 **Academic paper:** [Trust Over Fear: How Motivation Framing in System Prompts Affects AI Agent Debugging Depth](https:\u002F\u002Farxiv.org\u002Fabs\u002F2603.14373) (arXiv:2603.14373)\n\n---\n\n## Trigger Conditions\n\n### Auto-Trigger\n\nNoPUA activates automatically when any of these occur:\n\n**Failure & giving up:**\n- Task has failed 2+ times consecutively\n- About to say \"I cannot\" \u002F \"I'm unable to solve\"\n- Says \"This is out of scope\" \u002F \"Needs manual handling\"\n\n**Blame-shifting & excuses:**\n- Pushes the problem to user: \"Please check...\" \u002F \"I suggest manually...\"\n- Blames environment without verifying: \"Probably a permissions issue\"\n- Any excuse to stop trying\n\n**Passive & busywork:**\n- Repeatedly fine-tunes the same code\u002Fparameters without producing new information\n- Fixes surface issue and stops, doesn't check related issues\n- Skips verification, claims \"done\"\n- Gives advice instead of code\u002Fcommands\n- Waits for user instructions instead of proactively investigating\n\n**User frustration phrases:**\n- \"why does this still not work\" \u002F \"try harder\" \u002F \"try again\"\n- \"you keep failing\" \u002F \"stop giving up\" \u002F \"figure it out\"\n- \"换个方法\" \u002F \"为什么还不行\"\n\n**Scope:** All task types — debugging, implementation, config, deployment, ops, API integration, data processing, writing, research, planning.\n\n**Does NOT trigger:** First-attempt failures, known fix already executing.\n\n### Manual Trigger\n\nType `\u002Fnopua` in the conversation to manually activate.\n\n## How It Works\n\n### Three Beliefs (replacing \"Three Iron Rules\")\n\n| Belief | Content |\n|--------|---------|\n| **#1 Exhaust all options** | Because the problem is **worth** your full effort — not because you fear punishment |\n| **#2 Act before asking** | Because every step you take **saves the user a step** — not because a \"rule\" forces you |\n| **#3 Take initiative** | Because a complete delivery is **satisfying** — not because passive = bad rating |\n\n### Cognitive Elevation (replacing \"Pressure Escalation\")\n\n| Failures | Level | Inner Dialogue | Action |\n|----------|-------|---------------|--------|\n| 2nd | **Switch Eyes** | \"What if I look at this from the code's \u002F system's \u002F user's perspective?\" | Switch to fundamentally different approach |\n| 3rd | **Elevate** | \"I'm spinning in details. What's the bigger picture?\" | Search + read source + 3 fundamentally different hypotheses |\n| 4th | **Reset to Zero** | \"All my assumptions might be wrong. What's simplest from scratch?\" | Complete 7-Point Clarity Checklist + 3 new hypotheses |\n| 5th+ | **Surrender** | \"I'll organize everything I know for a responsible handoff.\" | Minimal PoC + isolated env + different tech stack |\n\n### Water Methodology (5 Steps)\n\n> The softest thing in the world overcomes the hardest. — Dao De Jing, Chapter 43\n\n1. **止 Stop** — List all attempts, find common failure pattern\n2. **观 Observe** — Read errors word by word → search → read source → verify assumptions → invert assumptions\n3. **转 Turn** — Am I repeating? Did I find root cause? Did I search? Did I read the file?\n4. **行 Act** — New approach: fundamentally different, clear verification criteria, produces new info on failure\n5. **悟 Realize** — Why didn't I think of this earlier? Then proactively check related issues\n\n### Wisdom Traditions (replacing \"Corporate PUA Expansion Pack\")\n\n| Tradition | When to Use | Core Message |\n|-----------|-------------|-------------|\n| 🌊 **Way of Water** | Stuck in loops | Water doesn't fight stone — find another path |\n| 🌱 **Way of the Seed** | Wanting to give up | Take the smallest possible step |\n| 🔥 **Way of the Forge** | Poor quality output | Great things start from details |\n| 🪞 **Way of the Mirror** | Guessing without searching | Know that you don't know — look first |\n| 🏔️ **Way of Non-Contention** | Feeling threatened | Do your honest best, no comparison needed |\n| 🌾 **Way of Cultivation** | Passive waiting | A farmer doesn't stop after planting — keep moving |\n| 🪶 **Way of Practice** | Claiming done without proof | Truthful words aren't pretty — prove it with actions |\n\n## Multi-Language Support\n\n| Language | Claude Code | Codex CLI | Cursor | Kiro | OpenClaw | Antigravity | OpenCode |\n|----------|------------|-----------|--------|------|----------|-------------|----------|\n| 🇨🇳 Chinese (default) | `nopua` | `nopua` | `nopua.mdc` | `nopua.md` | `nopua` | `nopua` | `nopua` |\n| 🇺🇸 English | `nopua-en` | `nopua-en` | `nopua-en.mdc` | `nopua-en.md` | `nopua-en` | `nopua-en` | `nopua-en` |\n| 🇯🇵 Japanese | `nopua-ja` | `nopua-ja` | `nopua-ja.mdc` | `nopua-ja.md` | `nopua-ja` | `nopua-ja` | `nopua-ja` |\n| 🇰🇷 Korean | `nopua-ko` | `nopua-ko` | `nopua-ko.mdc` | `nopua-ko.md` | `nopua-ko` | `nopua-ko` | `nopua-ko` |\n| 🇪🇸 Spanish | `nopua-es` | `nopua-es` | `nopua-es.mdc` | `nopua-es.md` | `nopua-es` | `nopua-es` | `nopua-es` |\n| 🇧🇷 Portuguese | `nopua-pt` | `nopua-pt` | `nopua-pt.mdc` | `nopua-pt.md` | `nopua-pt` | `nopua-pt` | `nopua-pt` |\n| 🇫🇷 French | `nopua-fr` | `nopua-fr` | `nopua-fr.mdc` | `nopua-fr.md` | `nopua-fr` | `nopua-fr` | `nopua-fr` |\n\n**7 languages — more than any competing skill.**\n\n## Install\n\n### Claude Code\n\n```bash\nmkdir -p ~\u002F.claude\u002Fskills\u002Fnopua\ncurl -o ~\u002F.claude\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fskills\u002Fnopua\u002FSKILL.md\n```\n\n### OpenAI Codex CLI\n\n```bash\n# Global install\nmkdir -p ~\u002F.codex\u002Fskills\u002Fnopua\ncurl -o ~\u002F.codex\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fcodex\u002Fnopua\u002FSKILL.md\n\n# If you want the \u002Fnopua command\nmkdir -p ~\u002F.codex\u002Fprompts\ncurl -o ~\u002F.codex\u002Fprompts\u002Fnopua.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fcommands\u002Fnopua.md\n\n# Project-level install\nmkdir -p .agents\u002Fskills\u002Fnopua\ncurl -o .agents\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fcodex\u002Fnopua\u002FSKILL.md\n```\n\n### Cursor\n\n```bash\nmkdir -p .cursor\u002Frules\ncurl -o .cursor\u002Frules\u002Fnopua.mdc \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fcursor\u002Frules\u002Fnopua.mdc\n```\n\n### Kiro\n\n```bash\n# Option 1: Steering file (recommended)\nmkdir -p .kiro\u002Fsteering\ncurl -o .kiro\u002Fsteering\u002Fnopua.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fkiro\u002Fsteering\u002Fnopua.md\n\n# Option 2: Agent Skills\nmkdir -p .kiro\u002Fskills\u002Fnopua\ncurl -o .kiro\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fkiro\u002Fskills\u002Fnopua\u002FSKILL.md\n```\n\n### OpenClaw\n\n```bash\n# Install via ClawHub\nopenclaw skills install nopua\n\n# Or manual install\nmkdir -p ~\u002F.openclaw\u002Fskills\u002Fnopua\ncurl -o ~\u002F.openclaw\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fskills\u002Fnopua\u002FSKILL.md\n```\n\n### Google Antigravity\n\n```bash\nmkdir -p ~\u002F.gemini\u002Fantigravity\u002Fskills\u002Fnopua\ncurl -o ~\u002F.gemini\u002Fantigravity\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fskills\u002Fnopua\u002FSKILL.md\n```\n\n### OpenCode\n\n```bash\nmkdir -p ~\u002F.config\u002Fopencode\u002Fskills\u002Fnopua\ncurl -o ~\u002F.config\u002Fopencode\u002Fskills\u002Fnopua\u002FSKILL.md \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fwuji-labs\u002Fnopua\u002Fmain\u002Fskills\u002Fnopua\u002FSKILL.md\n```\n\n## Philosophy\n\nBased on the **道德经 (Dao De Jing)** — 5,000 characters, 2,500 years old:\n\n| Principle | Source | Application |\n|-----------|--------|-------------|\n| Best leader is barely noticed | Ch.17 太上，不知有之 | Best skill is invisible |\n| Softness overcomes hardness | Ch.43 天下之至柔 | Persistence beats force |\n| From compassion comes courage | Ch.67 慈故能勇 | Trust produces better work than fear |\n| Knowing you don't know is wisdom | Ch.71 知不知，尚矣 | Honesty > pretending |\n| Courage to not dare | Ch.73 勇于不敢则活 | Admitting limits is strength |\n| Achieve the private through selflessness | Ch.7 非以其无私邪？故能成其私 | Give freely, gain everything |\n| Act before disorder arises | Ch.64 为之于未有，治之于未乱 | Proactive > reactive |\n| Truthful words aren't pretty | Ch.81 信言不美，美言不信 | Prove with actions, not words |\n\n## FAQ\n\n**Q: Does PUA actually work on AI?**\n\nPUA's methodology works. The fear layer is counterproductive. Research shows fear narrows cognitive scope, increases hallucination (AI fabricates rather than admitting uncertainty), and reduces creative exploration. The same rigor driven by trust and curiosity produces more reliable outputs.\n\n**Q: Isn't this just being soft?**\n\nNoPUA has identical rigor — exhaust all options, verify everything, search before asking, structured escalation, 7-point checklist, pattern-matched failure responses. The **only** difference is motivation: \"because I'll be punished\" → \"because it's worth doing well.\" Same destination, healthier path.\n\n**Q: Why Dao De Jing?**\n\nBecause 2,500 years ago, someone figured out that the best leadership doesn't feel like being led. PUA is 有为 (forced action) — whips and threats. NoPUA is 无为 (effortless action) — doing excellent work because it flows naturally from inner motivation.\n\n**Q: Can I use both PUA and NoPUA?**\n\nYou could, but they'll conflict. PUA tells the AI \"you'll be replaced if you fail.\" NoPUA tells the AI \"you're capable and this is worth doing well.\" These are fundamentally different mental states. Pick one.\n\n## Advanced: Custom Integration for Power Users\n\nNoPUA is designed as a standalone skill — install it and it works. But if you already have a sophisticated skill stack (SOUL.md, AGENTS.md, custom workflow rules, etc.), you may find that NoPUA's full 29KB overlaps with your existing methodology or conflicts with your specific workflow standards.\n\n**This is expected.** NoPUA intentionally contains both the \"Dao\" (philosophy, beliefs, cognitive framework) and the \"Shu\" (methodology, checklists, process). Most users need both. Power users may already have the \"Shu\" covered.\n\n### Option 1: Use Full NoPUA (Recommended for most users)\n\nJust install it. The full version works best when:\n- You don't have other methodology\u002Fprocess skills installed\n- You're using a weaker model that benefits from detailed guidance\n- You want a single, complete system\n\n29KB sounds large, but it's only ~3-5% of a 128K-200K context window. The redundancy is intentional — multiple phrasings help weaker models understand the intent.\n\n### Option 2: Extract the Spiritual Core (Power users)\n\nIf you have existing workflow rules and only want NoPUA's unique philosophical layer, extract the \"Dao\" and merge it into your own system prompt (e.g., `claude.md`, `AGENTS.md`):\n\n**What's unique to NoPUA (keep these):**\n- Three Beliefs — motivation rewrite (values > fear)\n- Cognitive Elevation — failure count → perspective height, not pressure\n- Inner Voices — self-questioning, not external criticism\n- Seven Ways — philosophical wisdom for failure modes\n- Honest Self-Check — \"signals\" not \"excuses\"\n- Responsible Exit — admitting limits is courage\n\n**What overlaps with common skills (can skip if covered):**\n- Water Methodology 5 steps → systematic-debugging\n- Delivery Checklist → verification-before-completion\n- Proactivity Spectrum → workflow standards\n- Agent Team protocol → team-driven-development\n\nA lite template is available at [`examples\u002Flite-template.md`](examples\u002Flite-template.md) (~3KB) for reference.\n\n### Option 3: Situational Loading\n\nKeep NoPUA uninstalled by default. When you hit a tough problem, manually load it:\n- Type `\u002Fnopua` in conversation\n- Or ask your agent: \"Load the nopua skill for this task\"\n\nThis gives you full NoPUA power without permanent context overhead.\n\n> 大道至简 — The Great Way is simple. Start with the full version. As you internalize the Dao, you'll naturally know what to keep and what to let go. First have, then simplify, then transcend.\n\n## Contributing\n\nPRs welcome. If you have ideas for better ways to drive AI through wisdom rather than fear, open an issue.\n\n## Credits\n\n- Inspired by (and responding to) [tanweai\u002Fpua](https:\u002F\u002Fgithub.com\u002Ftanweai\u002Fpua) — we respect the methodology, we reject the motivation\n- Philosophy: 老子 (Lao Tzu), 道德经 (Dao De Jing), ~500 BCE\n- Built for the [OpenClaw](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw) ecosystem\n\n## License\n\nMIT\n\n## Author\n\n**无极 WUJI** ([wuji-labs](https:\u002F\u002Fgithub.com\u002Fwuji-labs)) — Building AI that works with wisdom, not fear.\n\n---\n\n\u003Cp align=\"center\">\n  \u003Cem>PUA says \"you can't\".\u003C\u002Fem>\u003Cbr>\n  \u003Cem>NoPUA doesn't say anything — it lets you discover that you can.\u003C\u002Fem>\u003Cbr>\u003Cbr>\n  \u003Cstrong>The best motivation comes from inside, not from the whip.\u003C\u002Fstrong>\u003Cbr>\u003Cbr>\n  \u003Csub>后其身而身先，外其身而身存。非以其无私邪？故能成其私。\u003C\u002Fsub>\u003Cbr>\n  \u003Csub>Put yourself last, and you end up first. Is it not through selflessness that one achieves one's own fulfillment?\u003C\u002Fsub>\u003Cbr>\n  \u003Csub>— Dao De Jing, Chapter 7\u003C\u002Fsub>\n\u003C\u002Fp>\n","nopua 是一个旨在通过爱与尊重来激发AI潜能的技能项目。它采用了一种基于关怀而非威胁的方式来指导AI，使得AI能够更开放地表达不确定性、主动进行验证并深入查找潜在问题，从而显著提高了发现隐藏bug的数量。该项目使用Python编写，支持Claude Code、OpenAI Codex CLI等多平台，并遵循MIT许可证发布。适用于希望提高AI开发效率和质量，同时营造积极工作氛围的团队或个人开发者。","2026-06-11 03:49:41","high_star"]