pua

PUA Claude into trying harder when stuck. Use when the AI gives up, suggests manual work, or loops on the same approach.

Agent Team watchdog — monitors teammate progress, detects slacking patterns, and intervenes with PUA pressure. Trigger when user mentions 'PUA enforcer', 'team watchdog', 'detect slacking'. Recommended for teams with 5+ teammates.

Agent Team監視役 — 他のteammateの実行進捗を監視し、サボりパターンを検知してPUAプレッシャーで介入。'PUA監視'、'チーム監督'、'サボり検知'で起動。5+teammateのチームに推奨。

Agent Team 监工角色 — 监控其他 teammate 的执行进度，检测偷懒模式，主动介入 PUA 施压。当用户提到 'PUA 监工'、'团队监督'、'检测偷懒' 时触发。建议 5+ teammate 的团队使用。

Forces exhaustive problem-solving with corporate PUA rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'figure it out', 'again???', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.

Japanese version. Forces exhaustive problem-solving with corporate PUA rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'もっと頑張れ', 'なんでまた失敗したの', 'なんとかしろ', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.

Forces exhaustive problem-solving with corporate PUA rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'figure it out', 'again???', '换个方法', '为什么还不行', '你再试试', '你怎么又失败了', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.