测试与 QA

debugging-lambda-timeouts

2.2Ktesting-qa

通过系统分析函数配置、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.

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

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

wp-abilities-api

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

wp-project-triage

当你需要对WordPress仓库（插件/主题/区块主题/WP核心/Gutenberg/完整站点）进行确定性检查，包括工具链/测试/版本提示，并生成结构化JSON报告以指导工作流程和防护措施时使用。

wordpress-router

当用户询问关于 WordPress 代码库（插件、主题、块主题、Gutenberg 块、WP 核心检出）且你需要快速分类仓库并路由到正确的工作流/技能（块、theme.json、REST API、WP-CLI、性能、安全、测试、发布打包）时使用。

octocat

Use this skill whenever the prompt contains any `github.com` URL, even if the user only pastes a link and gives no GitHub-specific keywords. Handles git and GitHub operations using the gh CLI. Triggers include any GitHub link to an issue, pull request, commit, compare page, Actions run, release, discussion, or repository. Covers creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology with git log/blame/bisect.

mcollina

wp-performance

用于调查或改进WordPress性能（仅后端代理）：性能分析和测量（WP-CLI profile/doctor、Server-Timing、通过REST头部的Query Monitor）、数据库/查询优化、自动加载选项、对象缓存、cron、HTTP API调用以及安全验证。

wp-block-development

开发 WordPress (Gutenberg) 区块（Block）时使用：涵盖 block.json 元数据、register_block_type(_from_metadata)、属性与序列化（attributes/serialization）、supports 配置、动态渲染（render.php/render_callback）、版本废弃与迁移（deprecations/migrations）、viewScript 与 viewScriptModule 的对比，以及基于 @wordpress/scripts 和 @wordpress/create-block 的构建与测试工作流。

nodejs-core

Contributes to and debugs Node.js core, including nodejs/node commit and PR tone, contribution workflows, native crashes, V8 performance, node-gyp builds, N-API bindings, and libuv issues. Use when drafting or reviewing a Node.js core commit or pull request, working in nodejs/node, or diagnosing C++ addons, binding.gyp failures, segfaults, native leaks, V8 deoptimizations, and event-loop internals.

mcollina

node

提供 Node.js 与 TypeScript 开发的领域最佳实践，涵盖类型剥离、异步模式、错误处理、流、模块、测试、性能、缓存、日志等。适用于设置支持原生 TypeScript 的 Node.js 项目、配置类型剥离（--experimental-strip-types）、编写无需构建步骤的 Node 22+ TypeScript，或当用户提及“Node 原生 TypeScript”、“strip types”、“Node 22 TypeScript”、“无需编译的 .ts 文件”、“ts-node 替代方案”，或需要错误处理、优雅关闭、不稳定测试、性能分析或环境配置指导时。帮助配置用于类型剥离的 tsconfig.json、设置 package.json 脚本、处理模块解析和导入扩展，并在整个 Node.js 技术栈中应用稳健模式。

mcollina

crash-analytics

1.8Ktesting-qa

eronred

blue-ocean-strategy

1.7Ktesting-qa

通过价值创新创造无竞争的市场空间，而非正面竞争。当用户提及“蓝海”、“红海”、“战略画布”、“ERRC框架”、“价值创新”、“非顾客”、“买方效用地图”、“市场过于拥挤”、“我们如何脱颖而出”或“逃离价格战”时使用。在探索新市场类别、寻找服务不足或非顾客时也触发。涵盖四步行动框架、六条路径、买方效用地图和价值-成本权衡。如需真正的战略制定和不良战略检测，请参见good-strategy-bad-strategy。如需技术采纳战略，请参见crossing-the-chasm。如需产品定位，请参见obviously-awesome。