Use for any question or task about Rust tests, including quick how-to questions and one #[test]: where tests live, assert macros, should_panic with an expected message, Result-returning tests, integration and doc tests, rstest, mockall, coverage with cargo-llvm-cov and Criterion benchmarks. Has Rust test layout conventions and anti-patterns.

Use when the user asks for Product Change Adoption Course from supplied source materials. Trigger language: product update; feature adoption; migration guide; breaking change; interactive presentation. Produce a grounded interactive digital-human presentation your audience can interrupt with voice questions — delivered as an askable course. Do not invent unsupported facts or claim external certification, competence, or real-world completion. With explicit approval, this Skill may install or update the official PersonWise CLI and uses browser OAuth. Other course-creation requests are handled only when the user explicitly asks for them with this Skill.

Use when the user asks for Community Onboarding from supplied source materials. Trigger language: community onboarding; member onboarding; paid community start here. Produce a grounded interactive digital-human course learners can interrupt with voice questions. Do not invent unsupported facts or claim external certification, competence, or real-world completion. With explicit approval, this Skill may install or update the official PersonWise CLI and uses browser OAuth. Other course-creation requests are handled only when the user explicitly asks for them with this Skill.

Use when visual regression tests run on Chromatic Cloud for Storybook, Playwright or Cypress: the chromatic CLI, baselines, TurboSnap, UI Review, CI gating and reading exit codes to tell visual changes from errors.

Use for any question or task about a traceability matrix or requirements test coverage, including building one from a list of requirements and tests, finding requirements without tests, and proof for an auditor. Builds a requirements-to-tests matrix from a test case repository and Jira, Linear or GitHub Issues, with orphaned cases and requirements and a coverage summary.

Use when the regression suite is so large that PR-time CI is the bottleneck. Builds a CI step that runs only tests affected by the PR's changed files (from coverage maps or Bazel rdeps), plus previously failing and new tests, while a periodic full run guards against a stale map.

Use whenever Java/JVM tests call a slow, flaky, rate-limited or paid HTTP API: stub it with WireMock so tests run offline, including faults such as timeouts and 500 responses, request verification and parallel-safe ports. Mountebank for TCP, SMTP, LDAP and gRPC is in its references.

Use for any question or task about how tests build their data, including Object Mother vs Test Data Builder, long constructor calls repeated across tests, and shared fixtures that one test changes and ten others break on. Explains Test Data Builder, Factory, Object Mother, fixture composition, snapshots and production-data anonymization, and when each fits, before picking a tool.

Use when a masked dataset must be proven to meet a k-anonymity, l-diversity or t-closeness threshold before it reaches a non-production environment. Computes equivalence classes over chosen quasi-identifiers with pycanon or ARX, reports re-identification risk and gates CI.

Use when a critical user journey needs continuous checks in production, or monitor coverage was never derived from real usage. Writes a synthetic monitor for Datadog, Pingdom, Checkly or New Relic with browser or API steps, cadence, checks and alerts, and ranks unmonitored journeys from RUM data.

Use when writing or reviewing renovate.json for Mend Renovate on GitHub, GitLab, Bitbucket, Azure DevOps or Gitea: preset extends, schedules, PR limits, vulnerability alerts, packageRules matching with automerge, ignored dependencies and labels.

Use when a dependency, image or SBOM scan returned more CVEs than the team can fix and someone must decide what to fix first. Ranks each CVE by EPSS exploit probability and CISA KEV status, applies VEX and reachability, and sorts findings into Fix-Now, This-Sprint, Backlog or Accept-Risk.

Use for any question or task about SBOMs, including generating one for a container image or folder, adding SBOM generation and vulnerability scanning to a release job, compliance (US EO 14028, EU CRA, FDA) or drift between releases. Generates CycloneDX or SPDX SBOMs with Syft, scans them with Grype, diffs SBOMs in CI and explains how to choose a format.

Use when an event-sourced aggregate gains or changes an event type, snapshots are added, or a CQRS read model is projected from events. Tests given-events/when-command/then-events, replay determinism, upcasting, snapshot equivalence, projections and eventual-consistency windows.

Use when a feature pushes updates over Server-Sent Events (text/event-stream) and needs tests: EventSource events and errors, the stream format, reconnect with Last-Event-ID replay, retry intervals and per-origin connection limits, plus k6 load tests. Two-way messaging is websocket-tests.

Use when a product speaks MQTT, STOMP or AMQP and its delivery guarantees need broker-backed tests: QoS 0, 1 and 2, retained messages, Last Will, shared subscriptions and $SYS with Mosquitto and paho-mqtt; STOMP and RabbitMQ AMQP tests via Testcontainers are in its references.

Use when a PWA's manifest, icons or install handler change, install conversions drop, or an install test is flaky. Builds Playwright tests for the install flow: installability criteria, the beforeinstallprompt and userChoice chain, the iOS Safari path and display-mode standalone after install.