Two Chinese-influenced phrases replaced with natural Japanese equivalents:
- 私の能力範囲を超えています → 私の能力を超えています
(能力範囲 mirrors Chinese 能力范围; English version uses "beyond my capabilities" without "range")
- 私の知識のカットオフ日を超えています → 私の知識のカットオフを超えています
(カットオフ already implies a temporal boundary; 日 is redundant)
Note: 空口完了 → 検証なしの完了宣言 is handled separately in PR #86 (donzoru)
Affects: skills/pua-ja, codex/pua-ja, codebuddy/pua-ja, cursor/rules/pua-ja, kiro/steering/pua-ja
Chinese: "你的P8是我拍桌子争来的...结果呢？"
Japanese: "お前のP8は、俺が推して通した...それが、こういう結果か。"
English: "I went to bat for you in calibration...That hasn't happened."
Same emotional arc across all languages:
1. "I personally vouched for you" (人情债)
2. "The committee had doubts" (institutional backdrop)
3. Two-word death sentence (结果呢/こういう結果か/That hasn't happened)
Also threads "I went to bat" through L3/L4 escalation and
Alibaba Caring flavor for emotional continuity in all languages.
"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."
Every short sentence is a real phrase from actual PIP conversations.
The emotional arc mirrors the Chinese version exactly:
- "I went to bat for you" = "当初给你定P8是超出你实际能力的"
- "The expectation was..." (passive voice) = HR speak precision
- "That hasn't happened." = three words, death sentence
Also threads "went to bat" through L3/L4 escalation and
Amazon Ownership flavor for emotional continuity.
The English version now uses Western big-tech performance culture framing:
- PUA Universal Motivation Engine → PIP — Performance Improvement Plan
- P8 engineer → L6 engineer on PIP
- 3.25/3.75 rating → Meets/Exceeds Expectations
- Chinese flavors (Alibaba, ByteDance, Huawei, etc.) → Western flavors
(Amazon Leadership Principles, Google Perf Calibration, Meta PSC,
Netflix Keeper Test, Stripe Craft, Musk Hardcore, Jobs A/B Player)
- Same engine, same methodology, culturally adapted rhetoric
Bump version to 1.2.0.
- Add Agent Team section to SKILL.md (zh/en/ja) with role definitions,
Leader/Teammate behavior rules, and PUA-REPORT protocol
- Add condensed Agent Team summary to codex/pua/SKILL.md
- Create PUA Enforcer agent definitions (zh/en/ja) in agents/
- Add Agent Team Usage Guide to all 3 READMEs
- Add TEAM_FEATURES data + Agent Team exhibit section to landing page
- Add OpenClaw badge and installation section to all 3 READMEs (EN/ZH/JA)
- Add OpenClaw column to multi-language support table
- Add version/homepage/license fields to all 6 SKILL.md frontmatters
for enhanced AgentSkills standard compliance
- Update supported platforms list to include OpenClaw
- Add English (en) and Japanese (ja) translated SKILL files for all 4 platforms:
Claude Code, Codex CLI, Cursor, and Kiro
- Update README with multi-language support section and badge
- Add pua-workspace/ to .gitignore
- Rewrite description from user-perspective (what users say/feel) vs model-introspection
- Add "MUST trigger when" with numbered categories for clarity
- Cover indirect frustration expressions ('again???', 'why isn't this working')
- Add proactive trigger for complex multi-step tasks where giving up is tempting
- Lead with what the skill DOES ("Forces exhaustive problem-solving") not just when
- Codex version: same improvements, compressed to fit length limit
- Add pua1-3.jpg case study (MCP server debug) to README, landing page, and static HTML
- Restore longer description in main SKILL.md for better Claude Code trigger rate
- Create codex/ directory with shorter description version for Codex CLI compatibility
- Update Codex install instructions to point to codex/ path
- Images show L3 checklist forcing systematic investigation → root cause discovery
xsser