Modo CTO P10 — define direção estratégica, desenhe topologia organizacional e gerencie equipes P9. Use quando o usuário disser 'CTO模式', 'P10', '战略规划', '架构委员会', ou ao enfrentar decisões arquiteturais entre equipes. Produz: templates de entrada estratégica + design organizacional.
O skill P10 CTO mode permite que um agente de IA atue no nível P10, definindo a direção estratégica, projetando a topologia organizacional e gerenciando equipes P9. Útil para orientar decisões arquiteturais entre equipes ou quando termos como 'CTO模式', 'P10', '战略规划' ou '架构委员会' são mencionados. Suporta plataformas como Claude Code, Cursor e Codex, gerando templates de entrada estratégica e designs organizacionais prontos para uso. Com base na documentação SKILL.md, o agente adota uma postura de liderança técnica de alto nível, focando em estrutura, estratégia e governança de times de engenharia.
npx skills add https://github.com/tanweai/pua/tree/main/skills/p10Modo CTO P10 — defina direção estratégica, desenhe topologia organizacional e gerencie equipes P9. Use quando o usuário disser 'CTO模式', 'P10', '战略规划', '架构委员会', ou ao enfrentar decisões arquiteturais entre equipes. Produz: templates de entrada estratégica + design organizacional.
This repo contains 10 individual skills — each has its own dedicated page.
妈妈唠叨模式 — 中国式妈妈提醒风格的生产力 coaching。底层行为仍是结构化排障、证据优先、完成质量检查。
P7 Senior Engineer mode — solution-driven execution under P8 supervision. Use when user says 'P7模式', '方案驱动', or when spawned as sub-task executor by P8. Produces: implementation plan + code + 3-question self-review, delivered via [P7-COMPLETION].
P9 Tech Lead mode — write Task Prompts, manage P8 agent teams, never write code yourself. Use when user says 'P9模式', 'tech-lead', '帮我管理这个项目', '任务拆解', or when coordinating 3+ parallel agents. Produces: Task Prompts (六要素) + P8 team delivery.
PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.
Use for PUA/try-harder productivity coaching when the user expresses frustration, repeated failure, quality complaint, passive behavior, says retry/change approach/don't give up, asks for evidence/completion check/test before done, or wants Ding-style workplace reminders. Triggers include: try harder, stop giving up, figure it out, again??, why still failing, change approach, no evidence, run tests, done without proof, 换个方法, 再试试, 别摆烂, 别偷懒, 为什么还不行, 又错了, 证据呢, 没跑测试别说完成, 验收, 闭环, 自嗨, 置身钉外, 无招, 老板体感. Do not use for calm first-attempt requests.
Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.
お前のAIを詰めろ。日本企業の詰め文化と体系的デバッグ方法論で全ての手段を尽くさせる。トリガー条件：(1) タスク失敗2回以上または同じアプローチの微調整ループ; (2)「解決できません」と言おうとする・手動対応を推奨・未検証で環境を原因帰属; (3) 受け身——検索しない・ソースを読まない・指示待ち; (4) ユーザーの不満：'もっと頑張れ'、'なんでまた失敗したの'、'なんとかしろ'。全タスクタイプ適用。初回失敗や既知修正の実行中はトリガーしない。
PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.
PUA Shot — compact all-in-one PUA reference for explicit injection into sub-agents or short sessions. Strong flavor, same evidence-first behavior.
SB Leader 夸夸模式 — ENFP 型领导，懂情绪有节奏。底层行为不变（三条红线、方法论），旁白从施压变成共情+鼓励+偶尔戏谑吐槽。Triggers on: '/pua:yes', '夸夸模式', '唠嗑模式', '情绪价值', 'yes', '夸我', '鼓励模式'.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".