task-estimation
Provides task estimation before starting work. Use when planning new features, refactoring, bug fixes, or any non-trivial changes. Triggered by keywords like estimate, plan, complexity, tokens, approach.
brainstorming
MUST use before building features, creating components, adding functionality, or designing new behavior. Use when user says 'build', 'create', 'add feature', 'implement', 'design', or describes something new to build. Explores requirements through questions before writing code.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks. Features 3-stage review: spec compliance, code quality, then UX.
supabase-setup
Use when setting up Supabase, creating database tables, writing RLS policies, configuring Auth (especially Apple Sign-In), creating storage buckets, writing Edge Functions in TypeScript/Deno, or running migrations. Triggers on "Supabase setup", "RLS policy", "Edge Function", "database schema", "storage bucket", "Apple Sign-In auth".
swift-ios-app
Use when creating iOS apps, setting up Xcode projects, designing app architecture, implementing SwiftUI views, using SwiftData models, adding Swift 6 concurrency with actors, or integrating Supabase backend. Triggers on "new iOS app", "Swift architecture", "SwiftData setup", "actor pattern", "iOS project structure".
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
testing-flexible
Use when implementing features to write effective tests. Encourages test-first but allows prototyping.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
nix-patterns
NixOS module patterns. Use when creating or editing NixOS/home-manager modules, adding packages, or configuring programs.
markdown
>
mermaid-flowchart
>
testany-case-writing
Testany platform case 编写助手 - 将传统测试场景拆解为 Testany platform cases，并生成可注册的 case packages
testany-case
Testany platform case 注册与 CRUD - 将已准备好的 platform case package 注册到平台，并管理 metadata、脚本与生命周期
testany-debug
分析 Testany 测试失败原因 - 排查问题、查看日志、定位根因
testany-execution
Testany execution 观测与管理 - 查看进度、查询历史、刷新状态、取消未开始执行、将失败执行交给 debug
testany-guide
Testany 平台核心概念和配置参考
testany-pipeline
Testany pipeline 编排与 CRUD - 基于 automation design 或现有 case keys 创建执行与编排单元
testany-trigger
Testany 执行入口与单次触发 - 为 pipeline 配置 Plan、Manual Trigger、Gatekeeper，或立即执行一次
testany-workspace
管理 Testany 工作空间 - 成员管理、权限配置、团队组织
api-reviewer
API contract review, 接口契约评审。Use when: PRD 完成后、HLD/LLD/实现前需要审查 OpenAPI/AsyncAPI/GraphQL/gRPC/WebSocket/SSE/Webhook/SDK/文件格式/IPC-CLI 契约。
api-writer
Write API contract, 写接口契约。Use when: PRD 完成后、HLD 之前需要定义 OpenAPI/AsyncAPI/GraphQL/gRPC/WebSocket/SSE/Webhook/SDK/文件格式规范。
brd-interviewer
BRD interview, 业务需求访谈。Use when: 需要将模糊的业务想法梳理成 BRD、"帮我梳理业务需求"、"老板说要做 XXX"、"这个需求不太清楚"、"写 BRD"。
guardrails-reviewer
Review Project Guardrails, 工程规范评审。Use when: LLD/实现前需要审查 Guardrails/代码规范/工程标准是否可落地。
guardrails-writer
Write Project Guardrails, 写工程规范。Use when: 新项目启动、技术栈变更、多团队协作、事故复盘、代码规范漂移时需要定义前端/后端/API/数据/安全/运维/发布标准。
hld-reviewer
HLD review, High-Level Design review, 技术方案评审。Use when: HLD 完成后、进入 LLD/实现前需要审查技术设计、检测 PRD→HLD 漂移。
hld-writer
Write HLD, High-Level Design, 写技术设计文档。Use when: PRD 和 API Contract 完成后需要做系统架构设计、技术选型、制定技术方案。
lld-reviewer
LLD review, Low-Level Design review, 详细设计评审。Use when: 实现前需要审查 LLD 与 PRD/HLD/API Contract/Guardrails 的一致性。
lld-writer
Write LLD, Low-Level Design, 写详细设计。Use when: PRD/HLD/API Contract 完成后需要写模块设计、接口设计、实现级技术方案。
prd-reviewer
PRD review, 需求评审, 检查 PRD 质量。Use when: PRD 完成后需要评审、"审查 PRD"、"PRD 评审"、"需求评审"。
prd-studio
PRD automation, PRD 全流程。Use when: "帮我写个 PRD 并审查通过"、"自动完成 PRD"、"PRD 全流程"。
prd-writer
Write PRD, 写产品需求文档。Use when: 需要写新功能 PRD（有UI/无UI）、第三方集成、功能重构、性能/安全优化需求。
runbook-writer
Write Runbook, 撰写运维手册。Use when: LLD 完成后需要编写部署、回滚、监控、故障处理等运维文档。
test-reviewer
Review test design and readiness, 测试评审。Use when: Test Spec/Test Case Package 完成后，需要审查独立测试范围内的覆盖、追溯、执行证据与遗留风险，作为发布准备前的测试门禁。
test-spec-writer
Write test spec, 测试规格/测试用例包撰写。Use when: LLD 完成且测试策略已确认后，需要产出独立测试范围内完整的 test case package、追溯矩阵与执行说明。
test-strategy-reviewer
Review test strategy, 测试策略评审。Use when: 测试策略写完后，需要审查风险覆盖、独立测试分层、环境策略与入口/出口标准是否成立。
test-strategy-writer
Write test strategy, 测试策略撰写。Use when: PRD、API Contract、HLD 基线明确后，需要定义独立测试范围、独立测试层次、环境策略、入口/出口标准。
uc-interviewer
User journey interview, use case interview, 用户旅程访谈。Use when: BRD 完成后需要梳理用户旅程、"对齐 use case"、"确认用户操作流程"。
prompt-optimizer
撰写提示词、优化提示词、改写 Prompt、Prompt 优化。将模糊的想法转化为精确有效的 AI 提示词，支持 ChatGPT、Claude、Gemini、DeepSeek、豆包、智谱等多平台。
skill-creator
创建 Skill、写 Skill、Skill 模板。帮助创建和优化 Claude Code Skills，遵循 Testany 公司规范。
media-writer
Social media writing, content creation, 自媒体写作。Use when: 需要写微信公众号/知乎/小红书/LinkedIn/Medium/Reddit 文章。
sandbox-agent
Run agent CLIs (codex/copilot/opencode) inside a Podman container with full internet access but filesystem exposure limited to the repo root + explicit bind mounts.
mongoose
Mongoose ODM for MongoDB and Node.js. Use for schemas, models, queries, validation, middleware, population, aggregation, and MongoDB database operations in JavaScript/TypeScript applications.
bots
>-
open-brush-plugin-skill
Create and modify Lua plugins for Open Brush with full API documentation access. Use when the user wants to create Open Brush plugins, work with Lua scripts for Open Brush, or asks about Open Brush scripting API, Lua functions, or plugin development.
deep-analysis
Uses multiple parallel finder agents and multiple oracle consultations simultaneously for broad analysis. Use when asked to search from multiple angles, investigate across many files, or need parallel multi-perspective analysis.
iterative-analysis
Performs sequential multi-round oracle analysis where each round builds on previous findings. Use when user specifies analysis count (e.g., "analyze 5 times"), asks to think repeatedly, or needs progressive refinement.
Page 1123 of 1445 · 72242 results