测试与 QA

wp-block-development

1.9Ktesting-qa

Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.

wordpress

node

1.9Ktesting-qa

提供 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

blue-ocean-strategy

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

mom-test

使用“妈妈测试”规则与客户交谈，避免引导他们：讨论他们的生活而非你的想法，询问过去的细节，少说多听。当用户提到“客户访谈”、“验证我的想法”、“用户说想要但不购买”、“引导性问题”、“妈妈测试”、“客户反馈偏差”或“访谈脚本”时使用。在准备用户研究问题、解读模糊反馈或设计避免假阳性的客户发现时也触发。涵盖承诺与推进、避免赞美以及从噪音中提取信号。关于产品-市场匹配，请参见“待办任务”。关于快速原型测试，请参见“设计冲刺”。

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.

eronred

hooked-ux

使用钩子模型（触发、行动、可变奖励、投入）设计养成习惯的产品循环。当用户提到“用户不回来”、“习惯养成”、“参与循环”、“习惯区”或“操纵矩阵”时使用。在设计通知或重新参与策略、构建连续打卡或进度系统、或分析用户注册后为何停止使用时也可触发。涵盖伦理评估和习惯引导。关于减少摩擦和B=MAP，请参见improve-retention。关于病毒式传播，请参见contagious。

refactoring-patterns

应用命名的重构转换来改善代码结构，同时不改变其行为。当用户提到“重构这个”、“代码坏味”、“提取方法”、“替换条件”、“技术债务”、“移动方法”、“内联变量”、“分解条件”或“清理这段混乱的代码”时使用。同样适用于清理遗留代码、通过重构为新增功能做准备，或识别适合特定代码坏味的转换。涵盖坏味驱动的重构、安全转换序列和测试保护。关于代码质量基础，请参见 clean-code。关于管理复杂性，请参见 software-design-philosophy。

clean-code

通过规范的命名、短小的函数和清晰的错误处理，编写可读、可维护的代码。当用户提到“清理这段代码”、“这个函数太长了”、“代码坏味道”、“命名规范”、“童子军规则”、“单一职责”或“单元测试质量”时使用。在审查拉取请求的可读性、梳理混乱的函数、讨论注释风格或改进错误处理模式时也会触发。涵盖SRP、注释纪律、格式化和单元测试。有关重构技术，请参见refactoring-patterns。有关架构和依赖规则，请参见clean-architecture。

assess-react-native-migration

1.6Ktesting-qa

Assesses whether and how an existing mobile product should migrate to React Native. Use when auditing one or more product repositories for migration readiness, including products whose iOS, Android, and other clients live in separate directories or repositories; choosing brownfield, greenfield, or a checkpoint-based path; defining a representative trial; or preparing a baseline and ROI decision before implementation. When product scope or material evidence is unavailable, grills the stakeholder with exactly one question per turn instead of sending a questionnaire.

callstackincubator

swift-concurrency

1.6Ktesting-qa

诊断 Swift 并发问题，将基于回调的代码重构为 async/await，并在处理任务、Actor、@MainActor、Sendable、数据竞争、线程安全或与并发相关的编译器和 linter 警告时指导 Swift 6 迁移。

avdlee

upgrading-react-native

1.5Ktesting-qa

Upgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x to 0.y, or migrating Expo SDK alongside a React Native upgrade.

callstackincubator

dependency-confusion

1.5Ktesting-qa

Supply-chain testing via package-manager dependency confusion: when internal package names resolve to attacker-controlled public registries, leading to malicious install and script execution. Use for npm/pip/gem/Maven/Composer/Docker manifest review and authorized red-team supply-chain exercises.

yaklang

web-cache-deception

1.5Ktesting-qa

Web cache deception and poisoning playbook. Use when CDN, reverse proxy, or application caching may serve sensitive authenticated content to other users due to path confusion or cache key manipulation.

yaklang

unity-developer

1.2Ktesting-qa

使用优化的C#脚本、高效渲染和合理的资源管理构建Unity游戏。精通Unity 6 LTS、URP/HDRP渲染管线以及跨平台部署。处理游戏系统、UI实现和平台优化。主动用于Unity性能问题、游戏机制或跨平台构建。

