voidmatcha
- 10 skills
- 0 followers
- 18 hours ago last updated
- ▌
- ▌ Playwright Test Generator 2 · voidmatcha bundleUse this skill to generate new Playwright end-to-end tests from scratch — for a page, a user flow, a form, or a component — taking them from zero to reviewed, passing specs. Reach for it whenever someone wants to add, write, create, or scaffold Playwright E2E coverage, fill coverage gaps for uncovered routes, or bootstrap the first e2e test for a project and set up its conventions. It explores live pages only on local/disposable or externally isolated approved non-production targets to discover real selectors, proposes a scenario plan for approval, generates Page Object or flat specs that match the existing project style, then runs an e2e review and the suite before handing back. Do not use it for debugging an existing failing Playwright test (use playwright-debugger), reviewing or auditing tests that already pass (use e2e-reviewer), generating Cypress tests, or writing unit, component, or integration tests with Jest, Vitest, or Testing Library.
- ▌ Benchmark · voidmatcha bundleLocal-only regression / benchmark skill for ui-clone-skills maintainers. Drives the standard ui-reverse-engineering pipeline against the canonical reference site (https://realfood.gov) and records AE/SSIM, iteration count, gate fail counts, and outcome to benchmark/history.csv so prompt / sub-doc / model-version drift surfaces as a trend. Trigger phrases: "run benchmark" / "regression benchmark" / "benchmark clone". The Makefile no longer has a `benchmark` target — setup is inline bash in this skill (Step 1 below). Internal: NOT registered in `.claude-plugin/plugin.json` `skills`. Not part of the public 3-skill marketplace surface. Maintainer tooling only.
- ▌ UI Capture · voidmatcha bundleCapture baseline evidence from a live website URL: screenshots, scroll states, hover/click behavior, parallax, timers, and transition recordings. Use when reference artifacts are needed before implementation or comparison; not to build or diagnose a clone.
- ▌ Visual Debug · voidmatcha bundleDiagnose why an existing implementation differs from reference evidence using AE/SSIM, pixel, section, computed-style, and transition diffs. Use for post-implementation mismatch or repair guidance; not baseline capture or full clone generation.
- ▌ UI Reverse Engineering · voidmatcha bundleClone or recreate a live website URL, page, or section as React + Tailwind with extracted DOM, CSS, assets, responsive layout, motion, and interactions. Use for live-URL implementation or fidelity repair; not capture-only or diff-only requests.
- ▌ E2e Reviewer · voidmatcha bundleUse when reviewing Playwright or Cypress E2E specs, Page Objects (POM), PRs, pull requests, patches, diffs, or changed test files — asked to review tests, audit test quality, or find weak, flaky, or silently-passing tests; when tests pass CI but prove nothing or miss bugs; when auditing missing awaits, vacuous or always-passing assertions, anti-patterns, or coverage gaps. Not for debugging a test that is currently failing at runtime (use playwright-debugger / cypress-debugger).
- ▌ Cypress Debugger · voidmatcha bundleUse when a Cypress end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Cypress spec, Timed-out-retrying command, unresolved selector, cy.intercept alias or request race, suite-breaking hook, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split. Accept mochawesome or JUnit reports, errors and stacks, screenshots, videos, and CI artifacts such as a GitHub run id. Distinguish product regressions from brittle tests. Do not use for writing new Cypress tests, reviewing a passing suite, non-Cypress failures (Playwright, Jest, Vitest), or debugging an app/backend without a failing Cypress test.
- ▌ Playwright Debugger · voidmatcha bundleUse when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split. Accept error messages, playwright-report/ or HTML reports, trace.zip, screenshots, and CI artifacts identified by a GitHub owner/repo slug plus run id. Distinguish product regressions from brittle tests. Do not use for writing new Playwright tests, speeding up or reviewing a passing suite, non-Playwright failures (Cypress, Jest, Vitest), or debugging an app/backend without a failing Playwright test.
- ▌ Playwright Test Generator · voidmatcha bundleUse when someone wants to add, write, create, or scaffold new Playwright end-to-end tests for a page, flow, form, component, uncovered route, or first-project setup. The skill analyzes coverage gaps, explores live pages only on local/disposable or externally isolated approved non-production targets, proposes scenarios for approval, generates Page Object or flat specs in the project's style, then reviews and runs them. Do not use for debugging an existing failing Playwright test (use playwright-debugger), reviewing tests that already pass (use e2e-reviewer), generating Cypress tests, or writing unit, component, or integration tests with Jest, Vitest, or Testing Library.