
# A/B Testing Skill Compare two URL variants with the same persona to determine which provides a better user experience. This skill guides the comparison logic and report generation. ## When to Use - Comparing a redesign against current production - Testing feature flag variations - Evaluating staging vs production differences - Comparing different UX approaches ## Core Concept ``` Multi-Persona Testing: Same URL + Different Personas → Compare user types A/B Testing: Same Per
# Cookie Auditor Skill Audit web pages for GDPR and CCPA cookie consent compliance. ## When to Use - Verifying GDPR compliance before EU launch - Checking CCPA compliance for California users - Pre-deployment privacy compliance checks - Auditing third-party vendors' consent implementation - CI/CD compliance gates ## Audit Approach ### Phase 1: Fresh Session Setup Start with a clean browser state: ```javascript // Via browser_run_code async (page) => { // Clear all cookies await page.c
# Form Fuzzer Skill Test form inputs with edge case payloads to find security vulnerabilities and encoding issues. ## When to Use - Security testing forms for XSS/SQLi vulnerabilities - Testing input validation and sanitization - Finding unicode/encoding handling issues - Checking length limit enforcement - Pre-deployment security checks ## Flags ``` --fuzz Enable fuzzing mode --fuzz-category <category> Category: xss | sqli | unicode | length | all (default:
# GitHub PR Comments Skill Post user testing results as GitHub PR comments for CI/CD integration. ## When to Use - Running tests in CI/CD pipelines - Automated testing on PR preview deployments - Sharing test results with reviewers - Tracking UX regressions across PRs ## Prerequisites - `gh` CLI installed and authenticated - In GitHub Actions: `GITHUB_TOKEN` is automatically available - PR write permissions (`pull-requests: write`) ## Flag ``` --pr <number> Post results as comment on
# Link Checker Skill Find and validate links on web pages. Reports broken links, redirects, and other issues. ## When to Use - Before releases to catch broken links - After content updates - During user testing (with `--check-links` flag) - Regular site maintenance ## Link Extraction ### Using Browser Snapshot Use `browser_snapshot` to get page accessibility tree, then extract links: ```javascript // Links to extract const linkSelectors = [ 'a[href]', // Standard links 'area
# Screenshot Annotator Skill This skill provides visual annotation capabilities for screenshots taken during user testing. Annotations help highlight issues, confusion points, and notable elements in test screenshots. ## Purpose Add visual markers (boxes, highlights, callouts) to screenshots before capturing them. This makes test reports more actionable by clearly showing where issues occurred. ## Annotation Types ### Box A rectangular border around an element. | Variant | Border Style | U
# Session Recorder Skill Record user testing sessions as Playwright Traces for replay and analysis. Traces capture the full testing session including screenshots, DOM snapshots, network requests, and console logs. ## When to Use - `--record` flag is present in the command - User wants to replay or share a testing session - Need to debug issues found during testing - Creating documentation of UX issues ## Trace File Format Playwright Trace files (`.zip`) contain: - **Screenshots**: Captured
Comprehensive persona-based user testing skill for web applications. Simulates how real users from different demographics interact with interfaces, including realistic timing, behavioral patterns, and frustration triggers. Use when: - Testing user interfaces before release - Validating UX flows from diverse perspectives - Conducting accessibility reviews - Optimizing onboarding or checkout experiences - Getting feedback on form design
# WCAG Auditor Skill This skill provides WCAG 2.1 accessibility audit capabilities, including criteria definitions, check implementations, and scoring logic. ## Purpose Systematically evaluate web pages against WCAG 2.1 Level A and AA success criteria to identify accessibility barriers and provide remediation guidance. ## WCAG 2.1 Overview WCAG is organized around four principles (POUR): - **Perceivable**: Information must be presentable to users - **Operable**: Interface must be usable - *
# Critical Paths Skill Test must-work user journeys defined in project configuration. Critical paths are essential flows that must always function correctly. ## What is a Critical Path? A critical path is a user journey that: - Must work for the site/app to be usable - Represents core business functionality - Would cause significant harm if broken - Should be tested before every deployment ## Examples of Critical Paths | Site Type | Critical Paths | |-----------|----------------| | E-commer
# Network Throttling Skill Simulate slow or offline network conditions during user testing. Tests how well sites handle poor connectivity. ## When to Use - Testing loading states and spinners - Validating offline/PWA functionality - Simulating real-world mobile conditions - Testing error handling for slow requests - Pairing with `bad-connection-user` persona ## Network Presets ### slow-3g Simulates a poor mobile connection: | Metric | Value | |--------|-------| | Download | 400 Kbps | | U
# Stripe Checkout Testing Skill This skill provides guidance for testing Stripe checkout flows with any persona. It handles test card data, form detection, and payment-specific narration. ## Purpose Enable realistic user testing of Stripe payment flows using official test cards, with persona-appropriate reactions to checkout experiences. ## Test Card Reference Load card data from `test-cards.json`. Key scenarios: | Scenario | Card | When to Use | |----------|------|-------------| | `succes
# Smoke Testing Skill Run pre-configured smoke tests for common user flows. Quick validation that critical functionality works. ## What is Smoke Testing? Smoke testing is a quick sanity check to ensure basic functionality works before deeper testing. The name comes from electronics - if you turn on a circuit and smoke comes out, you know something is wrong without further testing. ## When to Use - Before releases to catch obvious breaks - After deployments to verify functionality - In CI/CD
# Persona Generator Skill This skill provides the schema and generation logic for creating custom user testing personas. ## Purpose Generate complete, realistic user personas from natural language descriptions. The generated personas are compatible with the `/user-test` command and follow the same schema as built-in personas. ## Complete Persona Schema ```json { "id": "string", "name": "string", "category": "custom", "techComfort": "number (1-10)", "patience": "number (1-10)",