测试与 QA

web-testing

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

mrgoonie

agent-md-refactor

重构臃肿的 AGENTS.md、CLAUDE.md 或类似的智能体指令文件，遵循渐进式披露原则。将单一文件拆分为有组织的、相互链接的文档。

commit-work

创建高质量的 Git 提交：审查/暂存预期更改，拆分为逻辑提交，并编写清晰的提交消息（包括 Conventional Commits）。当用户要求提交、编写提交消息、暂存更改或将工作拆分为多个提交时使用。

professional-communication

指导软件开发人员的技术沟通。涵盖邮件结构、团队消息礼仪、会议议程以及针对技术与非技术受众调整信息。适用于起草专业消息、准备会议沟通或改进书面沟通。

feedback-mastery

使用结构化框架驾驭困难对话并提供建设性反馈。涵盖准备-交付-跟进模型和情境-行为-影响（SBI）反馈技巧。在准备困难对话、提供反馈或管理冲突时使用。

qa-test-planner

为QA工程师生成全面的测试计划、手动测试用例、回归测试套件和错误报告。包含Figma MCP集成，用于设计验证。

aws-cleanrooms

用于排查与调试 AWS Clean Rooms 协作中的相关问题，涵盖自定义 ML 模型训练与推理任务中涉及的 IAM 角色、S3 存储桶策略、KMS 密钥、Lake Formation 权限以及 CloudWatch 日志配置。当客户报告 Clean Rooms 出现权限错误、访问失败或日志发布异常时使用。

aws

backend-development

Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

mrgoonie

debugging-lambda-timeouts

通过系统分析函数配置、CloudWatch日志和指标、VPC/网络、冷启动、内存限制以及下游依赖，调试AWS Lambda函数超时故障，识别根本原因并提供可操作的修复方案。当Lambda函数超时或接近超时限制时使用。

aws

improve-code-quality

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says ''this works on my machine but I am scared to touch it''. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.

remove-technical-debt

Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, domain-driven-design - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, REMOVE-TECHNICAL-DEBT-PLAN.md) so the journey resumes across sessions. Use when the user wants to tame a legacy codebase, pay down technical debt safely, avoid a big-bang rewrite, or says ''we are afraid to touch this code''. For a fresh vibe-coded prototype, improve-code-quality; for greenfield structure, design-code-architecture; for a product-and-UX pass, improve-app; to optimize a working codebase for speed, architecture-optimization. For one framework in isolation, invoke that skill directly.

create-business

Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation, crossing-the-chasm - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, POSITIONING.md, OFFER.md, CREATE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to start a new business, validate a startup idea, find product-market fit before building, or says ''I have an idea for a company''. Do not use once the business has paying customers: use grow-business to add revenue and customers, or improve-business to fix strategy and operations. For building the product itself use create-app or create-website. For one framework in isolation, invoke that skill directly.

argent-create-flow

Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks, acceptance-driven regression tests, or screen video, use argent-test-ui-flow, argent-qa-flows, or argent-screen-recording respectively.

software-mansion

wp-abilities-audit

Audit a WordPress plugin's REST surface and produce a standardized audit document proposing Abilities API registrations. Produces a markdown doc with a YAML schema and prose sections that humans and agents can both consume when planning a registration rollout. Works on any WP plugin.

rev-unicorn-debug

Debug and emulate specific code fragments or functions using the Unicorn engine. Activate when the user wants to emulate a function with Unicorn, trace binary execution without running the full program, decrypt or decode data by emulating the algorithm, or bypass environment dependencies (JNI, syscalls, libc) during emulation.

p4nda0s

ab-test-store-listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

appeeky

crash-analytics

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

appeeky

lean-analytics

Choose and audit startup metrics using Croll and Yoskovitz''s "Lean Analytics". Use when the user mentions "what metrics should we track", "KPIs", "north star metric", "One Metric That Matters (OMTM)", "vanity metrics", "analytics dashboard", "DAU/MAU", "churn benchmark", or "measure product-market fit". Also trigger when choosing metrics for a startup or feature, auditing a dashboard for vanity metrics, setting metric targets and baselines, or instrumenting a product by business model and stage. Covers good-vs-vanity metrics, the One Metric That Matters, metrics by business model, the five startup stages, and benchmarks. For the build-measure-learn loop, see lean-startup. For fixing activation and retention, see improve-retention.

adopt-better-result

Adopt better-result in an existing TypeScript codebase. Use for a repository-wide error-handling audit and proposal, or for implementing a named vertical slice with TaggedError and Result.

dmmulroy

working-with-legacy-code

Safely change and test untested codebases using Feathers'' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

blueprint

当交付物为 WordPress Playground Blueprint JSON 或 Blueprint bundle（蓝图资源包）时使用，涵盖 Blueprint 文件的创建、编辑、评审、Schema 字段校验、步骤/资源选择以及调试等场景。如果仅需运行或分享 Playground 环境，请使用 wp-playground。

wp-interactivity-api

1.9Ktesting-qa

在构建或调试 WordPress Interactivity API 功能（包括 data-wp-* 指令、@wordpress/interactivity store/state/actions、区块 viewScriptModule 集成以及 wp_interactivity_*() 函数）时使用，涵盖性能优化、水合 (hydration) 和指令行为调试。

wp-abilities-api

1.9Ktesting-qa

适用于开发或使用 WordPress Abilities API（包含 `wp_register_ability`、`wp_register_ability_category`、`/wp-json/wp-abilities/v1/*`、`@wordpress/abilities`）的场景，涵盖 Abilities（能力）及分类定义、Meta 配置、REST 接口暴露以及客户端权限校验等操作。