Coding & Development

审查中文合同文本，识别风险条款并给出修改建议。当用户发来一份合同（买卖、服务、合作、劳动合同、租赁等）并希望检查风险、谈判要点或"这份合同能不能签"时使用。

Use when user says asap, urgent, fix this asap, quick fix, just give code, no time, deadline. Fast direct fix mode for any markdown-supported CLI agent.

Find the root cause of a bug, failing test, crash or unexpected behavior with a reproduce, isolate, hypothesize, verify loop, then fix it with a regression test. Use when something is broken and the cause isn't obvious.

Use ONLY when user asks to be tutored, says be my teacher, act as TA, teach me, help me learn. Socratic concept-mastery guidance for any markdown-supported CLI agent.

Quy trình phát hành phiên bản mới lên GitHub Releases (release, phát hành, publish, tag, changelog, version mới, DMG, installer, file cài). Use when preparing or publishing a release of a tool/app - bump version, build installer, update CHANGELOG, tag, push, gh release create with asset, verify. Do NOT use for regular feature commits without a release.

Review a diff, branch or pull request for bugs, risky changes and readability problems, and report findings ranked by severity. Use when asked to review code, check a PR, or look over changes before merging.

Set up and run a WhatsApp virtual attendant for a business that sells products or services, using the Turbo Notify MCP server. Use when the user wants to create, configure, start, check or update the attendant, when an administrator or an attendant sends it a console command, or when a customer message arrives for a business that already has it. Works only with Turbo Notify.

Diagnose a failing or flaky Vitest test or a failing CI check, find the root cause, and propose or apply the smallest correct fix. Use when a test fails locally or in CI.

Add a new Next.js route handler under src/app/api with Zod validation, consistent errors and Vitest tests. Use when asked to add or extend an API endpoint.

Review the current branch's changes against main before opening a PR, using the code-reviewer subagent and this repo's checks. Use when asked to review local changes.

Configure supported Synoptic source monitors and custom scraper targets for social accounts, keywords, hashtags, cashtags, queries, follows or profile changes, Telegram channels, and GitHub repositories. Use when the user wants ongoing collection or a change to monitored sources.

Filter incoming Synoptic updates with keywords, include/exclude rules, regex, or AI filters, and organize feeds in dashboards, decks, collections, and terminal tabs. Use when configuring a monitoring workspace or reading its collection feed.

Read or edit a Synoptic profile, manage author follows and notification preferences, and review or mark notifications. Use for changes to the linked Synoptic account.

Connect to a remote machine over SSH and work in a remote project using alias, key, or password authentication configured in ssh.md. Use when the user asks to ssh into a server, run commands on a remote machine, inspect or edit files on a remote project, or work on a remote project.

>- 当用户要求“让 Pi 做/看/审”、“用 Pi Agent”、“让另一家模型出第二意见或做对比”，或遇到批量文件处理、写代码、长篇调研和联网搜索、 长文初稿这类重活时使用：为节省 Bot 自身用量，这些默认交给 Bot 电脑上的 Pi Agent。通过原生 RPC 模式调用，按任务名保存会话以便连续修改。

Every skill in ~/.agents/skills and ~/.claude/skills (mine, pstack, Matt Pocock's) is a symlink into the git repo ~/Dev/agent-skills. Use before creating, editing, or removing any skill, including via /reflect, /automate-me, or skill-creator.

Audita um perfil de Instagram e reescreve a bio. Use quando a pessoa pedir análise de perfil, revisão de bio, "meu perfil não converte", "o que melhorar no meu Instagram", ou colar bio, nome, link, destaques ou posts (ou um print) pedindo opinião. Dá nota de 0 a 10 em sete critérios, reescreve a bio em 3 versões de até 150 caracteres e lista as 3 mudanças de maior impacto, em ordem.

Guides a Product Manager through building a structured gradual release plan based on the Idira Gradual Release Framework. Use when a PM says anything like "build a gradual rollout plan", "build me a rollout strategy", "create a release plan", "rollout strategy", "release strategy", "how should I roll this out", "canary plan", "feature rollout", or mentions NFI, release rings, LaunchDarkly flags, or customer exposure waves.

Use when working on an issue-tracker ticket (Jira, Linear, GitHub Issues… e.g. RND-123) end to end — pick up, reproduce or implement, prove with evidence, move statuses. Bugs and features.

Prove a change with red → green evidence (screenshots, curl, failing-then-passing test, DB query, consumer outcome). Use standalone, as step 4 of autonomous-squad, or as QA verifying someone else's work.

Work an issue-tracker ticket (e.g. RND-123): bug → reproduce red, then minimal fix; feature → implement per PRD. Use standalone or as step 3 of autonomous-squad.

Ship a worked issue-tracker ticket (e.g. RND-123): PR → CI → independent review → evidence on the tkt → merge → cleanup, moving statuses. Use standalone or as step 5 of autonomous-squad.

改写中文或英文论文、学术文本和技术文档，减少模板化、机械化表达，保留事实、术语、引文与结构。用户要求降 AIGC、去 AI 味、人性化改写或继续已有改写轮次时使用，支持文本、TXT、DOCX、分块高亮 HTML 对照，以及可用环境中的子代理分工；不用于查重检测或承诺检测分数。

Code review rules for pull requests. Use when reviewing a PR or a diff, or re-reviewing a PR after new commits: what to flag, the severity bar, the comment format, and how to converge over review rounds instead of raising new minor issues every time.