rmyndharis

analyzing-user-feedback

1.2Ktesting-qa

Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.

refoundai

xcode-project-analyzer

1.2Ktesting-qa

审计 Xcode 项目配置、构建设置、Scheme 行为和脚本阶段，以发现构建时间改进点，并设有明确的审批门。当开发者需要项目级构建分析、缓慢的增量构建、目标依赖指导、构建设置审查、运行脚本阶段分析、并行化改进或模块映射与 DEFINES_MODULE 配置时使用。

avdlee

build

针对 SPEC.md 进行先规划后执行的实现。原生单线程循环，无子代理。测试或构建失败时，在重试前自动调用 backprop 技能——失败的验证总会考虑新的 §V 不变量是否能防止再次发生。当用户要求构建、实现、执行规范或处理特定 §T 任务时触发（`build §T.3`、`build --next`、`implement next task`、`run the build`）。期望 SPEC.md 存在；如果不存在，则交由 spec 技能处理。

juliusbrussee

spec

在仓库根目录创建、修订或反向传播缺陷到 SPEC.md。作为项目规格的唯一修改者。当用户要求编写规格、启动新规格、从现有代码提炼规格、添加不变量、修订章节（§G、§C、§I、§V、§T、§B）或通过反向传播记录缺陷时触发。常见表述：“为……编写规格”、“新规格”、“缺陷：……”、“修订 §V.3”、“从代码提炼规格”、“规格化这个想法”。读取并遵循 FORMAT.md 中的原始编码规则以及 §T 和 §B 的管道表格式。

juliusbrussee

backprop

Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

juliusbrussee

test-guard

Review generated or changed test code against universal testing rules before it ships. Best used reactively after an agent writes, edits, generates, or refactors tests, before presenting, committing, or merging them. Use for pytest (test_*.py, *_test.py), PHPUnit/Pest (*Test.php), Jest/Vitest (*.test.ts, *.spec.js), Go (*_test.go), files under tests/, __tests__/, or spec/, and review requests like 'write tests for X', 'add tests', 'test this', 'review these tests', or PR diffs containing tests. Can also guide test writing when explicitly invoked before the work. This skill is the quality gate that prevents AI-generated test bloat. DO NOT USE for production or implementation code review (use clean-code-guard), CI or test-runner configuration, running or debugging tests, or general architecture discussion.

amelnagdy

tabletopkit

972testing-qa

Builds multiplayer spatial board games using TabletopKit on visionOS. Use when creating tabletop game experiences with boards, pieces, cards, or dice; managing seats, turns, equipment state, TabletopAction flows, or TabletopInteraction delegates; synchronizing gameplay through FaceTime Group Activities; rendering with RealityKit; or implementing snapping, tosses, and physics on a virtual table surface.

dpearson2699

appmigrationkit

967testing-qa

Transfer app data to or from other platforms using AppMigrationKit. Use when implementing system-orchestrated one-time migration between iOS and Android or another platform, building an AppMigrationExtension, packaging transportable resources with ResourcesArchiver, importing resources on the destination device, reporting import progress, handling migration errors and app group cleanup, checking MigrationStatus, or testing migration code with AppMigrationTester.

dpearson2699

ux-audit

954testing-qa

Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss. REQUIRES proof of interaction (typing, clicking, sending, observing) before any verdict — a sweep that didn't interact terminates with verdict 'Incomplete'. Walks threads, exercises every element, runs the multi-pane stress matrix, visual polish sweep, component perfection checklist, automated a11y (axe-core), pragmatic performance budget (LCP/CLS/INP), scenario battery (11 scenarios), and stress recipes including the real-flavour data battery. Hard gates: console errors/warnings = 0, network 5xx = 0, layout collapse = 0, axe Critical/Serious = 0, perf budget green. Audit-the-audit meta-check rejects rushed reports. Each finding has reproduction steps, evidence path, and suspected code location. Trigger with 'ux audit', 'walkthrough', 'qa sweep', 'audit the app', 'dogfood this', 'check all pages', 'find what's broken', 'stress the UI'.

jezweb