This skill should be used when the user asks to change "Slack adapter", "Telegram adapter", "Discord adapter", "Webhook adapter", "status delivery", "message routing", or "delivery receipts". Enforces cross-adapter parity and explicit delivery semantics.

Use when assessing regime stability by distinguishing 土崩 (popular uprising from mass discontent) versus 瓦解 (elite rebellion with military resources). Prioritizes popular sentiment analysis over elite threat management.

Use when facing public criticism or accusations in a political or organizational context. Guides officials to preserve reputation through humble acknowledgment, symbolic authority surrender, and strategic resignation offers rather than retaliation.

Use when experiencing talent attrition or when followers perceive hypocrisy between stated values and leader behavior. Diagnoses the root cause through direct inquiry, then requires a visible personal sacrifice to demonstrate that talent is valued above personal pleasures or possessions.

Use when managing follower loyalty during adversity or processing feelings of betrayal after supporters depart. Applies the marketplace analogy (dawn crowds vs. dusk emptiness) to reframe departures as natural human behavior rather than personal betrayal, enabling magnanimous leadership.

Use when building multi-state coalitions or diplomatic alliances against a dominant threat. Applies Su Qin's 合纵 strategy — analyzing each party's geography, military strength, and fears, then proposing concrete mutual defense terms with specific obligations per member.

Use when evaluating territorial concessions or appeasement strategies against aggressive neighbors. Applies the 抱薪救火 (carrying firewood to extinguish fire) framework to expose why each concession emboldens further demands and weakens negotiating position.

Use when analyzing feudal power structures or ranking noble titles. Classifies ranks using the Zhou dynasty five-tier system (公侯伯子男) and determines appropriate land grants based on merit, lineage, and strategic need.

AWS cloud patterns for Lambda, ECS, S3, DynamoDB, and Infrastructure as Code with CDK/Terraform

Authentication and authorization patterns including OAuth2, JWT, RBAC, session management, and PKCE flows

Create, update, refactor, or troubleshoot Storybook stories using project conventions. Excludes component implementation, token changes, E2E browser tests, and other documentation.

Orchestrate Claude and Codex worker TUIs from a controller agent — one worker per named herdr tab, driven over the herdr socket CLI.

Rebase branches and resolve cross-commit conflicts while preserving changes. Excludes merge-commit workflows, cherry-picking, and repository setup.

Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA. Use when local QA needs daemon, workspace, provider, or playbook setup. Do not use for unit tests, planning-only work, or browser-only checks.

Guide for assistant-stream package and streaming protocols. Use when implementing streaming backends, custom protocols, or debugging stream issues.

Drive OneKey desktop or mobile apps to verify real visual and interactive behavior using CDP/Playwright or agent-device. Use for UI 验证 or screenshot confirmation.

Add or clean temporary OneKey debug console logs with consistent prefixes and safe stringify. Excludes analytics and permanent server logs.

Creates a Pull Request from current changes for OneKey app-monorepo. Use when user wants to create PR, submit changes, or merge feature branch. Handles branch creation, commit, push, and PR creation with conversation context extraction for code review AI.

基于用户提供的技术方案、草稿或参考专利，生成、改写与统稿中文发明专利的题目、摘要、背景技术、发明内容、权利要求、附图说明和具体实施方式。用于专利撰写、专利摘要、权利要求、说明书、专利润色、专利仿写、参考专利蒸馏等场景。

开发流程五步法。支持需求理解、方案设计、代码实现、代码审查、Bug 修复。当用户提到「需求分析」「方案设计」「代码实现」「代码审查」「理解需求」「技术设计」「开始写代码」「Review」「检查代码」「bug」「报错」「崩溃」「异常」「出错了」时使用。